# Base V3 partner package

**Package state:** documentation-only; no proposal is submittable and no deployment, activation, route, cap, role, partner, audit result, or public address is asserted by this package.

**Organizational readiness:** blocked. Legal entity, actual contacts,
insurance, counsel/privacy signoff, partner acceptance, role assignments,
authorized signatory authority, commercial agreement, and signatures remain
external human blockers. The package is partner-facing but the organization
must not claim to be partner-ready from these templates.

This package turns the existing Base V3 pilot material into updateable, implementation-backed handoff artifacts. It is intentionally fail-closed:

- `pilotReady` is `false`; V2 remains the default for every write decision.
- All role, partner, address, route, cap, audit-result, transaction, and approval-evidence fields are blank (`null` or `[]`).
- The prepared Base-only scope permits zero active design partners now and
  requires exactly one explicitly allowlisted design partner only at a future,
  independently evidenced activation. It does not assert a named partner or
  acceptance.
- Counsel, partner acceptance, Base Sepolia rehearsal, mainnet approval, and
  x402-settlement evidence are explicit `null` placeholders. Solana and
  cross-chain value flows are excluded.
- The eight proposals describe one action each. They cannot be bundled and have no calldata or target.
- The included scripts only validate or describe unsigned calldata structure; they cannot broadcast, sign, deploy, or activate anything.
- Organizational schema version 5 uses a dependency-free, fail-on-unknown
  Draft 2020-12 validator plus duplicate-key rejection. A ready claim requires
  25 distinct typed attestations under the approved package evidence root, 14
  external-human facts, an externally human-attested cryptographic identity
  registry rooted in a separately pinned Ed25519 trust root, exact internal
  versus partner organization separation, key-ownership and authority
  evidence, exact role allowlists/separation, strict UTC causality, and unique
  tracked evidence paths/digests.
- The ready path also requires an existing clean Git `HEAD`/tree; exact hashes
  for canonical operations, policy, supersession, open module spec, ledger,
  deployment manifest, package schema, trust registry, scope registry, and
  rollout plan; complete blocker-free canonical operations; source-commit and
  evidence-commit bindings; and exactly one canonically supported,
  deployed-authorized module/action/route with all other modules denied. The
  current worktree/status does not satisfy those gates.
- Accountability Bonds and Partnership Bonds are flourishing bonds supporting
  cooperation, accountable growth, and freedom. Flourishing is purpose-only:
  it cannot control principal, collateral, or any protected decision.
- Product boundary: `PartnershipBondV3Safe` remains bilateral settlement.
  `AccountabilityBondV3Safe` alone may use the closed typed enforcement path
  documented below; it accepts no generic evidence or discretionary payout.
- Until a signed independent human report names the exact source commit, the
  review status phrase is **exact-commit AI-assisted adversarial review**. This
  is not an audit or a mainnet-readiness statement.

## Contents

| Path | Purpose |
|---|---|
| `schemas/deployment-manifest.schema.json` | Canonical, fail-closed V3 deployment-manifest schema |
| `manifests/base-v3-deployment-manifest.template.json` | Blank Base template conforming to the schema |
| `docs/BB_MATRIX.md` | BB-01 through BB-05 partner/governance gate matrix |
| `docs/V2_V3_MIGRATION_AND_ROLLBACK.md` | Opt-in migration and rollback with V2 withdrawals/routes preserved |
| `docs/PRIVACY_DATA_MINIMIZATION.md` | Data-minimization statement |
| `docs/ORGANIZATIONAL_COMMITMENTS.md` | Principal, collateral, no-surveillance, explicit-consent, and bounded-exit commitments |
| `docs/FLOURISHING_BONDS_PRODUCT_STATEMENT.md` | Affirmative flourishing-bond purpose and exact no-control invariants |
| `docs/PILOT_COMMERCIAL_TERMS_AND_SCOPE.md` | Non-binding pilot scope and commercial schedule |
| `docs/NAMED_ROLE_COLLECTION_TEMPLATE.md` | Mandatory role/contact collection without invented people |
| `docs/SECURITY_AND_VULNERABILITY_REPORTING.md` | Private-reporting policy template and unassigned contact disclosure |
| `docs/INCIDENT_RESPONSE_AND_ESCALATION.md` | Severity, escalation, containment, communication, and drill policy |
| `docs/SUPPORT_SLA_MAINTENANCE_DEPRECATION.md` | Selectable support tiers and lifecycle policy |
| `docs/DEPLOYMENT_CHANGE_MANAGEMENT_RACI.md` | Responsibility matrix and candidate-rebinding rules |
| `docs/COMMERCIAL_LEGAL_ENTITY_SIGNATORY_CHECKLIST.md` | Entity, authority, agreement, insurance, counsel, and signature blockers |
| `docs/V3_OPERATIONS_RECONCILIATION.md` | Read-only reconciliation with canonical operations status |
| `docs/EVIDENCE_ATTESTATION_SPEC.md` | Exact evidence identity, signature, path, timing, and semantic rules |
| `docs/TWO_PHASE_CANDIDATE_FREEZE.md` | Acyclic candidate freeze and post-commit envelope procedure |
| `docs/ACCOUNTABILITY_TYPED_ENFORCEMENT_V1.md` | Closed Accountability rule, typed evidence/resolution, deadlines, and deterministic outcomes |
| `docs/GOVERNANCE_ROLE_SEPARATION.md` | Governance and role-separation disclosure |
| `docs/CAP_MAXIMUM_LOSS_DECISION.md` | Amount-free cap/maximum-loss decision record |
| `docs/INDEPENDENT_AUDIT_FROZEN_SOURCE_HANDOFF.md` | Frozen-source independent-audit handoff |
| `docs/AGENT_INTEGRATION_GUIDE.md` | Read-first agent integration guide structure |
| `PARTNER_QUICKSTART.md` | One-page state-label quickstart |
| `PARTNER_READINESS_RELEASE_CHECKLIST.md` | Fail-closed organizational release checklist |
| `schemas/organizational-readiness.schema.json` | Machine-readable organizational readiness schema |
| `schemas/trusted-identities.schema.json` | Exact trusted identity and role allowlist schema |
| `schemas/trust-root-policy.schema.json` | Non-caller-controlled external authority policy schema |
| `schemas/pilot-scope-registry.schema.json` | Closed module/route/action registry schema |
| `schemas/pilot-rollout-plan.schema.json` | Candidate-bound module-by-module rollout schema |
| `manifests/organizational-readiness.template.json` | Truthful blocked template with all human evidence absent |
| `config/trusted-identities.json` | Intentionally unconfigured human trust root; no identities invented |
| `config/trust-root-policy.json` | Intentionally disabled authority policy; positive readiness is structurally blocked |
| `config/pilot-scope-registry.json` | Intentionally unconfigured allowlist; no route invented |
| `config/pilot-rollout-plan.json` | Truthfully blocked rollout plan |
| `scripts/strict_json_schema.py` | Dependency-free strict JSON and Draft 2020-12 package-schema validator |
| `AUDIT_REMEDIATION_CLOSURE_20260826.md` | Source-level disposition of the independent adversarial findings and remaining blockers |
| `POST_REMEDIATION_REAUDIT_CLOSURE_20260826.md` | Finding-by-finding closure of the C1/H4/M2/L0 re-audit |
| `POST_REMEDIATION_VERIFICATION_RESULTS_20260826.json` | Machine-readable test, validation, checksum, and residual-blocker results |
| `proposals/` | Eight separate 3-of-5, 24-hour proposal templates |
| `scripts/` and `tests/` | Local, non-network validators and tests |

## Local verification

```bash
python3 pr10/partner-package/scripts/validate_partner_package.py
python3 pr10/partner-package/scripts/check_organizational_readiness.py
python3 pr10/partner-package/tests/test_partner_package.py -v
```

The validators inspect only local package shape/evidence. They perform no
network, RPC, wallet, signing, deployment, or governance action. Passing the
blocked template is not a readiness, legal, audit, deployment, or partner
acceptance claim.

## Engineering/audit prerequisites

See `docs/BLOCKED_FIELDS.md`. No blank field may be filled from this package alone.

## Eleventh-audit privacy execution posture

The privacy-portability execution gate no longer accepts a caller-selected
adapter or candidate-declared predicates. Its only future positive path is one
canonical repository-relative implementation and interface, exact source-commit
blob identity, an independent runner-owned oracle, an exact toolchain closure,
an enforced network/process/filesystem sandbox, and an atomic machine-signed
execution record.

That positive path is **currently structurally disabled** in
`config/privacy-execution-trust-policy.json`. No genuine canonical candidate
implementation, independently governed execution-signing authority, or reviewed
immutable toolchain closure is pinned. This is an intentional external/candidate
blocker, not evidence that execution or approval occurred. The live truth remains
`partnerReady=false`, `pilotReady=false`, zero active design partners, and V2 as
the default.

## Twelfth-audit execution transaction posture

The privacy execution design now requires a source-only, `-B` Python
standard-library closure. Any `.pyc`, `.pyo`, `__pycache__`, symlink, hardlink,
non-regular file, runtime digest mismatch, or unpinned dynamic dependency fails
closed. The isolated process receives a fixed `/work` current directory and
`PWD`, with a closed environment whose values cannot expose a host temporary
directory.

Output paths are traversed using directory descriptors and no-follow opens.
Parent symlinks, mount-boundary changes, path aliases, and linked targets are
rejected. Raw events and their signed execution record are published inside one
immutable generation directory; a single atomically replaced `CURRENT.json`
pointer exposes only a complete generation.

The independent verdict requires both expected-linked and expected-unlinked
classes. False negatives, false positives, and combined errors each receive a
conservative one-sided confidence bound. A candidate that emits a unique output
for every request, or one constant output for every request, fails closed.

The tracked execution policy remains disabled. These controls do not establish
a genuine candidate runtime, external authority, execution signature, privacy
result, or partner acceptance.
