Lifecycle records reference

This reference maps each lifecycle record to its canonical owner and mutation boundary. Command options evolve; inspect the shipped command descriptor for exact flags, but preserve these ownership rules.

Record	Canonical owner	Producer or transition	Consumer	Boundary
Task agreement	task-definition.md	task scaffolding and explicit task updates	readiness and implementation	Approved scope; not execution evidence
Readiness review	review receipt	task readiness-review	task readiness-authorize	Read-only, revision-bound
Readiness authorization	task metadata	task readiness-authorize	task attempt-open	Explicit write
Attempt	summary attempt history	task attempt-open	baseline, validation, completion	Explicit write; preserve prior attempts
Runtime baseline	current attempt	task baseline	runtime attribution and closeout	Post-readiness, pre-write only
Validation result	current attempt	task validation-record	completion and review	Command-owned, manual, CI, or imported provenance
Canonical technical evidence	implementation-summary.md	implementation-summary build plus authored evidence	summary review and reconciliation	Build writes; it does not accept
Implementation completion	current attempt	task implementation-complete	summary review	Changes only implementation status
Summary review	review receipt	implementation-summary review	task disposition and task close	Read-only
Disposition	current attempt	task disposition	closeout or retry	Explicit write
Task closeout	task/summary pair	task close	milestone reconciliation	Receipt-bound terminal write
Milestone rollup	reconciliation.md	reconciliation build	reconciliation review	Build writes a rollup, not a verdict
Reconciliation review	review receipt	reconciliation review	reconciliation accept	Read-only
Reconciliation acceptance	reconciliation	reconciliation accept	parent review and metadata sync	Receipt-bound explicit write
Administrative status	selected overview metadata	metadata sync-status-from-review	planning inventory and continuation	Deterministic explicit write from clean review evidence
Continuation guidance	no persistent authority	resume inspect, workflow explain, planning next-action	operator or agent	Read-only and advisory

Attempt fields

An attempt preserves attempt_id, readiness_review_id, readiness authorization kind, open and close times, implementation_status, validation results, deviations, waivers, blockers, review disposition, and baseline attribution when required. Superseding or retrying creates history; it must not reuse stale review or validation evidence as current proof.

Baseline attribution

The schema-2 baseline binds taskCycleId to the current attempt and checkpointId to its readiness review. It records source revision, working-tree and status digests, CLI identity, declared-target observations, and explicit adoption rationale. Derived runtime attribution lists only fresh runtime-eligible paths that overlap declared targets, plus executable validations and exact acceptance IDs.

Validation identity and freshness

Validation records are append-only identities. A replacement names supersedesValidationId; it does not erase history. Command-owned execution captures argv, exit status, stdout and stderr digests, scope observations, and a validated-state digest. Imported evidence preserves a verified source contract. Any drift in observed paths requires fresh validation.

Review and receipt rules

Reviews never repair, authorize an adjacent write, or synchronize status by themselves. Disposition, closeout, reconciliation acceptance, generic apply, and metadata synchronization each consume the exact receipt their command contract requires. A stale artifact revision invalidates that handoff.

For the operator sequence, use Evidence review and reconciliation. For machine-consumer requirements, use Evidence requirements.