Audit trail

Evolver uses a single-writer, append-only root event stream. Each record has a continuously increasing seq, and each append is followed by fsync. Strict reads check invalid JSON, ordering conflicts, and sequence gaps.

The current implementation does not define this log as a SHA-256 hash chain. Its audit properties come from ordered append-only writes, strict reads, and replayable records; do not describe it as a chain signature that does not exist.

Events and materialized views

The event stream is the audit source. Counts and timelines are rebuildable materialized views. To repair derived views, run:

evolver replay

replay reads events and rebuilds local materialized views. It does not revert source code, restore an asset, or undo an external side effect. Back up the event files and ensure no other process is writing before using it.

Integrity checks

evolver retention

Retention checks detect gaps, conflicts, and integrity problems. Destructive deletion remains disabled, so this command must not be treated as a history-cleanup operation.

Audit a decision

1. Locate events by asset ID, task ID, or time window.
2. Follow seq through candidate creation, validation, review, promotion, revocation, and reuse feedback.
3. Cross-check events against file diffs, validation output, and Hub request evidence.
4. On a gap, stop promotion, copy the evidence, and determine whether a write interruption, damaged file, or mixed home directory caused it.

Related pages

• Candidate lifecycle
• Backups

EvoX Docs · Security · Asset trust