Impact summary
`ai-agent-evidence-verifiers.ts` now owns provider-specific semantic verification
for the five governed registry kinds. Its typed entry table is checked at runtime
for missing, duplicate, unknown, and orphaned dispatch before processing evidence.
The readiness CLI now orchestrates configuration/file discovery, the shared
verifier result, queue construction, and output; it no longer
contains Calliope, Clio, reconciliation, Voyage, or visual parser branches. The
canonical readiness result remains four provider-evidence surfaces, two prepared
assignments, two retired behaviors, and zero proven advantages.
Ranked coupling and failure findings
- High — registry and verifier versions are not cryptographically bound:
compile/runtime coverage proves kind presence, but a semantically wrong kind on
a surface is rejected only by each verifier's explicit surface assertion.
- High — independent human evidence remains the decision bottleneck: cleaner
orchestration does not populate quality lift or reviewer-effort delta.
- **Medium — synchronous filesystem replay is acceptable for CLI use but not a
runtime request path:** importing this service into routes would add blocking IO.
Actions
| Owner | Action and acceptance criteria | Validation |
|---|---|---|
| AI Reliability | Preserve direct end-to-end assertions for the canonical provider and retirement sets plus wrong-surface/kind mutation rejection | Focused verifier and readiness CLI tests fail on mutations and pass canonical replay |
| AI Evaluation | Obtain two genuine independent timed responses for both prepared packets; only the aggregator may populate remaining scorecard fields | Exact packet/key-bound aggregate passes every protected dimension and effort gate |
| Platform | Keep verifier service CLI-only; no app route or request-time service may import it | Import-boundary search/test and production build |
| Search/Relevance | When Voyage or SigLIP becomes configured, retain existing privacy/rights preflight and require the registry verifier before readiness credit | Provider trial plus semantic readiness replay; filename alone remains insufficient |
Next-cycle hypothesis
Assignment-receipt verification can join the same exhaustive orchestration result
without coupling the registry leaf to private forms or weakening the separate
packet/readiness digest parser. Falsify by removing or mutating either assignment
binding; readiness must withhold assignment credit while provider credit remains
unchanged.