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
I2075
A candidate is routed by what it is about
Where it stands
devtask.issue- Readiness
- complete completion is recorded and every required evidence token is present
- Status
- DONE
- Can start
- not now
- Milestone
- Milestone status
- DONE
- Wave
2- Waiting on
- none
- Holds back
- none
- Behind it in all
0- Evidence
1of1
Moves
plan.transitionWhat it is
- Objective
- Derive route for every observation candidate from its subject, in ADR 0118's order: command:, capability:, rule:majordomus.*, the vendored rules directory, or the tool's share/ when inside the repository -> platform; another rule: or gate: -> enforcement; a path the scope declares generated or .gitattributes marks merge=derived -> generator; docs/ -> documentation; anything else -> project.
- Why
- A candidate with no owner is read by nobody, and the route must come from structure because ADR 0091 rejected classifying by wording; in an adopter, the project's own share/ is not the tool.
- Now
- No candidate carries an owner.
- Wanted
- Every observation candidate names its route, adopter-correct, and candidates shows it per group.
- Done when
- unknown: the record declares no `completion`
- Risk
- unknown: the record declares no `risk`
Acceptance
- In this repository each of the five routes is reached by a subject of its kind
- In a freshly initialised repository with its own share/, a path under it routes project, and command:, capability: and rule:majordomus.* route platform
- Two observations with different statements about one subject carry the same route
- The derivation emits no event it reads
- Validation
bash test/run.sh 982_a_candidate_is_routed_by_what_it_is_about- Evidence required
candidate_routed- Evidence present
candidate_routed
Scope
- Touches
lib/knowledge.shlib/changed.shdocs/KNOWLEDGE.mdtest/cases/982_a_candidate_is_routed_by_what_it_is_about.sh- Not
- unknown: the record declares no `non_scope`
- Depends on
- Priority
- p1
- 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-10-09
- Updated
- 2026-10-14T23:33:27Z
- Started
- 2026-10-14T23:33:12Z
- Verified
- 2026-10-14T23:33:18Z
- Completed
- 2026-10-14T23:33:27Z
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.