Development record
Two records build and publish a managed project's record site at each release by different routes: the shipped provider adapter, and the planned GitHub Pages route
Two records build and publish a managed project's record site at each release by different routes: the shipped provider adapter, and the planned GitHub Pages route
A scope leakage (severity major) found by the cross-document consistency pass.
- End A:
.abcd/development/intents/planned/itd-2610091010348892-anyone-who-opens-abcdev-app-finds-the.md:20— "The project's own workflow builds it and GitHub hosts it; abcd runs nothing." - End B:
.abcd/development/intents/shipped/itd-2609061543533170-abcd-sets-up-a-managed-repository-s.md:42— "one adapter ships (the provider abcd's own site uses); a second is a later intent, not a change to the verb"
itd-2609061543533170 shipped one verb that sets up a managed repository's site through a provider adapter, the provider abcd's own site uses. itd-2610091010348892 publishes an opted-in project's record on its own GitHub Pages through the project's workflow, with abcd running nothing, and moves abcd's own record to that route. Neither record names the other, so the same ground is covered twice with different hosts.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 1215.
Deferral 2026-10-27
Deferred past v0.15.1: Deferred by the product thinker on 2026-10-27 (dcn-2610271112330536): the brief's single-home rewrite (dcn-2610271112339516, dcn-2610271112330235) rewrites or removes most of the passages this record quotes.
Frontmatter
| id | iss-2610262044347395 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | major |
.abcd/work/issues/open/iss-2610262044347395-two-records-build-and-publish-a-managed.md
open on GitHub ↗ · commit history ↗
References2
- itd-2609061543533170One verb takes a managed repository's site from the checkout to a live addressrelated
- itd-2610091010348892An opted-in project's record is built at each release onto its own GitHub Pagesrelated
mentions3
- dcn-26102711123302352026-10-27 — The product thinker ruled on 2026-10-27 that the design brief shows the target design, in the present tense, with a status tag where a part is built, rather than the shipped state. With the ruling that behaviour lives in the command pages, the brief holds the product as aimed for and why, and the command pages hold what abcd does today. This reverses itd-147's currency rule, so a superseding ADR is owed, and the brief's checks are rebuilt around the status overlay.
- dcn-26102711123305362026-10-27 — The product thinker accepted on 2026-10-27 the triage of the 1301 records the 2026-10-26 consistency pass filed. The duplicates, the records a later record already settles, the ones that are no contradiction and the one already fixed are closed with each reader's reason. Every other record gets its fix as its remedy, the rulings' accepted answers included, so a drain can take it. The 45 major records left open are deferred past v0.15.1, because the brief's single-home rewrite rewrites or removes most of the passages they quote. The person ruled the major rulings one at a time; the minor rulings take their recommended answers.
- dcn-26102711123395162026-10-27 — The product thinker ruled on 2026-10-27 that each abcd command's behaviour is written once, in its command page, which agents follow when they run it. The brief's chapter for the command keeps why the command exists, its trade-offs and why it refuses what it does, with its sub-verb table and generated appendix, and points to the command page for behaviour. The documentation-fidelity check moves to the command pages. This reverses the behaviour half of adr-2609231028044006 and invariant 18, so a superseding ADR is owed.