Paper Overview¶
Source:
paper/centurion_phase1_p10_paper.pdf
What The Paper States¶
The paper defines a normative economic model with:
- principal-first accounting and settlement
- explicit separation of consensus observation and physical receipt accounting
- fail-closed claim behavior for stale/conflicting/unsafe observations
- reserve-backed smoothing with debt recoup semantics
What The Paper Is Not¶
The paper explicitly notes it is not an implementation manual and does not claim unconditional external reserve sufficiency.
Integration Guidance¶
Use the paper as normative policy reference when reviewing:
- risk-state derivation
- claim-mode gating
- settlement ordering
- source uniqueness and idempotency rules
Evidence Boundary¶
The confirmed local artifact is the PDF file, not a machine-checked proof that Solidity implements every model statement. Use the paper to define intended behavior, then require conformance tests, traces, invariants, or formal specs to prove implementation alignment.
Evidence Model¶
| Field | Requirement |
|---|---|
| Purpose | mapping the economic paper to implemented source concepts. |
| Expected location | paper artifact, traceability table, and review notes. |
| Current local evidence status | Evidence required unless the named artifact is present in this repository or the Solidity source snapshot and has been inspected in the current run. |
| What it proves | which paper claims have source analogues. |
| What it does not prove | that every paper claim is implemented unless traced. |
| How to regenerate | Run the documented tool from a clean environment, archive command, commit/source hash, config, stdout/stderr, and result files. |
| Production requirement | Results must be tied to the exact source manifest lock, compiler version, dependency lock, and deployment artifact under review. |
| Owner responsible | Protocol engineering owns source/test correctness; security review owns independent challenge; governance owns accepting residual risk. |
| Failure meaning | A failure blocks release, launch, upgrade, or operation until root cause is fixed or explicitly accepted with documented risk. |
Review Notes¶
Do not write “pass” for Paper conformance without current evidence. If evidence is missing, stale, or tied to a different source snapshot, write Evidence required and keep the gap visible in the release or operations checklist.