Does this require a token to use?

The programs implement reputation, trust tiers and governance on Solana devnet. The design intent is anchoring and verification, not a tradeable asset.

CCP: Celaya Chain Protocol

What it does

CCP is the settlement layer under EPPE, NOTARY, MORTEM and VERDICT's evidence anchoring. Instead of asking whether a signature is valid, it asks whether an agent is coherent: does its claimed identity, its earned reputation, its declared policy, its actual actions and its biological attestation agree with each other.

Six Anchor programs carry it: registry, identity, coherence, reputation and trust tiers, organizations, governance, and dispute resolution.

In the code

The five axes and their weights, from ccp-coherence

pub const SCALE: u64 = 1_000_000;

/// 5-axis Proof of Coherence weights (sum = SCALE)
pub const W_IDENTITY:   u64 = 300_000;  // 0.30
pub const W_REPUTATION: u64 = 250_000;  // 0.25
pub const W_POLICY:     u64 = 200_000;  // 0.20
pub const W_ACTION:     u64 = 150_000;  // 0.15
pub const W_BIOLOGICAL: u64 = 100_000;  // 0.10

pub const COHERENCE_THRESHOLD: u64 = 600_000;  // 0.60 minimum

Fixed-point integers, not floats, determinism matters when validators must agree. The weights are constants in a deployed program, which means changing what "coherent" means is a governed upgrade with an on-chain record, not a config edit.

How this differs from the ordinary version

Coherence rather than possession

A private key proves possession of a key. It proves nothing about whether the entity holding it has behaved consistently with what it said it would do. Proof of Coherence scores that agreement across five axes and puts a floor under it.

Biological attestation is one axis, weighted lowest

The biological signal, MORTEM's streamed pacemaker and wearable data, is deliberately 10 percent of the score. It is corroboration, not identity. A design that weighted it heavily would be both fragile and invasive.

In the field

Where an anchor beats a database

For most business records a database is the right answer. The narrow case where this is not true is when the party keeping the record is also a party to the dispute, utility infrastructure data, chain-of-custody, environmental readings near a permitted facility. Anchoring a hash makes later revision detectable by someone who does not trust the record keeper.

Questions

Does this require a token to use?: The programs implement reputation, trust tiers and governance on Solana devnet. The design intent is anchoring and verification, not a tradeable asset.