Reusing author journals

A source or grading revision invalidates old execution certificates. You can reuse the legal command journals as preparation inputs, while executing and verifying them again against the successor registration. This saves author planning work; it does not skip simulation, accounting reconstruction, required assessments or counterfactual verification.

From the repository root:

bun run worldseq instances revise private/instances-v1 \
  --out private/instances-v2 --file private/reviews-v2.json
bun run worldseq instances run private/instances-v2 \
  --reuse-from private/instances-v1 --workers 1

The revision must be the immediate successor recorded by the predecessor’s retirement fence. Every registered instance ID, task ID, exact seed and gameplay budget remains unchanged. Adding the 24 contractual/workforce tasks requires the explicit inventory extension, which preserves the original 650 realizations and appends 48 prospective draws. Current case and fairness bindings come from the reviewed successor registration. Already-issued predecessors cannot be migrated.

Before any new result, the command freezes reuse-plan.json in the private successor directory. Every instance has an entry. Selection uses its predecessor’s published certificate witness, or the complete source of its recorded campaign attempt when no certificate exists. An ineligible predecessor source is explicitly an unproven journal; it supplies no passing credit. A missing complete source causes ordinary author construction for that entry. Corrupt sources, mismatched registrations and substituted files fail closed.

For a selected journal, the worker starts a fresh world and submits the unchanged decisions, assessments and waits. It retains a new source, seal and finalization, together with provenance.json, the frozen selection hash and the original replay input. Only a newly eligible trusted finalization can publish a successor certificate. The dashboard receives normal public rollout frames, never the predecessor’s seeds or private witness.

If a changed mechanic rejects an old command, or a new requirement makes its outcome ineligible, the failed attempt remains on disk and in the campaign inventory. There is no automatic rewrite or successful fallback. Continue a paused campaign with the same --reuse-from argument. To explicitly request fresh author construction for failed entries on the same instances:

bun run worldseq instances run private/instances-v2 \
  --reuse-from private/instances-v1 --retry-failed --workers 1

--retry-failed reconstructs failed journals using the current author policy. It retains previous attempts, does not replace seeds, and still requires current certification. Pending entries continue their frozen selection; passing entries are independently checked on resume. You cannot remove or change the reuse directory on an existing campaign checkpoint.

Historical files must remain available and unchanged for the successor campaign’s provenance checks. Archive access is bounded and rejects symlinks. Keep both directories private. Do not manually copy certificates or mark progress entries passed.