Orientation¶
Source Of Truth¶
Protocol behavior in this handbook is derived from Solidity and support files under:
/Users/marcos/Desktop/centurion_phase1_upgradeable_refactor
If comments and implementation diverge, this handbook documents implementation behavior and flags the gap.
Working Assumptions¶
- Phase-1 custody model is principal-first.
- Deposit admission is permissioned by allowlist intent consumption.
- Vaults are per-validator beacon proxies created by
CenturionVaultFactory. - Upgradeability is intentionally enabled and controlled by
CenturionUpgradeGovernor.
How To Use The Handbook¶
- Start with System Map.
- Read Upgradeability Model before approving any production launch decision.
- Use Operations and Runbooks for execution.
- Use Permission Matrix before granting any role.
Non-Goals¶
This handbook does not claim that:
- reserve liquidity is always sufficient in correlated tail events
- oracle data is always correct
- governance keys are uncompromised
Those are explicit operational assumptions addressed in Threat Model.