Development record
2026-08-22 — Interview-workstream records filed (the 2026-08-22 handover's
2026-08-22 — Interview-workstream records filed (the 2026-08-22 handover's
items 5-9, three itd-84 hand-runs graded into the calibration note):
itd-142 (the brief-creation interview) filed as a DRAFT with its spec
explicitly waiting until the collaborating prototype has run once — no
speccing ahead of that run; adr-50 + brief invariant 14 (framing traces
never enter the record, automated reviewers never read them; local side
lives in .abcd/.work.local/); principle widen-options-never-recommend (at
most three construals, ceiling not target, null always available, no
recommendation markers); itd-143 (framing chapter under 01-product/, with
its brief-lifeboat mapping row) — itd-142 refines itd-90, surfaced by
the candidate pass before minting; adr-51 + intent-template additions
(optional Mechanism and Scope Conditions sections, enforcement an
explicitly deferred discipline question); hold-route seed
iss-2608220750029991 stays OPEN (RFC-vs-intent undecided, tied to the
hold-register home question now recorded in the evidence chapter);
glossary README names the glossary a deliberate frame surface;
ACKNOWLEDGEMENTS credits mattpocock/skills for the glossary format and
the frontier-questioning pattern in the change that adopts it. Open
sign-offs carried in itd-142's Open Questions: the escalation rule,
one-vs-three intents at the final round, a held working-principle at the
final round.
Frontmatter
| id | dcn-2608220000000007 |
|---|---|
| type | decision |
| date | 2026-08-22 |
.abcd/work/decisions/dcn-2608220000000007-interview-workstream-records-filed-the.md
open on GitHub ↗ · commit history ↗
mentions7
- adr-50Framing traces never enter the record, and automated reviewers never read them
- adr-51An intent can declare its mechanism claim and its scope conditions
- iss-2608220750029991capture's triage routes (defect fix / promote to intent / brief fix / wontfix) force frame-level unease into artefact-level fixes: there is no hold route for a finding whose real content is that the framing itself cannot yet be articulated. A hold-with-axes route is missing — non-articulation is data, holds carry axes and exit by articulation. Candidate RFC or intent; decompose before filing. Ties to the 03-evidence placeholder resolution (where would a hold-register-shaped record live?).
- itd-84An Intent Is Decomposed Before It Is Filed, And A Reversal Is Only Ever Flagged
- itd-90The Product Thinker Is Handed Exactly The Questions Only They Can Answer — And Nothing Else
- itd-142The brief-creation interview: abcd elicits a repository's brief in a staged conversation — narrative first, then frontier rounds that ask only what the record cannot yet settle, options at conjectural questions (at most three candidate construals, a ceiling not a target, with a null answer always available), and a per-item confirmation — distilling committed products into the brief and a ledger while the transcript is discarded. Entry is one door for both modes: a brownfield repository arrives pre-populated from embark probe coverage, provenance-stamped and still requiring confirmation; a greenfield repository is the same interview run from the all-blank coverage state. Command-shaped, because it mutates state — abcd ships zero skills
- 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