Re-score item 354 at L 4 and S 7 after the first read of the code

This commit is contained in:
2026-11-13 23:39:51 +01:00
parent f69ef96505
commit 854eb63407
+2 -2
View File
@@ -12,7 +12,7 @@
| ID | Release | Blocked by | Exempt | Item | L | E | I | R | S | Moves | Score |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 354 | 0.11.0 | | | **Read and write the decisions, score anchors, comprehension history, reading cost and changelog each through the backend its project's config names, with markdown files as one backend.** | 3 | 2 | 3 | 6 | 6 | 1.6 by 4, code health by 1 | 1.2 |
| 354 | 0.11.0 | | | **Read and write the decisions, score anchors, comprehension history, reading cost and changelog each through the backend its project's config names, with markdown files as one backend.** | 4 | 2 | 3 | 7 | 7 | 1.6 by 4, code health by 1 | 0.7 |
| 364 | 0.11.0 | 354 | | **Read a client repo's own `CLAUDE.md` and `AGENTS.md`, propose to its team each change that aligns them with this setup, and record each conflict left as a decision in the project's records.** | 2 | 2 | 2 | 4 | 2 | 1.6 by 4, 1.2 by 2 | 2.2 |
| 376 | 0.11.0 | | owner | **Make `principles/technical-principles.md` ask for files in folders before comment banners, and for an entry point a newcomer finds at once.** | 1 | 2 | 2 | 3 | 2 | 1.1 by 4 | 1.6 |
| 360 | 0.11.0 | | | **Make `chunk-pr merge` wait for the human approvals a project's config requires, as part of the gate, before it merges.** | 2 | 2 | 3 | 5 | 3 | 1.6 by 5 | 1.6 |
@@ -92,7 +92,7 @@
### 354. Read and write the decisions, score anchors, comprehension history, reading cost and changelog each through the backend its project's config names, with markdown files as one backend.
lilleman's call, 2026-11-12: each record has its own backend setting, so a client project can keep, say, decisions and changelog in Confluence and anchors and comprehension history as files. Which goes where is asked per client at setup. Every tool and agent that reads or writes a record goes through the interface: the judge's records, `rank_todo.py`'s decision check, `todo-item finish --changelog`, larv-review's scoring and places, `score-outcomes`, `rules/decisions.md`. The plan store's contract suite has a twin for records, on fakes. R is above 5, so this item ships alone.
lilleman's call, 2026-11-12: each record has its own backend setting, so a client project can keep, say, decisions and changelog in Confluence and anchors and comprehension history as files. Which goes where is asked per client at setup. Every tool and agent that reads or writes a record goes through the interface: the judge's records, `rank_todo.py`'s decision check, `todo-item finish --changelog`, larv-review's scoring and places, `score-outcomes`, `rules/decisions.md`. The plan store's contract suite has a twin for records, on fakes. Re-scored 2026-11-13 at L 4 and S 7: about 15 modules in 10 packages and 11 agent-facing files read a record, several at a git ref, and the record interface is the first backend interface, since item 350's plan store is not built yet. R is above 5, so this item ships alone.
### 364. Read a client repo's own `CLAUDE.md` and `AGENTS.md`, propose to its team each change that aligns them with this setup, and record each conflict left as a decision in the project's records.