remaining-work

remaining-work

Measure what the code delivers, not what a status document reports. The order is audit, plan, split, detail.

Files

File	Content
{{PLANNING_DIR}}/audit/rows.jsonl	One JSON row for each requirement
{{PLANNING_DIR}}/audit/state.json	The commit and the date of the last run
{{PLANNING_DIR}}/completion-plan.md	The CP view

Row keys: id, status, percent, evidence (a file:line), missing, date. status is done, partial, skeleton, gap, gated or not_audited. The rows are the deliverable. Every percentage and every item comes from them. The report is a view of the rows.

1. Audit

1. Extract the requirements from {{OPENSPEC_DIR}} with a script. Compare the total with the last count. A different total means that the extractor broke.
2. Map the code: modules, routes, jobs, tables and screens. Keep backend and frontend apart.
3. Rate each requirement. It is done only when the code is wired and tested.
4. A status document, a task checkbox, a type or a schema-only table is not proof. An API with no screen is not delivered.
5. gap means unbuilt. gated means blocked on a decision or a credential.
6. Run a second pass that tries to refute each done. It may lower a status. It may not raise one.
7. A claim with no file:line becomes gap. Open each cited file:line after the run.
8. An agent that returns no row leaves not_audited. Never average over missing rows.

Extraction traps:

• A duplicate id in one file is a redefinition. Keep the first position. The later text wins.
• Match every id prefix family. Match lower-case suffixes such as -004b.
• Take every table row whose first cell is a valid id. This includes appendices.
• Exclude a requirement only on a structured marker, never on prose.

2. Refresh

Audit again only what moved. Carry every other row forward with its original date.

1. These changes put a requirement back in scope: its text changed, it is new, or a file that its evidence cites changed.
2. New code that no row cites needs a discovery pass. Group it by directory. Ask whether it implements a gap requirement.
3. Name the pivot files, such as a root module or a shared schema. They inflate the scope.
4. Before a fan-out, state the scope and the cost in one line. Wait for a yes.
5. If nothing moved, say so and stop.
6. Report the movement: rows audited again, advances, regressions, the old and new percent. Separate fresh rows from carried rows.
7. Say that this is static analysis. Neither the app nor the tests ran.