01 / Overview
Tamper-evident evidence and transparency records.
OCO uses chain or on-chain infrastructure when a data product needs durable records, verification paths, public accountability, or alteration-detectable change history.
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.
OCO uses chain or on-chain infrastructure when a data product needs durable evidence, public accountability, transparent history, or independent verification. The chain layer is chosen only when it strengthens the record system; it is not treated as decoration or a replacement for governance.
Chain / On-Chain Delivery Flow
Evidence records where verification matters.
02 / Evidence purpose
Evidence purpose
The work starts by defining what must be proven: existence, approval, change history, public disclosure, organizational status, document state, candidate position, record lineage, or another accountable event.
OCO separates claims from evidence. A chain record can make alteration harder to hide, but it does not make a false input true.
03 / Record schema
Record schema
OCO defines the record object, identifiers, timestamps, source references, signer or approver context, public fields, private fields, hashes, attachments, status, and update rules.
The schema defines what goes on-chain, what is anchored, what stays off-chain, and how public verification can work without exposing private material.
04 / Chain boundary
Chain boundary
OCO decides whether the product needs a rollup, public chain, private chain, public anchor, transaction record, audit log, or no chain at all. The decision follows verification need, cost, privacy, throughput, permanence, and operational control.
This prevents forcing blockchain into records that are better served by a normal database, signed log, private ledger, or standard audit trail.
05 / Transaction path
Transaction path
OCO defines who can create, update, attest, revoke, correct, or publish a record. The path includes permissions, signatures, queueing, transaction status, retry behavior, failure handling, and final verification.
The user-facing product must explain pending, confirmed, failed, corrected, superseded, and revoked states without hiding uncertainty.
06 / Disclosure access
Disclosure access
OCO defines public views, private owner views, verification pages, APIs, explorers, download rules, redaction, and the difference between record proof and confidential source material.
The system must let approved users verify the record without giving everyone the private operating file behind it.
07 / Operations and recovery
Operations and recovery
The delivery includes key custody, signer rotation, contract or chain upgrades, indexing, monitoring, backups, archive rules, dispute handling, correction paths, and operational playbooks.
Evidence systems need a recovery plan because permanent records can also make mistakes permanent if correction behavior is not defined.