# BB matrix — Base V3 partner package

Every row is **blocked/pending** until the named evidence exists. “Prepared” means a template or validation surface exists; it is not a release decision.

| ID | Decision / boundary | Current package state | Required evidence before a status changes | Owner separation | Fail-closed rule |
|---|---|---|---|---|---|
| BB-01 | Build and source identity | Prepared; frozen handoff structure only | Exact commit, reproducible build result, compiler/settings, source hashes, dependency lock evidence | Engineering produces; independent reviewer verifies | No address, bytecode claim, or audit scope is inferred from a branch name or template. |
| BB-02 | V2 preservation | Pending engineering/V2 audit results | V2 ABI/route/withdrawal regression results; indexer/API compatibility evidence; rollback rehearsal | V2 maintainer and verifier separate from V3 implementer | V2 remains default; no V2 route or withdrawal is redirected, removed, paused, or made contingent on V3. |
| BB-03 | V3 deployment and module/route scope | Prepared; no deployment assertion | Populated manifest, source/build match, address/code hash, target ABI, post-state reads | Deployer/proposer, reviewers, and executor separately evidenced | Blank target/calldata, `pilotReady: false`, and no active module/route until a single-action proposal is verified. |
| BB-04 | Governance and role separation | Pending governance design/implementation audit | Verified governance variant, 5 signer slots, threshold, 24-hour delay, guardian design, conflict disclosures | Signers, guardians, attesters, adjudicators, and design partners cannot be assumed to overlap | No role/address is invented; the template does not prove an implemented 3-of-5 control. |
| BB-05 | Caps, loss limits, activation, and operations | Prepared; amount-free decision template | Approved cap/maximum-loss record, solvency/withdrawal results, monitoring and incident evidence, independent audit scope/result | Risk decision, technical verification, and activation approval are separately recorded | No numeric cap, partner, factory permission, write path, or production-ready claim exists until each linked evidence item is complete. |

## Gate rule

All evidence must identify its source, date, scope, reviewer, and immutable reference. A blank, a failed check, a stale reference, or an unrelated approval leaves the row blocked. BB rows do not substitute for on-chain controls, independent audit results, or explicit governance approvals.
