Skip to content

Evidence Status

This page distinguishes evidence confirmed in the current local snapshot from evidence that is referenced, missing, or required before production.

Confirmed Local Evidence

Evidence item Local path Current status What it supports What it does not prove
Solidity source snapshot /Users/marcos/Desktop/centurion_phase1_upgradeable_refactor/*.sol Confirmed present Source-grounded contract behavior and inventory Deployed addresses or production config
Source manifest lock docs/appendices/source-manifest.lock.json Confirmed present Hash, size, mtime, metadata, function, event, error, and privilege-candidate traceability for inspected Solidity files Source git commit, because the local source root is not a git checkout
Generated Solidity inventory docs/appendices/generated-solidity-inventory.md Confirmed present Human-readable source inventory and review aid Compiler-level parsing or formal proof
Implementation rationale /Users/marcos/Desktop/centurion_phase1_upgradeable_refactor/UPGRADEABLE_REFACTOR_RATIONALE.md Confirmed present Refactor intent and removed false-freeze model Independent audit result
P10 conformance report /Users/marcos/Desktop/centurion_phase1_upgradeable_refactor/P10_CONFORMANCE_REPORT.md Confirmed present Local explanation of source conformance Full formal verification
Paper PDF /Users/marcos/Desktop/centurion_phase1_upgradeable_refactor/paper/centurion_phase1_p10_paper.pdf Confirmed present Normative model reference Solidity proof by itself
JavaScript conformance harness /Users/marcos/Desktop/centurion_phase1_upgradeable_refactor/test_p10_conformance.js Confirmed present Structural/source conformance checks Exhaustive state-space proof
Compile scripts build_all.sh, compile_one.js Confirmed present Local build/size workflow Toolchain integrity without pinned binary evidence
Bytecode size JSON out/*.size.json, out/bytecode-sizes.json Confirmed present Size evidence from local build artifacts Source-to-artifact reproducibility without rerun logs

Evidence Integration Checklist

Evidence item Expected path Current status Owner Production requirement Notes
Foundry invariant suite test/, foundry.toml, CI logs Evidence required Protocol engineering Required for broad invariant confidence Not found in handbook repo or source snapshot.
Echidna campaigns echidna.yaml, corpus, logs Evidence required Security/protocol engineering Required for fuzz evidence Not found in current snapshot.
Certora specs certora/, proof reports Evidence required Formal methods/security Required before claiming Certora proof Not found in current snapshot.
SMTChecker reports reports/smtchecker/ or CI artifact Evidence required Protocol engineering Required before claiming SMTChecker coverage Not found in current snapshot.
Slither reports reports/slither/ Evidence required Security Required before claiming static-analysis pass Not found in current snapshot.
Golden traces traces/golden/ Evidence required Backend/protocol engineering Required for replayable economic scenarios Not found in current snapshot.
Python-Solidity trace bridge tools/trace_bridge/ or similar Evidence required Backend/protocol engineering Required for model-vs-Solidity replay Not found in current snapshot.
Deployment manifest deployments/<network>.json Evidence required Release engineering Required for production address claims Not in this handbook snapshot.
Role assignment manifest governance/roles-<network>.md/json Evidence required Governance operations Required for production custody claims Not in this handbook snapshot.
Runbook execution evidence evidence/<date>/... Evidence required Operations Required per production action Create per-action bundles.

Usage Rule

If evidence is missing, the handbook must say “Evidence required” instead of claiming the layer passed. Missing evidence does not prove failure; it proves the handbook cannot rely on that claim.