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
I0504
Prove the recommendation is advisory and publish it as such
Where it stands
devtask.issue- Readiness
- blocked 1 of its dependencies is not DONE
- Status
- BLOCKED
- Can start
- not now
- Milestone
- Milestone status
- BLOCKED
- Wave
3- Waiting on
- Holds back
- none
- Behind it in all
0- Evidence
0of2
| In the way | Subject | Detail |
|---|---|---|
| issue | I0503 | I0503 is not DONE |
| milestone | routing-recommendations | the milestone routing-recommendations waits on an outcome of its own |
Moves
plan.transitionWhat it is
- Objective
- Prove with a case that a recommendation never changes the profile a task runs under, and publish the routing claim stating that Majordomus recommends and does not route.
- Why
- The distance between recommending a profile and selecting one is one convenience commit wide. A case is the only thing that keeps it, and the claim is where a reader is told which side of the line the tool is on.
- Now
- The command answers with a profile and a basis. Nothing proves it cannot act on its own answer.
- Wanted
- A case starts a task after a recommendation and shows the profile is whatever the worker asked for, and the claim says recommendations only.
- Done when
- unknown: the record declares no `completion`
- Risk
- A tool that recommends is one flag away from a tool that decides; the case is the record of the decision not to add the flag.
Acceptance
- A case shows a task starting under a profile different from the recommended one, unimpeded
- The claim cites an implementation path and a test path that both exist and says recommendations only
- The generated site data regenerates with no stale file
- Validation
bash test/run.shscripts/generate-site-data --check- Evidence required
suitedocs_build- Evidence present
- unknown: the record carries no `evidence` entries
Scope
- Touches
test/casesdocssite/data/generated- Not
Any automatic application of a recommendation, behind a flag or otherwise- Depends on
- Priority
- p3
- Profile
- implementation
- 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.