A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:06:01Z by majordomus 0.29.0. Nothing on this page is read again. See it live
I0501
Group comparable work from what the records already carry
Where it stands
devtask.issue- Readiness
- waiting every dependency is satisfied; the milestone routing-recommendations waits on an outcome of its own
- Status
- BLOCKED
- Can start
- not now
- Milestone
- Milestone status
- BLOCKED
- Wave
0- Waiting on
- Holds back
- Behind it in all
3- Evidence
0of1
| In the way | Subject | Detail |
|---|---|---|
| milestone | routing-recommendations | the milestone routing-recommendations waits on an outcome of its own |
Moves
plan.transitionWhat it is
- Objective
- Derive the grouping that makes two pieces of work comparable from facts the records already hold, so that a recommendation compares like with like without anybody inventing a taxonomy of task types.
- Why
- A recommendation is only meaningful within a class of comparable work, and the obvious way to get one is to invent categories. Invented categories are a new vocabulary nobody validates, which this repository refuses on principle and would regret in practice.
- Now
- Records carry a profile, a declared scope, a verification result and an outcome. Nothing groups them, and nothing says what makes two tasks comparable.
- Wanted
- A derivation produces groups from recorded facts alone, states what it grouped on, and refuses to group where the facts are too thin to support it.
- Done when
- unknown: the record declares no `completion`
- Risk
- A grouping that is too coarse makes every recommendation the same one; too fine and no group ever reaches a usable denominator. Whichever is chosen has to be visible in the output.
Acceptance
- Grouping uses only fields already recorded, and names them in its output
- No new record type or vocabulary is introduced
- Work that cannot be grouped is reported as ungrouped rather than forced into a group
- Validation
bash test/run.sh- Evidence required
suite- Evidence present
- unknown: the record carries no `evidence` entries
Scope
- Touches
libdocs- Not
A hand-written taxonomy of task typesAny new noun; the grouping is a derivation, not a record- Depends on
- none
- Priority
- p3
- Profile
- deep-work
- Parallel safe
- false
- Owner
- unknown: the record declares no `owner`
The work so far
- Branches
- none
- Merged
- none
- Commits
0- Trunk
- master
- Sessions
- none
- Created
- 2026-09-04
- Updated
- 2026-09-04
- Started
- unknown: the record declares no `started_at`
- Verified
- unknown: the record declares no `verified_at`
- Completed
- unknown: the record declares no `completed_at`
Synchronisation
- Adapter
scripts/github-sync- Repository
- unknown: the derived plan's header carries no repository
- External issue
- unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
- State there
- unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
Findings
Nothing is wrong with these records.