The third independent consumer of the substrate.
H33 evidence is consumed by three independent paths — TDA (Trustless Decision Attestation), Submission (Portable Regulatory Submission), and Audit Response — all derived from the same H33-74 receipts. All three converge on the same underlying bundle hash. External auditors verify offline using the Apache 2.0 verifier. No H33 contact required.
The Auditor Artifact Loop is the loop in which an external auditor RENDERS AN INDEPENDENT VERDICT on a decision bundle — re-checking the same H33-74 receipts offline, trusting no one. It is a supporting expression of Verification, which renders the independent verdict on an artifact.
Why this exists: a decision is only defensible if a party who does not trust the producer can reach the same verdict from the record alone. The loop makes that re-check convergent and reproducible instead of a matter of belief.
The five questions this page answers
| # | Question | Answer |
|---|---|---|
| 1 | What does Verification render here? | An independent verdict that the three consumers converge on the same SHA3-384 bundle, signatures verify, and evidence paths resolve — re-checked offline. |
| 2 | What does it NOT do? | It does not PRODUCE the evidence (H33-74), record or monitor (HATS), govern the AI decision (Agent-008), or score maturity (HICS). |
| 3 | How is it different from H33-74? | H33-74 PRODUCES the receipts; Verification RENDERS the verdict on them. |
| 4 | What does a passing verdict MEAN? | It reproduces and validates — NOT that the decision was secure, correct, or compliant. |
| 5 | When to use it? | When an auditor or regulator must independently re-check a bundle with no H33 contact. |
Use it when a third party must independently re-check a decision bundle offline: audit responses to the locked Q0–Q5 questions, cross-consumer convergence, or regulatory submission re-verification. Do not use it to originate evidence (that is H33-74), to enforce or govern a decision in real time (Agent-008), to continuously record or monitor a control (HATS), or to assert that a decision was correct. A convergent verdict proves the record reproduces and validates — not that the outcome was right.
The three consumers
CROSS_CONSUMER_DISAGREEMENT. The convergence check is what makes the third-consumer story stronger than any individual artifact — same substrate, three independent verdicts, cryptographically reconciled.
Q0–Q5 question structure
Each question slot binds to a specific evidence path in the substrate and a specific verifier check code. The question TEXT is founder-locked content; the structural mapping below is independent of text and lives in /audit/questions/v0.1/manifest.json.
| Q | Theme | Evidence path(s) | Verifier checks |
|---|---|---|---|
| Q0 | authorized_holder_execution | $.decisions[0].authority_binding · $.authorities[0] | EC-3 |
| Q0.5 | constitutional_layer | $.authorities[0].scope_hash · $.decisions[0].policy_bind.policy_commitment_ns | EC-3 · EC-1 |
| Q1 | policy_committed_before_execution | $.decisions[0].policy_bind | EC-1 |
| Q2 | documented_pipeline_executed | $.decisions[0].pipeline_dag | EC-5 |
| Q3 | model_identity_at_decision_time | $.decisions[0].model_fingerprint | EC-2 |
| Q4 | evidence_citation_chain_to_corpus | $.corpus_pin · $.decisions[0].evidence_attestation.evidence_set · $.decisions[0].result_citation_bind.citation_set | EC-6 · EC-7 · EC-8 |
| Q5 | calibrated_abstention_attested | $.decisions[0].calibrated_abstention_bind | EC-4 |
Demo audit response
A scaffold audit response for the claim_84711 demo bundle is published. Verdict slot machinery is operational; question text awaits founder lock.
/audit/claim_84711/audit-response.json
$ curl -s https://h33.ai/audit/claim_84711/audit-response.json | jq '.responses[] | {question_id, verdict}'When Q0–Q5 lock completes
Within 5 working days of the lock session per auditor-loop-prebuild-v0.1.md: question text published at /audit/questions/v0.1/Q*.txt; manifest digest pinned; auditor-loop service builds and publishes real audit responses (no longer scaffolds); verifier --mode audit-response ships under Schema Freeze Alpha-1 Amendment #4; smoke test extended to assert convergence on every demo bundle.
Questions auditors ask
What is the Auditor Artifact Loop?
A supporting expression of Verification: the same H33-74 receipts feed three independent artifacts and an external auditor RENDERS an independent verdict on them offline, trusting no one. It re-checks the artifact; it does not produce the underlying evidence — that is H33-74.
What does a passing audit verdict mean — and not mean?
It means the artifact reproduces and validates: the three consumers converge on the same SHA3-384 bundle, signatures verify, and evidence paths resolve. It does NOT mean the underlying decision was secure, correct, compliant, or good.
How is this different from H33-74?
H33-74 PRODUCES the receipts and attestations. Verification — expressed here as the Auditor Artifact Loop — RENDERS the independent verdict on them. It does not record or monitor (HATS), govern an AI decision (Agent-008), or score maturity (HICS).
When should I use it?
When an external auditor or regulator must independently re-check a decision bundle with no H33 contact. Do not use it to originate evidence, enforce policy in real time, or claim a decision was correct.