What an engagement delivers

Sample audit — a synthetic engagement, worked end to end

This is a synthetic demonstration engagement. Every artifact below is public, frozen, and byte-bound by the signed delivery. The review cover projection, the rendered finding and refusal, and every number on this page are read back from the frozen artifacts at render time — never hand-typed — a build-time parity check diffs every projected field against the artifact bytes.

Follow-up receipts. Service completion and finding resolution are separate: every remediation candidate receives a receipt named by type (correction, refusal, supersession) with the actual disposition — never a generic resolved-or-refused. Receipt type and finding resolution are independent; a receipt names its type and records the outcome.

Review cover — projected from the frozen artifacts

Source: REVIEW-COVER.md and findings/findings.json (unchanged, signed). Every row below is a read-back, not a restatement.

engagementmock engagement 1
buyerExample Health Plan (SYNTHETIC)
eval_at2026-09-14T20:51:58.210Z
rows25
propositions100
Verified59
Contested23
Unverifiable17
Stale1

One complete finding, one complete refusal

Both render through the same shared finding component (a fixed eight-element order) that the record pages use. Both are HISTORICAL-FINDINGs from the synthetic engagement — evidence of what was found at the evaluation time, never a current verification record.

SYNTHETIC FIXTURE ENGAGEMENT: row 056 · NPI 1900000561
Buyer question — npi: is the buyer-published value supported by the authorities?(npi)
VERIFIEDVERIFIED — an authority's published file supports this proposition for this subject, within its stated reliance period.
the asserted NPI exists in the pinned NPPES pool, and the NPPES-registered name matches the buyer-published name under the published name law. temporal scope: board reading as of 2026-08-10 vs NPPES reading as of 2026-09-09 vs buyer publication frozen 2026-09-13 — non-contemporaneous readings; the comparison is bounded by that window
Source: SYNTHETIC FIXTURE AUTHORITY — NPPES (invented records for the mock demonstration; never the pinned real corpora)
Limitation: NOT a current verification record — this proposition carries no verified_at/next_required_by under the production freshness contract. It is valid evidence of what was found at the stated evaluation time against the pinned corpora, and is never presented as current verification; a relying party requiring current verification must use the production record path. This engagement schema is not a second, weaker verification kernel.
evaluated at Sep 14, 2026 20:51 UTC — a historical engagement finding: no production freshness, no reliance deadline
Evidence: findings.json · fixture-authorities.json#nppes (sha256 4810ff33…)
Verification status: Historical finding — valid evidence of what was found at the stated evaluation time; not a current verification record
SYNTHETIC FIXTURE ENGAGEMENT: row 056 · NPI 1900000561
Buyer question — licence number: is the buyer-published value supported by the authorities?(licence_number)
UNVERIFIABLEUNVERIFIABLE — the check is complete but the admissible evidence cannot establish the proposition; the recorded reason says why. It says nothing adverse about the provider by itself.
no board record for licence "9999999999" — the invented licence does not exist in the SYNTHETIC FIXTURE board roster (fixture-authorities.json)
Source: SYNTHETIC FIXTURE AUTHORITY — board (invented records for the mock demonstration; never the pinned real corpora)
Limitation: NOT a current verification record — this proposition carries no verified_at/next_required_by under the production freshness contract. It is valid evidence of what was found at the stated evaluation time against the pinned corpora, and is never presented as current verification; a relying party requiring current verification must use the production record path. This engagement schema is not a second, weaker verification kernel.
evaluated at Sep 14, 2026 20:51 UTC — a historical engagement finding: no production freshness, no reliance deadline
Verification status: Historical finding — valid evidence of what was found at the stated evaluation time; not a current verification record

The artifacts, grouped by task

Understand

What was commissioned, and under what rules it was judged

Engagement scope
The commissioned question, the field scope, and the exclusions.
Adjudication law
The published rules that decided every state, with version history.
Review cover
Counts, flips across law versions, and computed tables — generated from the artifacts.

Inspect evidence

The frozen inputs and the signed findings

Roster
The full sampling frame, ordered before selection.
Sample freeze
Which rows were selected, when, and the binding digests.
Findings
The signed findings: state, reason, evidence, signature over the canonical form.
Coverage evidence
The evidence behind each lookup, including honest no-record results.

Reproduce

Re-run the check and verify the receipts yourself

Follow-up receipts
Service completion receipts — every remediation candidate, named by receipt type and actual outcome.
Labor ledger
Per-phase effort with a basis line per number.
SHA256SUMS
Digests binding the package.
Frozen delivery and its check
How to re-run the shipped check and verify the whole package offline.
For health plansScope and limits