# Full audit plan (estimated effort for one senior engineer)

| Category | What | Needs | Estimate |
|---|---|---|---|
| A Crypto and supply chain | Verifier review; signature and canonicalisation binding; key custody interview; fixtures; a reproducible build from source | package; **repository access** for the rebuild | 1–2 days |
| B Authorization and execution path | Trace AGENT -> CAIN -> MCPGATE -> EXECUTION -> EVIDENCE in source; run bypass attempts against the real enforcement points (not helpers): no token, expired, replayed, wrong scope, malformed, policy-denied | **source access** and a **test tenant** authorised by the owner | 3–5 days |
| C Distributed systems | Fault model review; replay of the 25-scenario fault campaign; equivocation, duplicate and replayed messages; view change; restart and recovery; state divergence; independent-host assessment | **repository access**; a non-production cluster | 4–8 days |
| D Operations | Tenant isolation, secrets, logging and retention, backup and restore drill, incident response, rollback, monitoring, resource exhaustion (test environment only) | **operator interviews**; staging | 2–4 days |
| E Three sites | `PLATFORM_AUDIT/*.md` per domain; cross-site consistency; public claims compared with evidence | network | 1 day |
| F Reporting | Findings (FINDINGS_TEMPLATE.md), reproducibility worksheet, final verdict, independence declaration | — | 1 day |

Total: about **12–21 auditor-days**. Rows B–D cannot be done from the package alone. The owner keeps the implementation source private, so an engagement must arrange source access under contract. If source access is refused, your report must state that those categories were **not audited**.