Executive summary
Supervisory attention is moving from post-hoc monitoring alone toward lifecycle controls, human oversight, and evidence that decisions can be traced to approved anchors before they bind to systems of record. This page pairs two illustrative videos with the downloadable State of Admissibility 2026 Markdown skeleton (same file as the button above) for PDF export and auditor mapping tables.
Observability vs. admissibility
Archetypal comparison — named vendors (e.g. Arize, LangSmith, Honeycomb) are examples of the observability column, not a feature-by-feature audit. See white paper Appendix E.
| Feature | Traditional observabilitye.g. Arize, LangSmith, Honeycomb | BiDigest Trustee-tierAdmissibility |
|---|---|---|
| Primary goal | Model Performance: Debugging, evaluation, and drift detection. | Execution Integrity: Enforcement, SoD, and forensic admissibility. |
| Operational timing | Reactive: Analyzes traces after the LLM has already responded. | Proactive: Intercepts intent before the state transition (Commit Boundary). |
| Control mechanism | Alerting: Notifies a human if a “guardrail” is breached. | Mechanical Gating: Fails-closed at the DB layer if the “double-lock” is missing. |
| Trust foundation | Statistical: Based on confidence scores and semantic similarity. | Deterministic: Based on cryptographic hashes and versioned Anchor Prose. |
| Audit artifact | Logs/Traces: High-fidelity records of what the model said. | Forensic Receipt: Merkle-sealed proof of who authorized the action and why. |
| SoD enforcement | None: Does not distinguish between Proposer and Approver at the API level. | Hard-Coded: Schema-level constraints prevent self-approval of sensitive actions. |
| Regulatory fit (illustrative) | NIST (Measure): Good for “measuring” model risk. | MAS/FCA/EU AI Act (Manage): Designed for “lifecycle control” and “human oversight.” |
Primary goal
Observability
Model Performance: Debugging, evaluation, and drift detection.
BiDigest admissibility
Execution Integrity: Enforcement, SoD, and forensic admissibility.
Operational timing
Observability
Reactive: Analyzes traces after the LLM has already responded.
BiDigest admissibility
Proactive: Intercepts intent before the state transition (Commit Boundary).
Control mechanism
Observability
Alerting: Notifies a human if a “guardrail” is breached.
BiDigest admissibility
Mechanical Gating: Fails-closed at the DB layer if the “double-lock” is missing.
Trust foundation
Observability
Statistical: Based on confidence scores and semantic similarity.
BiDigest admissibility
Deterministic: Based on cryptographic hashes and versioned Anchor Prose.
Audit artifact
Observability
Logs/Traces: High-fidelity records of what the model said.
BiDigest admissibility
Forensic Receipt: Merkle-sealed proof of who authorized the action and why.
SoD enforcement
Observability
None: Does not distinguish between Proposer and Approver at the API level.
BiDigest admissibility
Hard-Coded: Schema-level constraints prevent self-approval of sensitive actions.
Regulatory fit (illustrative)
Observability
NIST (Measure): Good for “measuring” model risk.
BiDigest admissibility
MAS/FCA/EU AI Act (Manage): Designed for “lifecycle control” and “human oversight.”
AI admissibility infrastructure
Honest scope explorer
- Status
- Operational
- Phase
- 1 — implementation
- Security level
- High
High risk scope
Autonomous or high-impact engines (money, safety, legal). Mechanical enforcement and deterministic evidence are required before claims of admissibility.
CISO admissibility checklist
Decision lineage
ImplementedImplemented: forensic receipts capturing inputs and signatures (Trustee commit path).
Real-time intercept
ImplementedImplemented: commit-boundary APIs gate execution before external side effects.
Fail-closed blocking
ImplementedImplemented: schema and API posture fail closed when admissibility preconditions are missing.
entry_hash integrity (CAS)
ImplementedImplemented: compare-and-swap style hash checks on sealed entries.
Semantic / KB drift gate
IllustrativeIllustrative (Phase 2): freshness and semantic drift are on the roadmap; hash integrity is enforced today.
Second human approver (DB-enforced)
IllustrativeIllustrative (Phase 2): multi-human approval chains beyond single approver SoD.
Independent verification terminal
Terminal ready. Select a verification command to see auditor-facing notes (this UI does not run shell commands).
Badges reflect repository posture as of Phase 1. This panel is educational; run the listed npm scripts in your controlled environment to produce deterministic audit output.
Commit boundary (Slice A)
Mechanical segregation of duties: intent is anchored, human-approved with hash match, then executed—fail-closed by design.
Illustrative motion graphic — not a substitute for your policies, controls, or legal review.
Triple Lock — Legal · Risk · Engineering
How decision rights show up at the intercept: the same verdict semantics governance expects, not a rubber stamp.
Illustrative motion graphic — not a substitute for your policies, controls, or legal review.
Full narrative & appendices
Chapters on IFQ, Merkle forensic batches, jurisdictional sovereignty, glossary, and bibliography are in the Markdown skeleton download. Use it for long-form reading, PDF export, and mapping tables for auditors.