Development record
the 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
issueopenminoriss-390
the 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
Evidence
.abcd/development/principles/README.md:24-25— "The moment a principle gains a mechanical gate (a lint code, a hook, a CI check), it is promoted to a discipline-kind intent … this directory is the not-yet-enforced layer."- dcn-2607290000000001 — the iss-154 allowlist-inversion lint's shipping "promotes the principle to a discipline".
- The trigger fired (the lint is armed in
repolint), yet.abcd/development/intents/disciplines/holds only itd-1, itd-5, itd-37, itd-79, itd-81, itd-84 — no intent for examples-use-reserved-identifiers. - Refuter verdict: CONFIRMED (minor, process) — the promotion is pre-decided by two records, not an open design question. Minting a discipline-kind intent is a maintainer ceremony (an intent record, not an issue fix), so this record stays open as the tracker rather than being resolved by the autonomous round; iss-389 fixed the principle file's false prose in the same round.
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-390 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-390-the-pre-decided-promotion-of-examples.md
open on GitHub ↗ · commit history ↗
mentions13
- dcn-26072900000000012026-07-29 — privacy-leak follow-up: illustrative machine identifiers in anything committed or published always come from reserved documentation ranges (RFC 5737 IPv4, RFC 3849 IPv6, RFC 2606 domains, RFC 7042 MACs; hostnames derived from the persona registry, e.g. alice-laptop) — the itd-79 persona rule applied to infrastructure. Recorded as principle `examples-use-reserved-identifiers`; enforcement is the iss-154 allowlist-inversion lint (flag any identifier OUTSIDE the reserved ranges), whose shipping promotes the principle to a discipline. No new intent: real private identifiers are itd-74's banlist territory — the incident evidence extends itd-74's scope to machine identifiers (iss-158) rather than founding a second primitive. Incident issue text deliberately names no repo and no values (shape only), so the ledger itself cannot re-leak.
- dcn-26082000000000082026-08-20 — Bug-hunt round 3 (hunt B), branch bughunt-b/round-3. Baseline
- dcn-26082600000000072026-08-26 — Bug-hunt round 9 (bughunt-b): baseline green on the unshallowed
- examples-use-reserved-identifiersExamples use reserved identifiers
- iss-154privacy-hygiene detects only absolute home paths — no network-identifier patterns (IPv4 incl. CGNAT/tailnet 100.64/10, hostnames, device names, ports-in-context). Field incident: an agent committed a Tailscale investigation (tailnet IP, two device hostnames, firewall posture, service port, presence/away patterns) into a public repo's committed tier and audit passed it silently. The v1 deferral note names only emails and private-repo names; network identifiers are not even recorded as deferred.
- iss-389the examples-use-reserved-identifiers principle still says a fixture-identifier lint would make it a discipline — the allowlist-inversion lint shipped (iss-154) and cites the principle by name, so the Promotion paragraph misdirects an agent to build an existing rule
- iss-2608261338035835the-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.
- itd-1Every Intent Has Acceptance Criteria; Every Audit Verifies Them
- itd-5Every Agent Prompt Carries Its Version, Earns Its Lock, And Survives Injection
- itd-37Every Spec Externalises How It Should And Shouldn't Be Modified
- itd-79Personas Come From the Registry; the Role Picks the Name
- itd-81No Judge Ships Unmeasured, And A Clean Diff Is A Result
- itd-84An Intent Is Decomposed Before It Is Filed, And A Reversal Is Only Ever Flagged