Free Admissibility & Citation Gap Briefing.Map your brand's footprint across the AI ecosystem and identify unverified Shadow Sources. Available for regulated enterprise evaluators.Secure Your Audit →

Buyer education

What ships today—and what stays on the roadmap

BiDigest separates what you can evaluate in production today from what remains specification or internal research—so procurement conversations stay honest.

How to read the lanes

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.

Feature availability lanes

SHIPPED

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.

SPEC

Authority re-check at execute (roadmap)

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).

DRAFT

SACI methodology

Internal State of AI Compliance Index framework; public dataset / index not implemented.

Fresh verify vs authority re-check (do not conflate)

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.

Agency recipes — fresh verify boundary

Try and 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.

Sovereign KB · IFQ · per-LLM — ask here