Skip to main content
Open an artifact when you need to answer three separate questions: what does it say, why is it trusted, and what happened when it was used? No single badge answers all three.

What you can do

  • Read the current artifact on Overview: its scope, kind, source and grade.
  • See who stewards it and whether a person verified the current text.
  • Review a pending revision of a proven case.
  • Read its evidence and uses: the outcomes recorded against it and the runs and turns that cited it.
  • Walk its history of retained versions, including deleted content’s redacted versions.

Open an artifact

Select an artifact in Knowledge or follow a citation from chat, a run’s Context, an agent’s Knowledge tab, a scope card, Search quality, or Review. The drawer and full page expose the same tabs. The open artifact and tab stay in the URL, so an authorized link can return to the same view; the link never grants access. An artifact outside your current scope or source access appears unavailable rather than revealing its metadata. A source restriction continues to apply to citations, evidence, uses, and history.

Overview

Overview shows the current artifact:
  • title and author-chosen key;
  • scope, kind, content type, origin, source, and grade;
  • success and failure totals for a graded case and the latest grade change;
  • the authoring run, node, and agent for a recorded case; and
  • current text, or a field sheet for a structured record.
For synchronized content, use Synced from source and Open in source to inspect the owner of the current data. A long case can be shortened in the drawer; that display limit is not a claim that the stored artifact ends there. Read the fields independently. A proven grade can result from outcome learning, a steward decision, or a curated source. It does not establish that a person verified the current text or that every cited run succeeded. Outcome totals summarize uses; origin identifies provenance; source and scope determine access.

Human stewardship and verification

A native case can name a human steward and a reverification interval from 1 to 3,650 days. The due date is a reminder, not a grade change and not a ranking penalty. Assignment routes the task but does not grant access. With knowledge:manage at the artifact’s home and current access to the artifact, update the steward or interval and verify the current text. Verification records the person and server time. Changing the text or promoting a revision clears the prior verification; an unchanged write keeps it. Synced artifacts remain source-owned and cannot be verified here. A due occurrence creates a Verification due review item. Verifying or dismissing closes that occurrence; a later due occurrence can create new work. See Review.

Pending revision

When a person or agent proposes changed text for a proven case, Forge can hold it as a pending revision while the proven text remains live. The panel shows the proposed version, current grade, text when you may read it, progress toward promotion, and the reason a person must decide when applicable. Follow its linked review items and authoring run before approving it. A restricted revision never reveals its text to an unauthorized reader. The revision can be promoted, remain held, or be discarded; inspect History to distinguish those outcomes.

Evidence

Evidence is a bounded, newest-first log of retained outcome and review events. A row can show the signal, its source, grade change, actor, note, time, and linked run. Chat feedback appears when an agent answer cited the case and received a net feedback signal. The evidence list retains recent items; the Overview totals can include older outcomes. Evidence shows recorded signals, not proof that the artifact caused a run’s result.

Uses

Uses lists recent runs and chat turns that cited the case, newest first. A row identifies when the use occurred, the agent, and its run and node or chat turn. When an effective outcome signal exists, the row shows the success or failure counted for that use. Use this tab to move from an artifact to concrete work that consumed it. A citation proves which stored case version was used; it does not independently validate the case or the run’s reasoning.

History

History separates the current version from earlier versions. Rewriting the same keyed case retains the replaced text and attribution within the displayed history bound. Earlier versions are marked:
  • Superseded when newer text replaced them; or
  • Discarded when a pending revision never replaced the live case.
Version rows show the grade and outcome totals they held, write and replacement times, attribution, and a linked replacing run when available. Deleted content is redacted from retained versions. A deleted artifact with retained versions opens only its History tab; an unreadable artifact or one without readable retained history appears unavailable.

Interpret the evidence safely

Key state to watch

  • Unavailable. The artifact is outside your scope or source access; its metadata is not shown.
  • History only. A deleted artifact with retained versions opens only its History tab.
  • A badge read as more than it says. Use the table above before concluding from a grade, a verification or a citation.