Development record
2026-08-30 — Phase 1 adversarial review (ruthless-reviewer, fresh context) findings captured as iss-2608300114352100 (a first name disclosed through a homonym in the session-1 lapse record; the wording is replaced, and the pushed branch's history still carries it until the PR is squash-merged), iss-2608300114357633 (this log contradicting the branch, remedied by the two lines above), and iss-2608300114359543 (record consistency: one role name for the 2026-08-28 rulings, the ratified marker form in itd-143, the framing section statement-first, no adoption-date marker on invariant 15, the phase count, and "Phase 2 planning" reworded so it cannot read as roadmap Phase 2). All three resolved in the same change.
2026-08-30 — Phase 1 adversarial review (ruthless-reviewer, fresh context) findings captured as iss-2608300114352100 (a first name disclosed through a homonym in the session-1 lapse record; the wording is replaced, and the pushed branch's history still carries it until the PR is squash-merged), iss-2608300114357633 (this log contradicting the branch, remedied by the two lines above), and iss-2608300114359543 (record consistency: one role name for the 2026-08-28 rulings, the ratified marker form in itd-143, the framing section statement-first, no adoption-date marker on invariant 15, the phase count, and "Phase 2 planning" reworded so it cannot read as roadmap Phase 2). All three resolved in the same change.
Frontmatter
| id | dcn-2608300000000011 |
|---|---|
| type | decision |
| date | 2026-08-30 |
.abcd/work/decisions/dcn-2608300000000011-phase-1-adversarial-review.md
open on GitHub ↗ · commit history ↗
mentions4
- iss-2608300114352100The session-1 lapse record explains the misread go-ahead as a homonym and thereby discloses a participant's first name; the filing's own 2026-08-29 decision line rules that roles, never names, appear in any record or commit. Found by the Phase 1 adversarial review; the text also reached the pushed filing branch, so the branch history carries it until the PR is squash-merged or the branch rewritten.
- iss-2608300114357633The decision log's last word on two questions is the opposite of what the filing branch does: it defers the brief-lifeboat mapping row to itd-143's build while the branch adds the row, and it records the roadmap phase home as deferred while the branch authors Phase 7 on a facilitator ruling that the log never records. Append-only, so the remedy is appended lines carrying both rulings.
- iss-2608300114359543Record consistency findings from the Phase 1 adversarial review: itd-142 and itd-143 attribute the 2026-08-28 rulings to a third role name; itd-143 still describes the not-yet-real marker as pending in a form the same filing ratifies differently; 06-framing.md places a dated preface between the Construal heading and the token, so the section is not statement-first as its own rule and itd-143's projection criterion require; invariant 15 carries an adoption-date marker no sibling carries; 04-scope.md line 24 still counts seven phase docs; Phase 7 and the log say 'Phase 2 planning' where roadmap Phase 2 is a shipped phase; the phases README says phases 1-6 are organised by capability moment; the lifeboat mapping comment counts 23 rows.
- itd-143The brief gains a framing chapter under 01-product/ — the macro-why home: one section holds the project's framing, the why behind the why, and receives the brief-creation interview's committed framing products; the brief-lifeboat mapping gains the matching row so a lifeboat carries framing like any other section