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
I1986
The vendored rule package says nothing that is only true of this repository
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
- ACTIVE
- Wave
0- Waiting on
- none
- Holds back
- none
- Behind it in all
0- Evidence
2of2
Moves
plan.transitionWhat it is
- Objective
- Rewrite the baseline rules that describe Majordomus's own history as rules about any adopter. Mark their x-majordomus.tests as upstream proofs so an adopter is not pointed at test/cases it does not have, and give the package manifest a real source revision.
- Why
- In share/standard/majordomus/rules/{adr-integrity,lifecycle-observed,completion-gates,record-changed-files,publication-currency,schema-integrity}.v1.md, 'this repository' means Majordomus. Their tests name test/cases paths absent in OSCILLA. The vendored manifest says source_revision 0.6.0 although OSCILLA vendored it from 0.12. A second adopter saw the same on 2026-10-08: in prismatic-platform, `rules vendor update` moved a 0.6.0 baseline to the 0.14.0 package (3 rules added, 4 changed) and `rules vendor status` still printed 'distribution: 1 (0.6.0)', so the label cannot tell the two packages apart.
- Now
- As above at e08aec8651.
- Wanted
- Adopter-neutral rule text; tests resolvable or explicitly upstream; source_revision equals the release that produced the package.
- Done when
- unknown: the record declares no `completion`
- Risk
- unknown: the record declares no `risk`
Acceptance
- No vendored rule's text names this repository's own incidents as the adopter's
- scripts/rules-package write stamps the producing release as source_revision
- Validation
bin/majordomus plan validateMJ_TEST_JOBS=4 bash test/run.sh <the case this issue adds>- Evidence required
neutral_rule_textsource_revision_stamped- Evidence present
neutral_rule_textsource_revision_stamped
Scope
- Touches
share/standard/majordomusscripts/rules-packagetest/cases- Not
- unknown: the record declares no `non_scope`
- Depends on
- unknown: the record declares no `depends_on`
- Priority
- p2
- 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-10-04
- Updated
- 2026-10-14T14:53:20Z
- Started
- 2026-10-14T14:52:58Z
- Verified
- unknown: the record declares no `verified_at`
- Completed
- 2026-10-14T14:53:20Z
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.