Run a corpus epoch

Corpus transitions are operator-gated scientific migrations. Do not improvise commands from memory; use the versioned runbook shipped with the engine.

Stages

preflight → activate → replay → rebuild → verify

Preflight

Preflight requires a clean code tree and pins:

• engine commit;
• catalog fingerprint;
• replay inventory;
• runtime capabilities;
• protected-store baseline hashes;
• projected replay coverage.

Low coverage requires explicit fresh-start acceptance.

Activation

Activation archives derived state through rename-first operations, preserves scientific records, and sets the target epoch. Use the orchestrator's activation stage so pinned inputs remain available.

Replay and rebuild

Replay refuses records without authoritative fidelity and search metadata. Rebuild admits only eligible active-epoch evidence and generates corpus projections, queues, connections, and reports.

Verification

Verification must reconcile:

• inventory and replay outcomes;
• append-only decisions;
• holdout and protected-store hashes;
• denominator equality;
• eligibility totals and reasons;
• epoch stamps on all active projections;
• approved principles unchanged unless a human separately approved them.

Recovery

Rehearse activation-to-crash recovery on a disposable copy before the real transition. Recovery is for the pre-rebuild state and refuses to overwrite newly populated derived stores.