Work about abcd itself goes to abcd as a report, never into a managed repository's own plans

Press Release

In a repository abcd manages, a plan or issue that changes abcd itself (its commands, checks, hooks or pages) belongs to abcd, filed as a report, while what the repository decides about its own use of abcd stays in the repository and cites the report. abcd keeps such work out of the repository's own record three ways: it teaches the convention in a bundled rule recalled on intent, capture and decomposition work; decomposition routes a part that changes abcd's own surfaces to a report by default, and a decision to keep it in the repository is recorded with its reason; and intent and capture warn, without refusing, when the text names abcd's own surfaces, naming the report route. Product thinker's ruling 2026-10-07 (interview on iss-2610071538088019, promoted from a managed repository's report): teach, redirect and warn, all three.

Why This Matters

Why this matters to the user — replace before planning.

Mechanism

Prompted (the claim-recording gradient): why the authors expect this to work, as a falsifiable "we expect X because Y" — not the outcome restated. Replace this line with the claim, or with the exact token None stated. alone on its line to record the claim as considered and declined.

Scope Conditions

Required (the claim-recording gradient): the population, platform, scale, or assumptions this claim holds under, one per top-level bullet — abcd intent plan stamps each with a persistent identity. Replace this line with those bullets, or with the exact token None stated. alone on its line.

Acceptance Criteria

Required (the itd-1 discipline): add at least one Given-When-Then bullet describing the verifiable bar for "shipped" before this draft can be planned.

Open Questions

None recorded yet.

Audit Notes

Empty. Populated by intent-auditor when intent moves to shipped/.