Engineering record — internal detail. The manual is authoritative for product behaviour.
Engineering5 min read
Delivery log
The per-task execution reports that record what each agent run actually changed, kept alongside the dated plans.
ForEngineer
What this is
Alongside the dated plans, each execution run leaves a short task report recording what was actually changed. They are the audit trail of the build: the plan states intent, the report states outcome. They live in .superpowers/sdd/ and are named by task id.
| Report | Task group |
|---|---|
| task-0-report.md | Foundations and setup |
| task-2-1 … task-2-7-report.md | Second workstream, seven tasks |
| task-4-1 … task-4-4-report.md, task-4-report.md | Fourth workstream, four tasks plus summary |
| task-5-report.md, task-5-6-report.md | Fifth workstream |
| task-6-report.md | Sixth workstream |
| task-7-10-report.md | Seventh workstream, tasks seven to ten |
| task-8-report.md | Eighth workstream |
| task-11-14-report.md | Eleventh to fourteenth tasks |
How to read the build history
- Start with the dated plan for the workstream to understand the intent and the acceptance criteria.
- Read the matching task report to see what actually landed and where the plan changed.
- Where a report and a plan disagree, the report reflects the shipped state.
- The manual is the customer-facing consequence; this log is the engineering evidence behind it.
Source records
- Reports
- .superpowers/sdd/task-*-report.md