Development record
the-record-lands-with-the-act names an armed rung in present tense and its promotion never fired. The principle's Promotion paragraph states 'The armed rung is make lint-issues, a CI step and a pre-push gate' — verified true: RS001-RS003 live in scripts/check-issue-resolution.sh, wired at Makefile lint-issues and included in preflight. Per the principles README promotion contract (enforced principle -> discipline-kind intent), the gate shipping should have minted a discipline; none exists. Third instance of the promotion-pipeline class alongside iss-390 (examples-use-reserved-identifiers) and iss-2608261041210476 (spec-moves-with-the-surface), and the only one with no ledger record until now. The class evidence is now three: the promotion ritual that only a human can perform is the step that gets skipped, which is the-record-lands-with-the-act applied to its own pipeline.
the-record-lands-with-the-act names an armed rung in present tense and its promotion never fired. The principle's Promotion paragraph states 'The armed rung is make lint-issues, a CI step and a pre-push gate' — verified true: RS001-RS003 live in scripts/check-issue-resolution.sh, wired at Makefile lint-issues and included in preflight. Per the principles README promotion contract (enforced principle -> discipline-kind intent), the gate shipping should have minted a discipline; none exists. Third instance of the promotion-pipeline class alongside iss-390 (examples-use-reserved-identifiers) and iss-2608261041210476 (spec-moves-with-the-surface), and the only one with no ledger record until now. The class evidence is now three: the promotion ritual that only a human can perform is the step that gets skipped, which is the-record-lands-with-the-act applied to its own pipeline.
Remedy grounds (2026-09-29)
- Why: the promotion contract in principles/README.md (an enforced principle is promoted to a discipline-kind intent) and the itd-79 precedent give the fix; the ruling on who performs the ceremony is unanswered, so no answer is picked.
- Rejected: an agent lane retiring the principle unasked, which the record itself routes away from as a governance act.
Frontmatter
| id | iss-2608261338035835 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2608261338035835-record-lands-with-the-act-promotion.md
open on GitHub ↗ · commit history ↗
mentions3
- iss-390the pre-decided promotion of examples-use-reserved-identifiers to a discipline-kind intent never happened — the iss-154 lint shipped, the principles README contract says a mechanical gate promotes the principle, and no discipline intent exists
- iss-2608261041210476The principle spec-moves-with-the-surface names a promotion trigger that is already armed, yet sits unpromoted in the not-yet-enforced layer. The principle says a record-lint cross-check (every entry under commands/ and skills/ resolves to a brief surface row) WOULD promote it to a discipline; that is exactly surface_coverage Direction B, armed at blocker (lint.go, record-lint.json), documented live. principles/README.md makes promotion unconditional once any mechanical gate lands (the file is then retired to a discipline-kind intent, as itd-79 personas did), but no discipline intent exists for this principle and the file was never retired. The conditional 'would promote' predates the gate and was left stale — the inverse of the phantom-gate family (it understates its own enforcement). RECORDED NOT FIXED this round: the correct remedy is a governance act (mint a discipline-kind intent and retire the principle file, per the itd-79 precedent), which needs the maintainer rather than an autonomous edit. Proposed: promote per principles/README, or if promotion is deliberately deferred, record why on the principle.
- itd-79Personas Come From the Registry; the Role Picks the Name