Development record
2026-07-17 — Burst 3 (M3, itd-4/spc-6), three record adjudications: (1) AC2's
2026-07-17 — Burst 3 (M3, itd-4/spc-6), three record adjudications: (1) AC2's
resolve note lives as the structured frontmatter scalar resolution: (the
live setScalarField design), not body-appended prose as the AC letter says —
recorded as intentional design evolution, not a gap. (2) AC3 (promote) is a
genuine BLOCKED gap: skill-orchestrated by design but uncompletable with
today's verbs (no intent-create until itd-46; no engine-backed related_intents
back-link write; hand-editing frontmatter from markdown would violate the
engine-backed convention) — spc-6 stays OPEN and itd-4 stays planned on it.
(3) AC4 migration recorded satisfied-by-history (source absent, ledger
populated iss-1..iss-103); no dead migration code built.
Frontmatter
| id | dcn-2607170000000002 |
|---|---|
| type | decision |
| date | 2026-07-17 |
.abcd/work/decisions/dcn-2607170000000002-burst-3-m3-itd-4-spc-6-three-record.md
open on GitHub ↗ · commit history ↗
mentions6
- iss-1launch phase ownership contradicts across the record: phase-1-ahoy.md and build-sequence.md make install plus launch the first milestone, but 04-surfaces/04-launch.md says full launch builds in Phase 5. ADR-bound.
- iss-103gitutil.CheckIgnored returns an empty map for every non-zero git exit, conflating 'nothing ignored' (exit 1) with 'git cannot answer' (exit 128 not-a-repo/corrupt, or git absent). This is intentional fail-open and correct for the audit-rule callers (which guard with InRepo). The one reachable defect was the launch bundle's finalize calling it unguarded, so a git failure silently admitted every gitignored file to the release bundle — that is already fixed (was B18: launch now uses a fail-closed checkIgnoredStrict). Recorded from the multi-agent bug hunt (was B23) for the record: consider lifting a strict, error-returning CheckIgnoredStrict into gitutil so the launch package need not keep its own copy, while preserving the fail-open CheckIgnored for audit. Nitpick / tech-debt; no live defect remains.
- iss-261025221442915506-capture.md:519-527 (§4) keeps the legacy scratch migration as a staged design ('Not built yet ... on first run after install, the command parses a free-form scratch buffer'), while dcn-2607170000000002:14-15 ruled it 'satisfied-by-history ... no dead migration code built' and 05-internals/03-configuration.md:1198-1200 says it 'has nothing left to migrate'.
- itd-4Nothing You Notice Gets Lost
- itd-46`/abcd:intent "<text>"` And `/abcd:capture "<text>"` Become Symmetric Create Paths
- spc-6issue-capture