diff --git a/CHANGELOG.md b/CHANGELOG.md index 632b722..5317364 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -4,6 +4,40 @@ Edit the release descriptors, not this file. The headings from "## 4.7 — The volume layer (boundary charter)" on are a frozen tail, kept byte for byte (canon.yaml, changelog.tail-sha256). --> +## v0.7.0 — Step 1b, map the flow of demand; the PDLC and the SDLC + +2026-11-10 · pre-release · descriptor [`releases/v0.7.0.yaml`](releases/v0.7.0.yaml) + +**Step 1b, map the flow of demand, is a new step card** (`DDD-dec-118`). Adding a card is a +MINOR release (`DDD-dec-82`). **The step is `[PROPOSED]`.** Its place after step 1 and its scope +are ruled. Its procedure, its fields and its worked example are not ruled. + +- **Step 1b** (#68) traces demand across step 1's act map. It records where an item is + sighted, where it enters, who orders it and where it is discharged. Each process declares its + own kinds of demand. The PDLC's kinds are new, owed and own-ground. They are the worked example + and the starting point, and the step does not claim they apply to every process. The step + rests on four claims, `DDD-flow-01` to `-04`. They are projected and scoped to the PDLC. How + the steps are numbered is still open. +- **The PDLC and the SDLC** are new applications (#64; `DDD-dec-114`, `DDD-dec-115`). The PDLC + is the product lifecycle. It has three owners: What, When and How. The SDLC is the How + owner's arrangement within it. It runs from an issue to production, dark behind a toggle. Both + specifications are ruled, by Round 28, and Rounds 29 and 30 settled the forecast. Each + specification carries its act map as graph data, with SHACL shapes and a checker. The + reference workflows are not written. +- **Two open items join `sdlc.md` §19** (#66). They are not rulings. O-8 proposes an act that + accepts the realisation plan before work starts. O-9 asks product-cli either to adopt the SDLC + for its issue sessions or to record where it departs from it. +- **Specification feasibility is ruled** (#63; `DDD-dec-116`). The How decides whether a + dependency on outside ground can be realised loosely coupled, using three conditions that can + be checked. What may be used from the source is the data owner's decision. +- **Grants and roles are ruled** (#63; `DDD-dec-117`). product-cli carries the same grants and + roles as the other systems, which supersedes its `[D1.11]`. `DDD-dec-116` and `DDD-dec-117` + are not yet applied to `what.md`, `how.md`, `authority.md` or product-cli's definition. +- **product-cli's definition** is brought up to sdlc edition 1 (#65). It cites the ruled + validation regime (`DDD-dec-113`). It records edition 1 as shipped in v0.6.0. + +No other step's register moves. The method stays "ready to try (preview)" (`DDD-dec-74`). + ## v0.6.0 — sdlc edition 1: the What's vocabulary and shapes, tagged for product-cli 2026-11-06 · pre-release · descriptor [`releases/v0.6.0.yaml`](releases/v0.6.0.yaml) diff --git a/meta/sessions/2026-11-10-release-v0.7.0/bootstrap.md b/meta/sessions/2026-11-10-release-v0.7.0/bootstrap.md new file mode 100644 index 0000000..b3a8c4e --- /dev/null +++ b/meta/sessions/2026-11-10-release-v0.7.0/bootstrap.md @@ -0,0 +1,45 @@ +# Bootstrap — release v0.7.0, 2026-11-10 + +Filled in at arrival and committed with `prompt.md` as the session's first commit. + +| Parameter | Value | +|---|---| +| Invocation | Interactive. Emil's rulings and his refused `canon release v0.7.0` run are verbatim in `prompt.md` | +| Principal | Emil (sole ratifier; ratifies by landing the branch, then cuts the release) | +| Issue | [#69](https://github.com/mindovermachine-dev/decision-driven-design/issues/69). Every commit of the session carries `Refs #69` | +| Upstream pin | `v5.15.2` (`graph/upstream.yaml`), unchanged by this session | +| Downstream base | `87db443` (`87db443b86712ddc0f678ffc3e2cb3e8ea066e05`), the head of `main` at arrival. **`main` has not moved** from the `87db443` the prompt names | +| Downstream branch | `claude/clever-brown-h3ewei`, from `main` at `87db443` | +| Last release | `v0.6.0`, tag on `1ab1de0` (#59) | +| Model | Claude Opus 5.5 | + +## Gates + +| Gate | What | Who | +|---|---|---| +| G0 | This charter committed before any other change | Claude | +| G1 | The version confirmed from the rules; commit 1, `releases/v0.7.0.yaml` and its `CHANGELOG.md` section from `canon changelog` (the head Emil ratifies); commit 2, `canon ratify v0.7.0`; `scripts/ci.py` and canon's checks green; pushed, pull request opened, CI green | Claude; **stops for Emil** | +| G2 | Confirm `prerelease: true`; land the branch (`canon land`); then, from `main`, `canon release v0.7.0 --plan` and `canon release v0.7.0` | **Emil** | + +## The range at arrival + +`git log v0.6.0..main` holds 38 commits. They came from five pull requests, all landed: + +| PR | What | Decisions and claims | +|---|---|---| +| #64 | The PDLC and the SDLC as applications | `DDD-dec-114`, `DDD-dec-115` | +| #65 | product-cli's definition brought up to sdlc edition 1 | none new (basis `DDD-dec-113`, `-73`, `-72`) | +| #66 | `sdlc.md` §19: O-8 and O-9, open items only | none new (basis `DDD-dec-115`) | +| #63 | Specification feasibility; grants and roles | `DDD-dec-116`, `DDD-dec-117` | +| #68 | Method step 1b, map the flow of demand | `DDD-dec-118`; `DDD-flow-01` to `-04` | + +#67 is an issue (the demand-flow session's), not a pull request. + +## Scope + +In scope: `releases/v0.7.0.yaml`, the `CHANGELOG.md` section that `canon changelog` generates from +it, this session record, and the session's row in `meta/sessions/README.md`. That row and the +record go in before commit 1. The release-head guard allows only the descriptor after the ratified +head (rule 7). + +Out of scope: every claim, decision, step card and specification; landing; `canon release`. diff --git a/meta/sessions/2026-11-10-release-v0.7.0/findings.md b/meta/sessions/2026-11-10-release-v0.7.0/findings.md new file mode 100644 index 0000000..e46ffc1 --- /dev/null +++ b/meta/sessions/2026-11-10-release-v0.7.0/findings.md @@ -0,0 +1,68 @@ +# Findings — release v0.7.0, 2026-11-10 + +## F-1. The version is v0.7.0, from the rules + +**Checked against `DDD-dec-82` and `method/README.md` §Registers.** MINOR moves when a step card +is added or a step's register moves. Below 1.0, everything else is PATCH or nothing. + +- **A card added.** `method/01b-map-the-flow-of-demand.md` arrived in #68 (`DDD-dec-118`), at + `[PROPOSED]`. That alone makes the release MINOR, so `v0.6.0` becomes `v0.7.0`. +- **No register moved.** Across `v0.6.0..main`, the step table in `method/README.md` and + `README.md` gains the 1b row and nothing else. The cards for steps 1 to 10 are unchanged, except + that 1 and 7 each gain one line pointing to 1b. Step 1 stays "Ruled for test". Steps 2 to 10 + stay `[PROPOSED]`. +- **Nothing calls for more.** The version is below 1.0, so MAJOR cannot arise (`DDD-dec-82`). The + new decisions (`DDD-dec-114` to `-118`) and claims (`DDD-flow-01` to `-04`) move no number by + themselves (`DDD-dec-75`). They count only through 1b's card. +- **Noted, not acted on.** `DDD-dec-118` (N-1) records that "the version stays below 1.0 until + all ten steps are ruled" now counts eleven steps, and needs a ruling to say so. This does not + change v0.7.0. It will matter at 1.0. + +## F-2. The prompt calls the specifications `[PROPOSED]`. The repository says they are ruled. Emil to settle + +The prompt says: "Say plainly that the step and the specs are [PROPOSED]." + +**The step is `[PROPOSED]`.** That agrees with the card and with `DDD-dec-118`. Its place and +scope are ruled. Its procedure, fields and worked example are Claude's, +`UNVERIFIED — Emil review`. + +**The PDLC and SDLC specifications are ruled**, according to the repository: + +- `applications/pdlc/pdlc.md` opens with "Register: ruled (Rounds 28 to 30)". +- `applications/sdlc/sdlc.md` opens with "Register: ruled (Rounds 28 and 30)". +- The statements of `DDD-dec-114` and `DDD-dec-115` both say "Round 28 rules the … specification's + proposals as drafted". + +**One index disagrees.** `applications/README.md` still marks `sdlc/sdlc.md` as `[PROPOSED]`. +The `2026-11-07-sdlc-and-pdlc` row in `meta/sessions/README.md` does the same. The row is +historical and describes the session as it first landed. The index line is a stale line, a bug in +the prose (`AGENTS.md`). This session does not fix it: a fix after the ratified head would break +the release-head guard (rule 7), and the line is not the release's to change. + +**What the summary says.** It follows the repository (`AGENTS.md`: "The repo is ground truth"): + +- the specifications are **ruled**; +- step 1b is **`[PROPOSED]`**; +- `DDD-flow-01` to `-04` are **projected**; +- the parts of the specifications that remain proposals are named as such: O-8's plan-acceptance + act, and `DDD-dec-116` and `-117` not yet applied. + +**Another reading.** "The specs" in the prompt may mean the specifications that +`DDD-dec-116` (specification feasibility) governs. Read that way, the prompt and the repository +agree. `DDD-dec-116` and `-117` are ruled, and the changes they call for to `what.md`, `how.md`, +`authority.md` and product-cli's definition are not yet made (S-1 to S-8 in that session's +`successor-items.md`). + +**If Emil wants the PDLC and SDLC called `[PROPOSED]`**, that contradicts `DDD-dec-114` and `-115` +as they stand. It needs a ruling, not a wording change. The summary then changes, which means a +new commit 1 and a new ratification. + +## F-3. `prerelease: true` is Claude's choice, for Emil to confirm + +The prompt says this was asked and not answered. The descriptor says so in a comment, and the +pull request asks for it. + +## F-4. #67 is an issue + +The prompt names "PRs #63 to #68". #67 is the demand-flow session's issue, not a pull request. The +range comes from five pull requests: #63, #64, #65, #66 and #68. diff --git a/meta/sessions/2026-11-10-release-v0.7.0/predictions.md b/meta/sessions/2026-11-10-release-v0.7.0/predictions.md new file mode 100644 index 0000000..2c70a5f --- /dev/null +++ b/meta/sessions/2026-11-10-release-v0.7.0/predictions.md @@ -0,0 +1,17 @@ +# Predictions — release v0.7.0, 2026-11-10 + +Written before each operation. The guard allows only the descriptor after the ratified head +(`spec/release-format.md`, rule 7). So this file is committed before commit 1, and nothing in the +session record can change after it. What was observed after that point is reported in the pull +request and to Emil, not here. + +| # | Operation | Prediction | +|---|---|---| +| 1 | `canon changelog` after writing `releases/v0.7.0.yaml` (no `ratified_head`) | Writes a `## v0.7.0 — …` section above v0.6.0's, marked "pre-release" and "not cut". Leaves the frozen tail byte for byte. Exit 0 | +| 2 | `canon changelog --check` at commit 1 | Passes, exit 0 | +| 3 | `scripts/validate-releases.py` (the releases gate) at commit 1 | **Fails**, by design. At format 2, `ratified_head` is mandatory, and commit 2 fills it. `v0.6.0`'s commit 1 failed in the same way (b651677's message) | +| 4 | `canon ratify v0.7.0` at commit 1 | Adds one line, `ratified_head: `, after `version:`. Commits nothing. Exit 0 | +| 5 | The releases gate and `check-release-head.py` at commit 2 | Pass. `ratified_head` is an ancestor of HEAD, and only `releases/v0.7.0.yaml` changed after it | +| 6 | `python3 scripts/ci.py` at commit 2 | Every gate passes | +| 7 | canon's CI steps (`dotnet test`, `changelog --check`, `issue-refs --basis`, `check --compare`) at commit 2 | Pass. `issue-refs` finds `Refs #69` on every commit. None of the session's commits touch `core/`, so `--basis` asks for no `Basis:` line, though every commit carries one | +| 8 | GitHub CI on the pull request | `pipeline (devcontainer)` green | diff --git a/meta/sessions/2026-11-10-release-v0.7.0/prompt.md b/meta/sessions/2026-11-10-release-v0.7.0/prompt.md new file mode 100644 index 0000000..fddc473 --- /dev/null +++ b/meta/sessions/2026-11-10-release-v0.7.0/prompt.md @@ -0,0 +1,24 @@ +# Prompt — release v0.7.0, 2026-11-10 + +The session prompt, verbatim. Per `DDD-dec-20`, this file is committed before any other file +changes, so the session's scope is fixed at arrival. + +--- + +New session: the v0.7.0 release descriptor, 2026-11-10, in mindovermachine-dev/decision-driven-design. Branch from main. On 2026-11-10 main was 87db443. Report main's head at arrival, and say so in bootstrap.md if it has moved. Open an issue; Refs #N on every commit. Commit prompt.md and bootstrap.md under meta/sessions/2026-11-10-release-v0.7.0/ first. +Emil's rulings, verbatim +Claude explained that the release goes through a descriptor, not by hand, and named it v0.7.0: a card was added (step 1b), which is MINOR under DDD-dec-82. Emil then ran it: +release: refused at step 1: releases/v0.7.0.yaml is not on origin/main (87db443b8671); a release is cut only from a landed descriptor +Whether v0.7.0 is a pre-release was asked but not answered. Write `prerelease: true`, as v0.6.0 did, since DDD-dec-74 keeps the method "ready to try (preview)", and mark it as a choice for Emil to confirm when he ratifies the head. +Sources +CONTRIBUTING.md §Releases; GOVERNANCE.md §Releases; spec/release-format.md; DDD-dec-75, -82, -84, -104; releases/v0.6.0.yaml as the model; tools/canon/README.md (canon changelog, ratify, release). Read what landed since v0.6.0: `git log v0.6.0..main`, DDD-dec-114 to -118, and PRs #63 to #68. +The work +Predict before each operation. Stop at every gate. + +1. Confirm the version from the rules, not from this prompt. Since v0.6.0, step 1b's card was added (DDD-dec-118), so the release is MINOR: v0.7.0. Check that no other change in the range moves a step's register, which would also be MINOR, and that nothing calls for more. If the rules give something else, stop and say so. +2. Commit 1, the head Emil ratifies: releases/v0.7.0.yaml in format 2, modelled on v0.6.0.yaml. + * basis: DDD-dec-114 to -118, and anything else the range carries, each with a comment line. + * A title, and a summary written for readers: one idea per sentence, British spelling, registers stated (what is ruled, what is [PROPOSED], what is projected). Cover the PDLC and the SDLC as applications (#64), specification feasibility with grants and roles (#63), product-cli's definition (#65), sdlc.md O-8 and O-9 (#66), and step 1b with DDD-flow-01 to -04 scoped to the PDLC (#68). Say plainly that the step and the specs are [PROPOSED]. + * prerelease: true, marked as above. Then generate its CHANGELOG.md section with `canon changelog`; never edit CHANGELOG.md by hand. Run the releases gate and `canon changelog --check`. +3. Commit 2: `canon ratify v0.7.0`, which fills ratified_head with commit 1 and changes nothing else. +4. Run scripts/ci.py and canon's checks as CI runs them. Push, open the pull request, wait for green CI, and report the pull request, its head, and the steps: land it, then `canon release v0.7.0 --plan` and `canon release v0.7.0` from main. Stop. Do not land, and do not run canon release. diff --git a/meta/sessions/README.md b/meta/sessions/README.md index 14b7cf7..ecd9910 100644 --- a/meta/sessions/README.md +++ b/meta/sessions/README.md @@ -53,3 +53,4 @@ session's later work exceeds the committed prompt, the excess is visible as exce | `2026-11-07-sdlc-and-pdlc/` | Interactive, gated — the PDLC founded (`DDD-dec-114`): three owners as scopes under the genesis grant (What, with assurance; When, the business and go-to-market; How, the SDLC), responsibility placed per decision, the option pool and pull, ready for users and the toggle constraint, priority as a When decision; the SDLC filed as an arrangement (`DDD-dec-115`): issue-driven sessions started by a label, takt's `ready/` with Varve's force and no squash, Claude Code Action first, Varve's identity map ported, the occurrence record from edition 1. `applications/pdlc/` and `applications/sdlc/sdlc.md`, `[PROPOSED]`; the `lc:` act map with SHACL shapes and checkers. Fifteen rounds of rulings, verbatim. Workflows not written. Continuation (Rounds 16–22, `prompt-2.md`), amended in place before landing (Round 21): two assurances (product, the What owner's; implementation, the How owner's), evidence in use and observation needs, the What owner's output, three kinds of demand (new through the pool; owed and own-ground direct to the SDLC), the DORA keys as the How owner's answerability, computed over the record. Issue #61 | | `2026-11-08-specification-feasibility/` | Rulings filed, gated — specification feasibility, from a claude.ai conversation (F-1 to F-12): every dependency on ground has a What layer and a How layer, the How decides by three loose-coupling conditions, any granted actor vets a pinned What change and product-cli records the decision (`DDD-dec-116`); vetted ground becomes a ground-sourced bounded context, admitted per system for Deciders, Projectors and Views, with permission the data owner's; product-cli and the framework carry grants and roles, superseding `[D1.11]` (`DDD-dec-117`). Not applied; S-1 to S-8. Issue #62 | | `2026-11-08-demand-flow/` | Rulings filed, gated — map the flow of demand, from the claude.ai conversation's Rounds 23 to 25: a method step after step 1 (`method/01b-map-the-flow-of-demand.md`, `[PROPOSED]`), general, with each process declaring its kinds of demand and the PDLC's new, owed and own-ground as its worked example and starting point; four PDLC-scoped claims in a new area, `DDD-flow-01` to `-04`, projected; `DDD-dec-118`, adding to `DDD-dec-114`; the acme shop's #101, #103 and #104 traced as graph data checked against the act map. Nothing upstream. Round 26 (2026-11-10) closed R-1: sighting separated from entry, only the What owner says whether a defect is a bug. Open: numbering (N-1), promotion (P-1), the two examples (E-1). Issue #67 | +| `2026-11-10-release-v0.7.0/` | Release descriptor, gated. `releases/v0.7.0.yaml` is MINOR under `DDD-dec-82`: step 1b's card was added (`DDD-dec-118`), and no step's register moved (F-1). Format 2, `prerelease: true` for Emil to confirm (F-3). Its `CHANGELOG.md` section is from `canon changelog`, and `canon ratify` fills the ratified head. The prompt calls the PDLC and SDLC specifications `[PROPOSED]`, while the repository says they are ruled (Round 28). The summary follows the repository, and Emil is to settle it (F-2). Not landed and not cut. Issue #69 | diff --git a/releases/v0.7.0.yaml b/releases/v0.7.0.yaml new file mode 100644 index 0000000..3514a6f --- /dev/null +++ b/releases/v0.7.0.yaml @@ -0,0 +1,65 @@ +format: 2 +version: v0.7.0 +ratified_head: 74e4805013f1764b824a399e7335954637285cd3 +# Cut by Emil with `canon release v0.7.0` once this file lands on main (spec §2 rule 3). No +# `commit`. ratified_head is filled in the next commit by `canon ratify v0.7.0`, naming the commit +# that adds this file and its CHANGELOG.md section (spec, port note 4). +date: 2026-11-10 +# prerelease: Claude's choice, FOR EMIL TO CONFIRM when he ratifies this head. It was asked and +# not answered (meta/sessions/2026-11-10-release-v0.7.0/prompt.md). It follows v0.6.0, since the +# method stays "ready to try (preview)" (DDD-dec-74). +prerelease: true +basis: + # The version: a step card added is MINOR (DDD-dec-82); the version is the method's (DDD-dec-75). + - DDD-dec-82 + - DDD-dec-75 + # The preview the pre-release flag follows. + - DDD-dec-74 + # Step 1b, map the flow of demand: the card added, [PROPOSED] (#68). + - DDD-dec-118 + # Step 1b's four claims, projected, scoped to the PDLC (#68). + - DDD-flow-01 + - DDD-flow-02 + - DDD-flow-03 + - DDD-flow-04 + # The PDLC, founded and ruled (#64). + - DDD-dec-114 + # The SDLC as an arrangement, ruled (#64); sdlc.md §19's O-8 and O-9 rest on it (#66). + - DDD-dec-115 + # Specification feasibility (#63). + - DDD-dec-116 + # Grants and roles in product-cli and the product framework (#63). + - DDD-dec-117 + # product-cli's definition brought up to sdlc edition 1 (#65). + - DDD-dec-113 +title: 'Step 1b, map the flow of demand; the PDLC and the SDLC' +summary: | + **Step 1b, map the flow of demand, is a new step card** (`DDD-dec-118`). Adding a card is a + MINOR release (`DDD-dec-82`). **The step is `[PROPOSED]`.** Its place after step 1 and its scope + are ruled. Its procedure, its fields and its worked example are not ruled. + + - **Step 1b** (#68) traces demand across step 1's act map. It records where an item is + sighted, where it enters, who orders it and where it is discharged. Each process declares its + own kinds of demand. The PDLC's kinds are new, owed and own-ground. They are the worked example + and the starting point, and the step does not claim they apply to every process. The step + rests on four claims, `DDD-flow-01` to `-04`. They are projected and scoped to the PDLC. How + the steps are numbered is still open. + - **The PDLC and the SDLC** are new applications (#64; `DDD-dec-114`, `DDD-dec-115`). The PDLC + is the product lifecycle. It has three owners: What, When and How. The SDLC is the How + owner's arrangement within it. It runs from an issue to production, dark behind a toggle. Both + specifications are ruled, by Round 28, and Rounds 29 and 30 settled the forecast. Each + specification carries its act map as graph data, with SHACL shapes and a checker. The + reference workflows are not written. + - **Two open items join `sdlc.md` §19** (#66). They are not rulings. O-8 proposes an act that + accepts the realisation plan before work starts. O-9 asks product-cli either to adopt the SDLC + for its issue sessions or to record where it departs from it. + - **Specification feasibility is ruled** (#63; `DDD-dec-116`). The How decides whether a + dependency on outside ground can be realised loosely coupled, using three conditions that can + be checked. What may be used from the source is the data owner's decision. + - **Grants and roles are ruled** (#63; `DDD-dec-117`). product-cli carries the same grants and + roles as the other systems, which supersedes its `[D1.11]`. `DDD-dec-116` and `DDD-dec-117` + are not yet applied to `what.md`, `how.md`, `authority.md` or product-cli's definition. + - **product-cli's definition** is brought up to sdlc edition 1 (#65). It cites the ruled + validation regime (`DDD-dec-113`). It records edition 1 as shipped in v0.6.0. + + No other step's register moves. The method stays "ready to try (preview)" (`DDD-dec-74`).