How To Read This Handbook¶

Reader Paths¶

• Owner or signer: start with governance, security, runbooks.
• Engineer: start with architecture, smart contracts, state machines.
• Operator: start with deposits, claims, operations, runbooks.
• Auditor: start with source references, permission matrix, threat model.

Evidence Markers¶

Pages use the following evidence patterns:

• Implementation-grounded: behavior visible in Solidity functions, enums, errors, events, and storage.
• Operational recommendation: safety policy added by handbook authorship.
• Evidence required: claim cannot be confirmed from inspected repository snapshot or local evidence files.

Safety Reading Order Before Production Actions¶

1. Roles And Custody
2. Monitoring Queued Upgrades
3. Permission Matrix
4. Threat Model
5. Upgrade Runbook