Integrity baseline
Phase 3 — commit / bundle integrity on governed paths, evidenced by chained hashing and execute-boundary validation (independent of model vendor / inference path). See Phase 3 acceptance + archived report.
Buyer education
BiDigest separates what you can evaluate in production today from what remains specification or internal research—so procurement conversations stay honest.
SHIPPED means in-repo product and tests support the claim on governed paths we describe. SPEC/roadmap means design intent or partial routes—not a promise that every integration behaves the same way. DRAFT means internal frameworks or indices that are not a public dataset.
Phase 3 — commit / bundle integrity on governed paths, evidenced by chained hashing and execute-boundary validation (independent of model vendor / inference path). See Phase 3 acceptance + archived report.
Live policy re-derivation at the trustee execute boundary—spec and roadmap, not production for every route. Not agency fresh verify: a new POST /api/v1/admissibility/verify with the current payload before you continue (see /partners/ai-automation/recipes).
Internal State of AI Compliance Index framework; public dataset / index not implemented.
Agency fresh verify (shipped on protected n8n recipes): call POST /api/v1/admissibility/verify again with the current payload before you continue or compensate—receipts are evidence, not standing permission. Authority re-check at execute (roadmap): live policy re-derivation at the trustee execute boundary when that route is implemented—internal engineering spec only; not interchangeable with per-request verify.
Run the simulator for a deterministic verdict on synthetic payloads, follow the handbook for definitions (T₀, T₁, breach posture), and use the published verification CLIs where Merkle batch exports apply—evidence you can rerun.