# Base V3 partner quickstart — status labels

**Current state: pilot prepared. This is not a pilot activation or production readiness claim.**

**Organization state: blocked, not partner-ready.** The documents are prepared
for partner review, but actual contacts, legal entity, insurance, counsel and
privacy approvals, role assignments, authorized signatory, executed commercial
terms, partner acceptance, and signatures are absent.

The only contemplated activation scope is Base chain ID 8453 with exactly one
active, explicitly allowlisted design partner. There are **zero** active
partners in this prepared package. Partner acceptance, qualified-counsel
review, Base Sepolia rehearsal, mainnet approval, and x402 settlement evidence
remain blank fail-closed fields. Solana and cross-chain value flows are outside
the pilot.

| Label | Meaning | What a partner may do | What it does **not** mean |
|---|---|---|---|
| **Read-only deployed** | A contract/address has been independently verified as deployed and is documented with chain, code hash, and read evidence. | Query documented read methods with the stated finality. | No write permission, pilot participation, audit conclusion, or production endorsement. |
| **Pilot prepared** | Artifacts, blank templates, validation structure, and decision records exist. **This package is here.** | Review schemas, plan integrations, supply only minimal off-chain test data, and identify required evidence. | No deployment, partner enrollment, role assignment, route activation, cap approval, or write authorization. |
| **Activated** | A specific, separately approved, timelocked proposal was executed and its target, calldata, receipt, and post-state were independently verified. | Use only the documented action scope and limits. | A blanket approval for other modules, routes, partners, caps, or writes. |
| **Release evidence complete** | All approved release criteria, independent audit scope/results, monitoring, incident response, V2 preservation, and governance evidence are complete for the named scope. | Use the explicitly released surface under counsel-cleared terms. | A conclusion inferred from a template, a code branch, or another module's result. |

## Partner sequence

1. **Stay on V2 by default.** Existing V2 withdrawals and routes remain the default and are not redirected by this package.
2. **Read before sharing.** Ask for the current manifest, frozen source reference, BB matrix, and required decision record. Treat missing evidence as a stop.
3. **Use minimal data.** Do not submit PII or secret material to a public chain or a template. Use a salted commitment/reference only after the evidence policy is approved.
4. **Check the exact scope.** A single activated proposal may affect only its named action. It does not activate a related route, module, cap, or partner.
5. **Do not send value or sign a transaction** based on this package. A completed independent review, populated manifest, approval records, and explicit operational authorization are required first.
6. **Do not infer organizational readiness.** Run the organizational checker
   against a separately completed candidate-bound manifest and require every
   human blocker and exact evidence digest to be satisfied.

## Immediate stop conditions

Stop and escalate if `pilotReady` is not exactly `false` before the approved release gate, V2 is not the default, a required approval phrase/evidence record is missing, a proposal contains more than one action class, or a target/calldata/cap/role is filled without the linked engineering and audit result.
