Read plans, tasks, and attempts
Distinguish accepted work intent from immutable execution attempts and outcomes.
Outcome
You can trace an objective through its plan version and task to one immutable attempt without treating an attempt outcome as an editable task record.
Prerequisites
Open a completed deterministic story from projects and runs.
Steps
- Read the plan version ID associated with the run.
- Open the task and compare its title, objective, and phase with the run objective.
- Open the attempt and inspect its immutable state and summary.
- Follow the attempt to the notebook execution and artifact it produced.
The Slice-0 plan has one task. Branching plans, joins, retries, pause, cancellation, and durable multi-attempt orchestration activate in later slices and must pass their own recovery gates before the UI presents them as available.
Verify
The task ID, attempt ID, execution ID, and artifact ID are distinct. Reloading does not rewrite the attempt or reuse its identity for another try.
Recover
If execution fails in a later slice, retain the failed attempt and retry as a new attempt. Never edit a terminal attempt to make the task appear successful.