Supporting systems

Supporting systems cut across assets, primitives, and products. They supply the information contracts act on, decide who can change rules, motivate external participants, hold shared resources, transfer selected losses, and connect otherwise isolated chains.

Follow this dependency-aware order:

1. Market information — observations and benchmark methodology.
2. Oracle — admitting selected observations into contract state.
3. Multisignature control — threshold execution authority.
4. Governance — proposal, approval, delay, execution, and emergency control.
5. Tokenomics — supply, allocation, utility, and control rights.
6. Incentive — paying for measurable protocol behavior.
7. Protocol treasury — governed assets, obligations, budgets, and backstops.
8. DeFi insurance and cover — conditional risk-transfer claims and capital.
9. Bridge — cross-chain verification, finality, and destination accounting.

Bridge remains in the foundation family because its state and finality model is prerequisite knowledge. This index links that single canonical page instead of duplicating its explanation.

The diagnostic to keep asking

For every dependency, identify its input, output, controller, economic payer, failure state, downstream consumers, and loss absorber. “Supporting” does not mean optional: an oracle, signer set, treasury, or claims process can determine whether a financial position remains solvent and redeemable.