Development record
2026-09-23 — The changelog-as-index ruling of 2026-08-26 includes stale closures (product thinker, ruling on iss-2608260941298050): every terminal transition gets a changelog line, principles and ADRs included and `internal` no longer silenced, and so does an issue closed with no fixing commit. Planned next cycle as its own intent.
decisiondcn-2609230000000007
2026-09-23 — The changelog-as-index ruling of 2026-08-26 includes stale closures (product thinker, ruling on iss-2608260941298050): every terminal transition gets a changelog line, principles and ADRs included and internal no longer silenced, and so does an issue closed with no fixing commit. Planned next cycle as its own intent.
Frontmatter
| id | dcn-2609230000000007 |
|---|---|
| type | decision |
| date | 2026-09-23 |
.abcd/work/decisions/dcn-2609230000000007-the-changelog-as-index-ruling-of.md
open on GitHub ↗ · commit history ↗
mentions1
- iss-2608260941298050the changelog should index every record transition rather than curate a subset, which deletes the inclusion judgement and the reason shipped_in exists. Design decision of 2026-08-26, recorded in [dcn-2608260000000003](../../decisions/dcn-2608260000000003-the-changelog-is-an-index-of-record.md) and resting on the less-but-better principle. Today the cut reads two families (intents/shipped, issues/resolved) and renders only records whose impact is non-internal, so impact carries TWO jobs: it decides the version bump, which it must, and it silences a changelog line, which is a publication judgement bolted onto a product one. checkIssueImpact's own comment names the cost — a rule refusing internal would force work into a user-facing changelog or push authors into a mislabel. Measured consequence of removing the judgement: v0.6.2 saw 175 records enter terminal folders against 98 rendered lines, of which 57 records were internal, so that release becomes roughly 175 entries. Also in scope: principles (30 files) and ADRs (45) are invisible to the cut today, and a new principle is arguably more consequential than half the issues that render. NOT in scope: bundling stays, because one line citing several records that were one user-visible change is fewer lines carrying the same information, which is the better half rather than curation; and impact keeps its version arithmetic. Residue that is NOT a migration artefact and needs a decision: AGENTS.md makes a stale closure legal forever, so some transitions carry no code change even in a greenfield repo, and under this model they render.