Skip to content

spec: version 1.6 - the fourth released proposal wave becomes a new version - #58

Open
delchev wants to merge 1 commit into
mainfrom
spec/v16-release
Open

spec: version 1.6 - the fourth released proposal wave becomes a new version#58
delchev wants to merge 1 commit into
mainfrom
spec/v16-release

Conversation

@delchev

@delchev delchev commented Aug 24, 2026

Copy link
Copy Markdown
Contributor

Folds the fourteen accepted proposals of the 2026-08-24 wave into versions/1.6.md, per the release process (#32): spec text copied to each proposal's declared anchor, Appendix A rows added, statuses flipped to released in 1.6, README table updated.

New constructs: reports.parameters · kind: statement · kind: subset · {{a|b}} placeholder fallback · fileName · generates step-axis + mode: append · the retired-target guard · sourceStatusOnRetire · inbound accept/map.

Stated precisely (no new construct): rollup update/re-parent recompute · settlement recompute on correction · expansion reconcile + master-delete · aggregate moved-key repair bound to every writer.

Release-editorial decisions to review:

  1. Three proposals (0021-financial-statement-definitions, 0024, 0025) carry no formal Specification text / Anchor / DSL index sections — their version prose is assembled from their own Expected behaviour / Edge rules normative blocks, verbatim where normative, restructured only.
  2. 0021-rollups-recompute-on-child-update and 0022-rekey-repairs-both-groups amend the same rollups paragraph; 0022 (merged later) tightens 0021's SHOULD on the vacated parent to MUST. The folded text keeps 0021's general rule and 0022's both-parents MUST, dropping the superseded SHOULD clause.
  3. Not folded: 0028-period-locking (reference implementation dirigible#6928 still in review) and 0028-cross-model-rollup-child (dirigible#6930, not started). Statuses set to accepted - awaiting the reference implementation; they head the 1.7 wave.
  4. Housekeeping observed, not fixed here: proposal file numbering collided in the parallel wave (six 0021-*, two 0026-*, two 0028-*). Renaming merged files would break inbound links, so left as-is — the "next free number" rule needs a mechanical guard.

Verified: all 188 intra-document anchors resolve; 1.6 is 1.5 + exactly this wave (180KB vs 150KB).

🤖 Generated with Claude Code

…ersion

Folds the fourteen accepted proposals of the 2026-08-24 wave into versions/1.6.md
(copied from 1.5, spec text inserted at each proposal's declared anchor, Appendix A
rows added, version header written):

New constructs: reports.parameters, kind: statement (financial statement
definitions), kind: subset, print placeholder fallback {{a|b}}, fileName patterns,
generates step-axis + mode: append, the retired-target guard, sourceStatusOnRetire,
inbound accept/map.

Stated-precisely (no new construct): rollup update/re-parent recompute, settlement
recompute on correction, expansion reconcile + master delete, aggregate moved-key
repair bound to every writer (glue preamble).

Release-editorial notes:
- 0021-financial-statement-definitions, 0024 and 0025 carried no formal
  'Specification text' section; their version prose is assembled verbatim from
  their own Expected behaviour / Edge rules normative blocks, restructured only.
- 0021-rollups... and 0022 amend the same rollups paragraph; 0022 (merged later)
  tightens 0021's SHOULD on the vacated parent to MUST, so the folded text carries
  0021's general event-set rule and 0022's both-parents MUST, without the
  superseded SHOULD clause.
- 0028-period-locking and 0028-cross-model-rollup-child are NOT folded: their
  reference implementations are not merged (dirigible#6928 in review; #6930 open).
  Statuses set to 'accepted - awaiting the reference implementation'.

Statuses of the fourteen folded proposals flipped to 'released in 1.6'; README
version table and normative-file pointer updated. All 188 intra-document anchors
verified resolving.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant