What you will build
A review package that explains what the system knew, what it used and why it produced each material result.
Inputs and ownership
- Retained traces
- Audit period
- Reviewer and control scope
Blueprint
This illustrates the governed fields to define during onboarding; it is not a public production API contract.
{
"review_period": "2026-Q3",
"include": ["claims", "boundaries", "abstentions", "changes"],
"exceptions": "owner_required",
"format": "reviewable_record"
}Build it step by step
- 01
Set the review boundary
Choose the period, workflow, knowledge units and controls included in the review.
- 02
Collect material traces
Gather claim bases, policy decisions, abstentions and source changes.
- 03
Resolve exceptions
Identify missing evidence or failed controls and assign remediation owners.
- 04
Publish the review record
Preserve the approved evidence set and reviewer decision.
Prove the governed path
- The permitted path produces an answer from approved evidence.
- An unsupported request returns an explicit governed outcome.
- Every material claim resolves to a known knowledge unit.
- The decision can be rerun after a source version changes.