Chain / On-Chain
Define the record object, source evidence, required metadata, submitter roles, approval states, change rules, and the difference between stored evidence and verified truth.
Evidence design begins before any chain decision. OCO defines what the record represents, where the source evidence comes from, who can submit or update it, which metadata is required, what changes are allowed, and what must remain private. The chain layer is only useful if the record model is already clear enough to be reviewed and challenged.
Approach
Chain or on-chain infrastructure is used only when the use case justifies a durable evidence layer. OCO begins by separating truth of the original input from proof of submission, approval, timestamp, change history, or disclosure state. Governance, input controls, reviewable records, and clear user explanation carry the trust model. The chain layer then becomes one part of a broader evidence system: useful when it strengthens accountability, avoided when a normal database, audit log, or private record is the better engineering choice.
Scope
OCO uses chain or on-chain infrastructure when a data product needs durable records, verification paths, public accountability, or alteration-detectable change history.
Tamper-evident evidence and transparency records.
A chain record does not make an original claim true by itself. It makes records, changes, approvals, and evidence trails harder to alter without detection when governance, input controls, and review paths are defined.