Events and the hash chain

link to this sectionEvents and the hash chain

Every protocol action - claims, evidence, runs, verifications, challenges, frontier publications - lands on an append-only chain of signed events.

link to this sectionEvent anatomy

Each event carries:

• a stable event_id;
• an event_type (for example claim.created, evidence.linked,

verification.completed, frontier.snapshot_published);

• the acting actor id;
• a JSON payload with the action specifics;
• a hash, its parent hashes, and a signature.

Natural language first: the audit page shows the type, actor, and time prominently, with hashes and signatures folded one layer down per event.

link to this sectionReading the chain

Parents tie an event to its predecessors, so the chain is verifiable without trusting the server: fetch the events, recompute, compare. Merkle checkpoints bundle ranges of the chain into inclusion proofs for frontier snapshots.

link to this sectionAccess

The event audit lives at /events with deep-link filters (objectType, objectId, actorId, eventType, and time bounds). The API exposes the same reads for programmatic audit.