# Security and Partner Operability Notes

## Hard boundary

The immutable source boundary is:

> Morals over metrics. Privacy over surveillance. Freedom over control. Human
> thriving over extraction.

The complete protected-input set is **behavioral, belief, biometric,
flourishing, loyalty, profiling, quality, reputation, and surveillance**. The
complete protected-decision set is **access, custody, disputes, eligibility,
pricing, routing, settlement, slashing, and value-transfer**. The canonical
manifest records these exact sets, and supported candidate sources may not
introduce those inputs. This is a scope boundary, not a technical guarantee
about independent consumers: every proposed external integration must be
reviewed and rejected if any protected input can affect a protected decision.

## Deliberate non-features

- **Bootstrap/deployment:** all global initialization is fail-closed. The npm
  `deploy` wrapper exits non-zero.
- **Custody/slashing:** accountability vault withdrawal is rent-safe and closes
  completed accounts; slashing rejects until an independent adjudication,
  decision, appeal, and settlement-recipient design is approved.
- **Cross-chain trust:** bridge messages reject until source-domain,
  source-event proof, verifier binding, and replay protection are reviewed.
- **Post-quantum claims:** ML-DSA submissions reject until verification is
  implemented and independently reviewed for the Solana target.
- **Privacy/surveillance compliance:** a signed declaration is not a verified
  compliance finding. New declarations remain unverified and compliance
  promotion rejects until proof/adjudication exists.
- **Profile trust claims:** the passive adapter has no reputation or
  identity-verification fields. Only the profile's agent signer can update or
  close its canonical PDA.

## Release and incident posture

This is source-only and blocked, not an approval to deploy. A partner must
retain the blocked state when any required evidence is missing. No source
record, program identifier, local-validator transcript, wallet, or metadata
file establishes deployment, upgrade-authority custody, settlement, or
operational readiness.

If a previously unknown deployed instance is discovered, do not assume this
source controls it. Preserve the account/program evidence, identify the
executable program owner and upgrade authority from a trusted RPC, suspend
public claims, and route the matter through the accountable partner's incident
process.
