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
I0205
Declare the clamp as a doctrine so the mapping and the adapter cannot drift
Where it stands
devtask.issue- Readiness
- blocked 1 of its dependencies is not DONE
- Status
- BLOCKED
- Can start
- not now
- Milestone
- Milestone status
- PLANNED
- Wave
4- Waiting on
- Holds back
- Behind it in all
1- Evidence
0of2
| In the way | Subject | Detail |
|---|---|---|
| issue | I0204 | I0204 is not DONE |
Moves
plan.transitionWhat it is
- Objective
- Declare the rule that every applied limit is derived from the declared mapping as a doctrine with its own validator, dispatched from the registry, reaching the command that claims to run it, covered by a case and run in CI.
- Why
- A new enforced rule that lives as an inline check inside a command is invisible to doctor and to the doctrine list, and drifts the first time somebody edits the adapter. The registry is the only place a rule can be proven to be wired.
- Now
- One adapter applies one derived limit. Nothing refuses an adapter that stops consulting the mapping, and nothing lists this rule among the rules the repository enforces.
- Wanted
- The rule appears in the doctrine list, a refusal names it, doctor proves it reaches its command and that a case covers it, and CI runs that case.
- Done when
- unknown: the record declares no `completion`
- Risk
- A blocking doctrine over a provider-specific adapter can refuse work in a repository whose provider changed underneath it; whether it blocks or advises is decided against that, and recorded.
Acceptance
- The doctrine is declared in the registry with its validator, and doctor fails if either half is missing
- An adapter that applies a value the mapping does not derive is refused, and the refusal names the doctrine
- A case covers the refusal and CI runs it
- Validation
bash test/run.shbin/majordomus doctor- Evidence required
suitedoctor- Evidence present
- unknown: the record carries no `evidence` entries
Scope
- Touches
sharelibtest/cases- Not
Blocking on anything a worker cannot fix from inside the repository- Depends on
- Priority
- p2
- 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.