Architecture Center
Human-approved artifact
Show how sources become a structured artifact whose claims are grounded, reviewed, and released only through an authorized decision.
previewreferenceContract >=0.8 <1.0Reviewed 2026-07-20
Problem statement
Model- or worker-generated outputs need to be grounded in verifiable claims and reviewed before they ship, with a durable record of exactly what was produced and approved. This is a platform pattern, not a fixed research product.
When to use
- Outputs must be reviewed by a human before they are considered final.
- Every claim in the output must be traceable to its sources.
- You need the revision that was approved kept as a durable record.
When not to use
- Low-stakes drafts where no review or provenance is required.
- Fully automated pipelines with no human approver in the loop.
Flow
SourcesObservationsClaimsEvidence coverageStructured artifactReviewer feedbackRevised artifactFinal decisionApproved delivery
Resource inventory
- Artifact + revisions
- The structured output and its immutable history.
- Claims + evidence
- Ground each assertion; coverage informs the reviewer.
- Decision
- The authorized approval that releases the artifact.
- Audit projection
- Records feedback, revisions, and the final decision.
Failure modes
- Evidence threshold not met
- Reviewer requests a revision; the author adds evidence.
- Reviewer rejects
- A rejection with reason is recorded; the artifact does not advance.
- Stale revision approved
- Version preconditions reject an approval against a superseded revision.
Security controls
- Only authorized reviewers can resolve the decision.
- The approved revision is immutable and retained.
- Every feedback and decision event is auditable.
Deployment checklist
- Reviewer roles and authority defined.
- Evidence policy set for the gated claims.
- Revision retention confirmed.
- Audit projection monitored.
Related quickstart: Request and resolve a decision →