Development record
The site internals page puts a second-instance demonstration ahead of any repo-agnostic claim; the site chapter already ships site setup for any repository abcd manages
The site internals page puts a second-instance demonstration ahead of any repo-agnostic claim; the site chapter already ships site setup for any repository abcd manages
A sequencing impossibility (severity minor) found by the cross-document consistency pass.
- End A:
.abcd/development/brief/05-internals/10-site.md:109— "the gate adr-47 decision 6 puts in front of any repo-agnostic claim, and the reason none is made here" - End B:
.abcd/development/brief/04-surfaces/22-site.md:48— "Setting up takes a repository abcd manages from the checkout to a live address"
10-site.md says itd-139, the generic explorer demonstrated on a second instance, is the gate adr-47 decision 6 puts in front of any repo-agnostic claim, and that no such claim is made. 22-site.md describes a shipped abcd site setup that takes any repository abcd manages to a live address, and says every repository gets the same pages. The setup verb depends on the genericity that, according to the internals page, has not yet been demonstrated, so it ships ahead of its own gate.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 606.
Frontmatter
| id | iss-2610262035542834 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610262035542834-the-site-internals-page-puts-a.md
open on GitHub ↗ · commit history ↗
mentions3
- adr-47abcdev.app is rendered from this repository alone
- iss-2610262042028384The site chapter says no repo-agnostic explorer claim is made until a second instance proves it; shipped itd-2609061543533170 claims the pages render for every managed repository.
- itd-139Carol's team adopts abcd and gets a readable record the next day, without writing a line of site code