Evidence
Conformance
A claim is publishable only when a reproducible test, signed artifact, or independent review backs it. This page is the honest scoreboard.
Claims matrix
| Claim | Evidence required | Current |
|---|---|---|
| Non-destructive attach | Write-denial test on a fixture tree | TARGET |
| Warrant verification at edge | Signed/expired/revoked vectors | TARGET |
| Atomic budget reservation | Concurrent bid harness, no overspend | TARGET |
| Idempotent write | Replay returns prior receipt | TARGET |
| Tenant isolation | Cross-tenant read/write suite | TARGET |
| No fabricated metrics | Reviewer sign-off on published claims | POLICY |
| Modern MCP transport | Recorded negotiation and compatibility tests | GAP |
Known gaps
- MCP handshake revision predates the modern target.
- README tool count (45) disagrees with the registry (53).
- Some authorization and ledger modules are in-process prototypes.
- No live production partner credentials or independent benchmark.
Release rule
No production claim without: a passing conformance suite on a pinned build, an independent review, a published security.txt, and a reconciled sandbox ledger. Marketing pages must link the evidence, not restate it.