Re-score item 373 at L 4 and S 6 after the first read of the code
CI / tests (pull_request) Successful in 3m6s
CI / tests (pull_request) Successful in 3m6s
This commit is contained in:
@@ -2152,3 +2152,20 @@ Read most (opens and searches):
|
||||
- `bin/mattermost_dm/dm.py` 3
|
||||
- `.gitignore` 2
|
||||
- `bin/loop_claude/direct_message.py` 2
|
||||
|
||||
## Reading cost, chunk f2d04ba767bd, finished 2026-11-15T01:11:32Z
|
||||
|
||||
85940 new input tokens before the first commit.
|
||||
|
||||
Read most (opens and searches):
|
||||
|
||||
- `bin/larv_review/test_larv_review.py` 8
|
||||
- `bin/larv_review/reviewer_header.py` 5
|
||||
- `bin/plan_store/stores.py` 4
|
||||
- `README.md` 3
|
||||
- `skills/larv-review/SKILL.md` 3
|
||||
- `skills/larv-review/review-findings.md` 3
|
||||
- `todo.md` 3
|
||||
- `agents/principles-auditor.md` 2
|
||||
- `bin/larv_review/main.py` 2
|
||||
- `bin/larv_review/plan.py` 2
|
||||
|
||||
@@ -12,12 +12,12 @@
|
||||
|
||||
| ID | Release | Blocked by | Exempt | Item | L | E | I | R | S | Moves | Score |
|
||||
|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||
| 373 | 0.11.0 | | | **Pick the next release's chunks that may run at once by the files and the parts of files each is predicted to touch, and record the prediction beside what each merged chunk touched.** | 3 | 2 | 2 | 5 | 5 | 1.5 by 4, 1.4 by 2 | 1.3 |
|
||||
| 352 | 0.11.0 | | | **Write a project's plan to its Jira epic: file items as child issues, edit those the loop filed, score unscored issues with a comment, and move a finished item to the status its config names.** | 3 | 2 | 3 | 6 | 5 | 1.6 by 6 | 1.2 |
|
||||
| 355 | 0.11.0 | | | **Store a record on the Confluence Cloud page its config names, as markdown converted through the adf-codec shim, and interrupt the human when a teammate saved the page since the loop read it.** | 3 | 2 | 3 | 6 | 5 | 1.6 by 6 | 1.2 |
|
||||
| 356 | 0.11.0 | | | **Hand reviewers the review standards from the folder a project's config names, in place of `~/.claude/skills/larv-review/standards/`.** | 2 | 2 | 3 | 5 | 2 | 1.6 by 3 | 1.1 |
|
||||
| 372 | 0.11.0 | | | **Key loop-claude's session, archive, routing state and config-folder commits per chunk, so two chunks of one project run side by side without touching each other's state.** | 3 | 2 | 3 | 6 | 6 | 1.5 by 3 | 0.4 |
|
||||
| 374 | 0.11.0 | 372 | | **Merge open chunks one at a time: rebase, finish the item in todo.md and CHANGELOG.md, rerun the gate and the paired ruling, and keep a chunk waiting for approval in the queue without blocking the next.** | 4 | 2 | 3 | 7 | 6 | 1.5 by 4, 1.6 by 3 | 1.0 |
|
||||
| 373 | 0.11.0 | | | **Pick the next release's chunks that may run at once by the files and the parts of files each is predicted to touch, and record the prediction beside what each merged chunk touched.** | 4 | 2 | 2 | 6 | 6 | 1.5 by 4, 1.4 by 2 | 0.8 |
|
||||
| 359 | 0.11.0 | | | **Tie a project's releases to what its config names: semver tags, Jira Fix Versions, sprints, or none.** | 3 | 2 | 3 | 6 | 4 | 1.6 by 3 | 0.8 |
|
||||
| 375 | 0.11.0 | 372, 373, 374 | | **Run up to the project's configured number of chunks at once, each in its own window of one tmux session named for the project, mark a window whose chunk waits for the human, and refuse to start without tmux at the needed version.** | 4 | 2 | 3 | 7 | 7 | 1.5 by 7 | 0.6 |
|
||||
| 319 | 0.12.0 | | | **Start a fresh session with a brief of the chunk when a rung step changes the worker's model, in place of resuming the old session.** | 3 | 2 | 3 | 6 | 4 | 1.1 by 2, 1.4 by 2 | 1.2 |
|
||||
@@ -78,14 +78,6 @@
|
||||
|
||||
## Details
|
||||
|
||||
### 373. Pick the next release's chunks that may run at once by the files and the parts of files each is predicted to touch, and record the prediction beside what each merged chunk touched.
|
||||
|
||||
lilleman's call, 2026-11-13, splitting item 361. A planning pass, on the project's rung or above, predicts for each item of the next release the files it will touch and, within each file, the parts: a function, a class, a section heading, a table row. It writes the prediction into the item's detail, where `chunk-preflight` reads it. Two chunks may run together where their predicted parts don't overlap, even in one file. `todo.md` and `CHANGELOG.md` don't count, since item 374 writes them at merge time.
|
||||
|
||||
A conflict is not a catastrophe; lilleman expects projects where wall-clock time matters most and tokens spent per hour don't, while tokens per delivered chunk still do (goals 1.4 and 1.5). So the pass picks the set that keeps the most chunks running within the project's parallel limit, item 375's config key, and takes an overlap only where it predicts a small change to the same part. The rules for a chunk hold as today: a chunk takes every item that can share its review, an item with R above 5 forms its own chunk, an item waits while an item that blocks it is still in the plan, and only the next release's items start.
|
||||
|
||||
Record each chunk's predicted parts beside the parts its merged diff touched, so a later item can measure how often the predictions miss and tune the pass. Name the source of each part's boundaries per language, such as the Python `ast` module, or say where the pass falls back to line ranges.
|
||||
|
||||
### 352. Write a project's plan to its Jira epic: file items as child issues, edit those the loop filed, score unscored issues with a comment, and move a finished item to the status its config names.
|
||||
|
||||
lilleman's calls, 2026-11-12. Without asking, the loop may create child issues in the epic, edit the summary, description and scores of issues it created, and comment on and transition any issue in the epic. It never edits the summary or description of an issue a person filed. An issue a teammate files without scores gets scored like any item, with a short comment saying it was scored and why; its scope stays as written. A finished item moves by the transition and to the status the config names, since each Jira workflow differs. An issue the loop files goes into Jira rank by its score among the issues the loop filed. A security finding is filed in the epic like any item, labelled `security` and ranked first, never with a secret's value. R is above 5, so this item ships alone.
|
||||
@@ -114,6 +106,16 @@ Where the rebase conflicts, the chunk's worker resolves it, and only the review
|
||||
|
||||
`bin/chunk_preflight/choices.py:80` `forge_of` is a place the comprehension seats found hard: forge code split across tools. Where this item touches it, build on item 287's forge module if that has shipped.
|
||||
|
||||
### 373. Pick the next release's chunks that may run at once by the files and the parts of files each is predicted to touch, and record the prediction beside what each merged chunk touched.
|
||||
|
||||
lilleman's call, 2026-11-13, splitting item 361. A planning pass, on the project's rung or above, predicts for each item of the next release the files it will touch and, within each file, the parts: a function, a class, a section heading, a table row. It writes the prediction into the item's detail, where `chunk-preflight` reads it. Two chunks may run together where their predicted parts don't overlap, even in one file. `todo.md` and `CHANGELOG.md` don't count, since item 374 writes them at merge time.
|
||||
|
||||
A conflict is not a catastrophe; lilleman expects projects where wall-clock time matters most and tokens spent per hour don't, while tokens per delivered chunk still do (goals 1.4 and 1.5). So the pass picks the set that keeps the most chunks running within the project's parallel limit, item 375's config key, and takes an overlap only where it predicts a small change to the same part. The rules for a chunk hold as today: a chunk takes every item that can share its review, an item with R above 5 forms its own chunk, an item waits while an item that blocks it is still in the plan, and only the next release's items start.
|
||||
|
||||
Record each chunk's predicted parts beside the parts its merged diff touched, so a later item can measure how often the predictions miss and tune the pass. Name the source of each part's boundaries per language, such as the Python `ast` module, or say where the pass falls back to line ranges.
|
||||
|
||||
Re-scored 2026-11-15 from L 3 and S 5, after a read of the code: it adds a new package that maps a diff to parts, changes chunk-preflight, and adds a record writer that reads todo.md's history, so several components, a new tool and S 6, which is L 4.
|
||||
|
||||
### 359. Tie a project's releases to what its config names: semver tags, Jira Fix Versions, sprints, or none.
|
||||
|
||||
lilleman's call, 2026-11-12: what a release is differs per client. With none, items name no release, and the architecture and principles passes the release review runs need another trigger, which this item settles and records. Readers: `rank_todo.py`'s release order, chunk-preflight's next release, loop-claude's "release ready to cut", larv-review's release review, `CLAUDE.md` → "Working loop". Cutting a release stays the human's.
|
||||
|
||||
Reference in New Issue
Block a user