Lifecycle records

Day Shift lifecycle records are a chain of evidence and explicit transitions. Each record has one owner, and each mutation is bound to the current artifact revision or a fresh review receipt. A later record consumes earlier evidence without rewriting its meaning.

The ordered chain

1. The task agreement declares scope, evidence profile, acceptance, validation, and recovery in task-definition.md.
2. Readiness review reports blockers without writing; readiness authorization records the selected clean review.
3. An implementation attempt binds a stable attempt_id to the readiness review.
4. Runtime and Hybrid attempts capture baseline attribution before implementation writes.
5. Validation records preserve the validation identity, exact command or imported source, status, scope, observations, and freshness.
6. implementation-summary.md records changed paths, acceptance evidence, deviations, waivers, blockers, and follow-up work for the attempt.
7. Implementation completion, read-only review, disposition, and closeout remain separate transitions.
8. Milestone reconciliation rolls up closed summaries; reconciliation review is read-only and reconciliation acceptance is an explicit receipt-bound write.
9. Metadata synchronization may apply deterministic administrative status changes from clean review evidence. It does not create the substantive evidence it synchronizes.
10. Resume inspection, workflow explanation, and planning next-action derive continuation from current repository records without silently selecting or mutating work.

Receipts prove application

A receipt identifies the exact mutation plan, revision preconditions, intended paths, outcome, and transaction identity. It proves that an authorized apply occurred. It does not independently authorize a different command, widen the affected path set, cure stale evidence, or override a task agreement.

Preview and review outputs are also evidence, but they are no-write records. A preview can authorize its matching apply only when the command contract says so and all revision bindings remain current. A review can authorize disposition or acceptance only through the dedicated explicit transition that consumes its fresh receipt.

Freshness and continuation

Freshness is local to the record that claims it. A validation becomes stale when its observed paths drift. A review receipt becomes stale when the reviewed artifact changes. A baseline belongs to one attempt and readiness checkpoint. Re-open the changed artifact, rerun the owning read-only surface, and continue from the last proven gate.

resume inspect, workflow explain, and planning next-action are advisory. They reconstruct the likely handoff from durable evidence; they do not repair metadata, reopen attempts, accept reconciliation, or close work. See Resume, trace, archive, and release handoff for recovery and Lifecycle records reference for the canonical record map.