Cognous Evidence Registry | Open Control Stack | Cognous
Open Control Stack/ Components/ Component 01 Group 01 · Knowledge & Provenance

Cognous Evidence Registry

Register claims and evidence, and keep the whole history.

A protocol and reference implementation for registering scientific claims, linking evidence commitments and preserving revision and lifecycle history. In the accepted slice a local blockchain contract is authoritative for those records, and Evidence Attestation verification runs independently off-chain.

View repository All components
The problem
Inclusion is mistaken for truth

A registry must show who registered a record, what evidence was committed and what changed. Chain inclusion cannot say whether a claim is true or the evidence independent.

With Evidence Registry
Commitments and lifecycle, labeled honestly

Wallet attribution, chain inclusion, signature assurance and scientific interpretation each stay separately labeled.

What it provides
Claim registration

content commitments and wallet attribution recorded through the local contract.

Evidence relationships

supporting and contradicting evidence linked, without turning votes or duplicates into truth.

Revision and lifecycle

prior content preserved through revision, withdrawal and supersession, with explicit ownership rules.

Read-only reconstruction

state and history rebuilt by an indexer with documented reorganization handling.

Attestation binding

content bindings recomputed and issuer signatures verified off-chain with the exact accepted verifier revision.

In the refund workflow

A researcher registers a claim commitment on the local chain and attaches an evidence commitment. An independent reader reconstructs the record, retrieves the expected evidence bytes and checks the signed statement with Evidence Attestation. Withdrawal or supersession preserves history rather than silently replacing it.

Try it

Register a claim, revise it, then reconstruct its full history from the indexer.

Open the repository →
What it does not claim

No public-chain deployment, audited production contract, remote consensus finality, authenticated RPC verification or on-chain attestation-verification bridge. Legacy FastAPI and store surfaces are non-authoritative demonstrations, and reputation-weighting goals are not implemented guarantees.