[Hafeok]

What this changes, and why

canon release v0.7.0 was refused because releases/v0.7.0.yaml is not on origin/main (87db443). This pull request adds that descriptor. Refs #69.

Commit	What
38908a9	Session record: prompt.md and bootstrap.md, committed first. main was at 87db443 when the session started, the commit the prompt named, so it had not moved
9310b41	Session record: findings, predictions and the row in the sessions index. They go in before the ratified head, because the guard allows nothing but the descriptor after it
74e4805	The head to ratify. releases/v0.7.0.yaml (format 2) and its CHANGELOG.md section, written by canon changelog
84aa466	canon ratify v0.7.0. It adds only ratified_head: 74e4805…

Rulings and decisions

No decision is filed or superseded. The version comes from the rules (findings.md F-1):

• MINOR under DDD-dec-82. Step 1b's card was added (DDD-dec-118), so the version is v0.7.0.
• No step's register moved. Step 1 is still "Ruled for test", and steps 2 to 10 are still [PROPOSED]. The only edits to cards 1 and 7 are one line each pointing to 1b.
• Nothing calls for more. The version is below 1.0, so it cannot be MAJOR.

The release rests on DDD-dec-114 to -118, DDD-flow-01 to -04, DDD-dec-113 (#65), and DDD-dec-82, -75 and -74. The descriptor gives each a comment line.

Emil, two things to confirm when you ratify 74e4805:

1. prerelease: true is Claude's choice. You were asked and did not answer. It follows v0.6.0 and DDD-dec-74, and the file marks it as yours to confirm (F-3).
2. The register of the specifications (F-2). The prompt said "the step and the specs are [PROPOSED]".
   • The step is [PROPOSED], and the summary says so plainly.
   • The PDLC and SDLC specifications are ruled by Round 28, according to pdlc.md, sdlc.md and the statements of DDD-dec-114 and -115. The summary follows the repository.
   • What the summary does call unruled or unapplied: O-8's proposal is open, and DDD-dec-116 and -117 are not yet applied.
   • If you mean the PDLC and SDLC to read [PROPOSED], that needs a ruling, then a new commit 1 and a new ratification.

Predicted, then measured

#	Prediction	Observed
1	canon changelog writes the v0.7.0 section, marked pre-release and "not cut"	Wrote it, marked pre-release, exit 0. There is no "not cut" marker. v0.6.0's section has none either, so the prediction was wrong on that point
2	canon changelog --check passes at commit 1	CHANGELOG.md is the projection of releases/, exit 0
3	The releases gate fails at commit 1, by design	v0.7.0: ratified_head missing or not a hex SHA of 7-40 chars: None, exit 1
4	canon ratify adds one line and commits nothing	ratified_head 74e4805013f1764b824a399e7335954637285cd3. Not committed. The diff is one line
5	The guard passes at commit 2	ok: the merged head is the ratified head plus at most the descriptor
6	scripts/ci.py passes	all gates passed. The first run skipped what and how because scripts/requirements.txt was not installed. After installing it, every gate passed
7	canon's CI steps pass	dotnet test: 66 succeeded, 0 failed. changelog --check ok. issue-refs --basis: 4 commits … Refs checked on 4, Basis on 0. In a shallow clone it exits 2, which is a clone artefact, not the tree. check --compare: every case agrees, all gates passed
8	GitHub CI green	Green on 84aa466. Both runs of pipeline (devcontainer) passed, and so did agent review (judge). agent review stays red, as designed, until a hand-written approve 84aa466… comment by Hafeok appears

What was found

• F-2. applications/README.md still marks sdlc/sdlc.md as [PROPOSED], which contradicts sdlc.md itself. That line is a bug in the prose. It is left alone here, because no change may follow the ratified head except the descriptor.
• F-4. Method step: map the flow of demand (Rounds 23–25, 2026-11-08) #67 is an issue, not a pull request. The range comes from Specification feasibility: DDD-dec-116, DDD-dec-117 #63, The PDLC and the SDLC: DDD-dec-114, DDD-dec-115 #64, product-cli definition: edition 1 shipped in v0.6.0; D1.19 ruled, M-12 corrected, the table met #65, sdlc.md §19: O-8 (accepting the realisation plan) and O-9 (product-cli's issue sessions); Round 31 #66 and Method step 1b, map the flow of demand: DDD-dec-118, DDD-flow-01 to -04 #68.
• Noted for 1.0. DDD-dec-118's N-1 records that "below 1.0 until all ten steps are ruled" now counts eleven steps. That does not affect v0.7.0.

What is left (Emil)

1. Confirm prerelease: true and F-2. Approve 84aa466, then land with canon land.
2. From main: canon release v0.7.0 --plan
3. Then canon release v0.7.0

This session does not land the branch and does not run canon release.

---

• python3 scripts/ci.py passes (every gate: claims, decisions, core order and pins, the What, the How examples, fixtures)
• Every commit that changes canon carries a Basis: line. None touches core/, but every commit carries one
• Decision ids checked across every branch of both repositories. Not applicable: no decision is filed
• A session record exists under meta/sessions/, with prompt.md and bootstrap.md committed first
• No customer-identifying material anywhere in the diff

🤖 Generated with Claude Code

https://claude.ai/code/session_01NbWSYQWvqXNynbkWq84UyK

[Hafeok]

approve 84aa466