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
I0007
Enforce the canonical model as doctrine
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
5- Waiting on
- none
- Holds back
- none
- Behind it in all
0- Evidence
1of1
Moves
plan.transitionWhat it is
- Objective
- Add the project model to the doctrine registry so that doctor reports a broken model and watch reports a model that has drifted, through the same dispatcher every other rule uses.
- Why
- A rule enforced by a script nobody runs is documentation. The doctrine registry is how this repository makes enforcement verifiable end to end.
- Now
- The registry covered policy, profiles, scope, state, notes, projections and retention. Nothing covered the plan.
- Wanted
- majordomus.project-integrity and majordomus.dag-integrity are declared, have validator functions, are dispatched by doctor and watch, and each has a test.
- Done when
- unknown: the record declares no `completion`
- Risk
- A doctrine that fails in a repository without a project model would make every user installation red.
Acceptance
- A repository with no canonical model skips both doctrines rather than failing
- An invalid model is a blocking doctor failure with a reproduce command
- watch reports the same violations as drift
- Validation
bash test/run.sh 44_model_doctrine- Evidence required
doctrine_test- Evidence present
doctrine_test
Scope
- Touches
share/standard/majordomus/lib/doctor.sh- Not
Blocking a commit on a work-in-progress issue; progress is reported, not blocked- Depends on
- Priority
- p1
- Profile
- implementation
- Parallel safe
- true
- 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-04T03:12:58Z
- Started
- 2026-09-04T03:12:56Z
- Verified
- 2026-09-04T03:12:57Z
- Completed
- 2026-09-04T03:12:58Z
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.