# Organizational commitments for any partner pilot

These are non-negotiable operating and commercial boundaries for the prepared
pilot. They apply to proposals, statements of work, support decisions, incident
handling, and change approvals. They do not assert deployment or partner
acceptance.

Accountability Bonds and Partnership Bonds are flourishing bonds supporting
cooperation, accountable growth, and freedom. Partnership Bonds support
cooperation through bounded bilateral commitments; Accountability Bonds
support accountable growth through objective typed commitments. Both preserve
freedom through explicit consent and bounded exits. Flourishing is purpose,
not a score or control signal: it cannot control principal, collateral, or any
protected decision. See `FLOURISHING_BONDS_PRODUCT_STATEMENT.md`.

1. **Flourishing cannot slash principal.** Flourishing, wellbeing, loyalty,
   quality, reputation, belief, or behavioral measurements must never reduce
   principal, collateral, custody, settlement, access, or eligibility.
2. **Rewards cannot consume collateral.** Incentives and rewards must be funded
   separately. They cannot draw down, reclassify, encumber, or make contingent
   any principal or collateral owed to a participant.
3. **Surveillance is never required.** Participation, pricing, support,
   eligibility, dispute rights, and exit must not require behavioral tracking,
   biometric data, location history, communications monitoring, social-graph
   analysis, or equivalent surveillance.
4. **Consent is explicit.** Consent must be specific, informed, affirmative,
   recorded, scoped to a stated purpose, and revocable prospectively where
   applicable. Silence, bundled terms, continued use, or a public-chain address
   is not consent.
5. **Exits are bounded.** Every pilot agreement must state its term, termination
   triggers, notice, wind-down responsibilities, data return/deletion rules,
   unresolved-dispute handling, and the maximum time to complete exit. An exit
   must not silently strand partner data or expand custody.

## Machine-enforced release principles

The readiness manifest also requires: surveillance data is never permitted for
custody, access, eligibility, pricing, slashing, settlement, dispute, or routing
decisions, including biometric, profiling, behavioral, reputation, belief,
flourishing, quality, loyalty, hashed, derived, or transitive forms; refunds
and terminal exits remain bounded and available while paused; rollout is one
enumerated module/action/route at a time; liabilities and maximum loss are
numeric and bounded; value recipients use pull payments; APIs fail closed;
evidence bindings are immutable; tests bind an existing exact clean Git commit
and tree; and cross-chain trust portability is chain-specific, consented,
minimal, and unlinkability-reviewed while cross-chain value flow remains
excluded from this Base pilot.

No exception may be created by an SLA, commercial discount, incident response,
or change request. A requested exception is a stop condition requiring written
privacy and counsel review plus a revised candidate; it cannot be accepted by
an operator informally.
