Plan #
What didbot-claude has built and what it is building. One file per epic.
Where the reasoning goes #
In the epic, beside the work it justifies. There is no separate decision log.
An epic is a line of work that takes many pull requests and has an exit criterion somebody could check. The tasks live inside it.
What belongs here #
The parts that know about a harness. Nothing here signs, nothing here knows a product's record types, and the socket protocol is versioned as data rather than shared as a type. AGENTS.md says why each of those is a rule rather than a preference.
The id is the commit scope #
Each epic's filename is its id, and that id never changes. plan/harnesses.md
is harnesses, so its commits read feat(harnesses): …. plan is a valid
scope too, for changes to this register.
Status #
shipped — the exit criterion is met. open — being worked on or ready to
be. blocked — waiting on another epic. continuous — never finished.
declined — decided against, kept for the reasoning.
The tables are generated #
scripts/gen-plan-readme.py reads each epic's frontmatter and rewrites what
sits between the <!-- generated: … --> fences. Edit the epics, not the
tables.
Complete #
| id | title |
|---|
Shipped, with loose ends #
| id | title |
|---|
Open #
| id | title | status |
|---|---|---|
| harnesses | What a harness has to provide, measured rather than assumed | open |
| collection | Real sessions reach a receiver, and we find out what breaks | open |
| first-run | A new install says what it will cost, from evidence already on the disk | open |
Continuous #
| id | title |
|---|
Not pursued #
| id | title |
|---|