Architecture recipe

Prepare an audit evidence review

Package source identities, boundaries, claims and re-verification events into a reviewable operating record.

Advanced40 minUpdated Aug 11, 2026
Outcome

What you will build

A review package that explains what the system knew, what it used and why it produced each material result.

Before you begin

Inputs and ownership

  • Retained traces
  • Audit period
  • Reviewer and control scope
Conceptual configuration

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"
}
Implementation path

Build it step by step

  1. 01

    Set the review boundary

    Choose the period, workflow, knowledge units and controls included in the review.

  2. 02

    Collect material traces

    Gather claim bases, policy decisions, abstentions and source changes.

  3. 03

    Resolve exceptions

    Identify missing evidence or failed controls and assign remediation owners.

  4. 04

    Publish the review record

    Preserve the approved evidence set and reviewer decision.

Verification checklist

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.
Next recipeBuild your first governed knowledge flow→