You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
> **Current release note:**`v10.36 / P128` establishes `diagram/`as the dedicated governed visual lane, opens`diagram/STRUCTURE.md`as the whole-repo visual anchor, and keeps repository diagram doctrine separate from inline answer/phase-local text-diagram formatting.
36
+
> **Current release note:**`v10.37 / P129` makes governed `diagram/`source mandatory Kroki-compatible, supports all suitable formats by defining them as Kroki-compatible + governance-suitable, upgrades`diagram/STRUCTURE.md`into a bodyful whole-project detailed visual structure authority, and keeps inline answer/phase-local text-diagram formatting outside governed source truth by default.
37
37
38
38
<!-- CTA Buttons -->
39
39
<p>
@@ -333,9 +333,9 @@ ls "$HOME/.claude/rules/worker-routing-and-context.md"
333
333
|`./design/<slug>.design.md`| Compact active parent design index/gateway for governed chains | Active design parent |
334
334
|`./design/<slug>/*.design.md`| Active child target-state shards in same-stem nested mode | Active design shards |
335
335
|`./design/*.design.md` beside a compact parent | Flat sibling design shards when the current folder already scopes the chain | Active design sibling shards |
336
-
|`./diagram/STRUCTURE.md`|Whole-repo visual anchor when a governed diagram lane is opened | Active diagram global anchor |
337
-
|`./diagram/<subject>.design.md`| Default integrated subject diagram in the dedicated visual lane| Active subject diagram |
338
-
|`./diagram/<subject>/*.design.md`|Child visual shards only after a real visual split trigger | Active diagram child shards |
336
+
|`./diagram/STRUCTURE.md`|Bodyful whole-project detailed visual structure authority when a governed diagram lane is opened | Active diagram global anchor |
337
+
|`./diagram/<subject>.design.md`| Default integrated Kroki-compatible subject diagram as a zoom-in / decomposition view of the global structure| Active subject diagram |
338
+
|`./diagram/<subject>/*.design.md`|Kroki-compatible child visual shards only after a real visual split trigger | Active diagram child shards |
339
339
|`*.md` (root) | Active runtime rules | Rules files |
|`./changelog/*.changelog.md`| Per-chain authoritative active parent history/current version state | Active parent changelogs |
@@ -358,9 +358,10 @@ ls "$HOME/.claude/rules/worker-routing-and-context.md"
358
358
359
359
> **💡 Single Source of Truth Principle:**
360
360
> - Governed design/changelog chains should classify chain shape before parent files absorb more detail
361
-
> -`diagram/STRUCTURE.md` is the top-level visual anchor when a governed diagram lane is opened
362
-
> -`diagram/<subject>.design.md` is the default bodyful integrated subject diagram; split only when visual complexity or genuinely different visual questions justify it
363
-
> - Diagram structure must not auto-mirror design shards, and `design/` remains semantic authority when text and diagram differ
361
+
> -`diagram/STRUCTURE.md` is the bodyful top-level whole-project detailed visual structure authority when a governed diagram lane is opened
362
+
> - governed `diagram/` source is mandatory Kroki-compatible and supports all formats that are both Kroki-compatible and governance-suitable
363
+
> -`diagram/<subject>.design.md` is the default bodyful integrated subject diagram as a zoom-in / decomposition view of the global structure; split only when visual complexity or genuinely different visual questions justify it
364
+
> - Diagram structure must not auto-mirror design shards, inline answer/phase-local text diagrams do not become governed source truth automatically, and `design/` remains semantic authority when text and diagram differ
364
365
> - Flat sibling shards are valid when the current folder already scopes the chain and the compact parent clearly exposes the shard map
365
366
> - Broad active design chains should still strongly prefer same-stem parent/index + shard pairs (`design/<slug>.design.md` + `design/<slug>/`) and do not use a default `design/done/` surface
366
367
> - Per-chain active changelogs (`*.changelog.md`) remain the authority for current governed chain history/version state
@@ -394,7 +395,7 @@ This section defines how `design`, `diagram`, `changelog`, `runtime rules`, `TOD
394
395
| Document | Role | Update Trigger |
395
396
|----------|------|----------------|
396
397
|`design/*.design.md`| Target behavior/specification | Requirement or policy change |
397
-
|`diagram/STRUCTURE.md` and `diagram/*.design.md`| Governed visual synthesis / relationship explanation | A whole-repo or subject-level visual explanation needs active source truth |
398
+
|`diagram/STRUCTURE.md` and `diagram/*.design.md`| Governed Kroki-compatible visual synthesis / relationship explanation | A whole-repo or subject-level visual explanation needs active source truth |
|`changelog/*.changelog.md`| Authoritative active per-chain version history | Any rule/design update with version impact |
@@ -1005,7 +1006,7 @@ Result: ✅ Verified from actual files
1005
1006
### Runtime install boundary
1006
1007
1007
1008
- Current README meaning: the Quick Start block installs the compact 18-rule source-owned active runtime set and uses owner-aware cleanup instead of filename-only deletion.
1008
-
- Source state: this README reflects the released `v10.36 / P128` unified diagram doctrine model while the active runtime install set remains 18 root rules, `diagram/` stays the governed visual lane, and `playground/` stays outside the install payload.
1009
+
- Source state: this README reflects the released `v10.37 / P129` Kroki-compatible diagram doctrine model while the active runtime install set remains 18 root rules, `diagram/` stays the governed Kroki-compatible visual lane, and `playground/` stays outside the install payload.
1009
1010
- Ownership guard: manifest-owned files are removed only when they still match the last recorded install snapshot, and legacy pre-manifest files are quarantined only when their content exactly matches this repo's git history for that rule path.
1010
1011
- Boundary: files already present in a shared runtime destination but outside this repo's recorded install ownership or repo-history proof are not cleanup targets by default.
1011
1012
- Impact: protects install scope and other-owner runtime files while still allowing safe cleanup of this repo's old runtime leftovers, including legacy installs from before the merged-rule transition.
@@ -1128,8 +1129,8 @@ Personal rule set and configuration framework for Claude Code CLI.
1128
1129
---
1129
1130
1130
1131
<p>
1131
-
<b>Version</b>: 10.36 |
1132
-
<b>Last Updated</b>: 2026-06-01 |
1132
+
<b>Version</b>: 10.37 |
1133
+
<b>Last Updated</b>: 2026-06-02 |
1133
1134
<b>Framework</b>: Sophisticated AI Framework with Constitutional Governance
-[x] P129 / v10.37 Kroki-compatible governed diagram doctrine was completed, pushed, mirrored to the remote default branch, and released.
14
+
- Verified: governed `diagram/` source is now mandatory Kroki-compatible; allowed breadth is defined as all formats that are both Kroki-compatible and governance-suitable; `design/` remains semantic authority; `diagram/STRUCTURE.md` is now a bodyful whole-project detailed visual structure authority; subject diagrams are positioned as zoom-in / decomposition views of the global structure; inline answer/phase-local text diagrams are explicitly kept outside governed source truth unless promoted; touched README/design/TODO/phase/changelog/patch surfaces are aligned; `git diff --check` passed; branch/default-branch/tag/release evidence is aligned to the promoted `v10.37` state.
-[x] P128 / v10.36 RULES unified diagram doctrine correction was completed, pushed, mirrored to the remote default branch, and released.
14
18
- Verified: RULES now recognizes `diagram/` as a dedicated governed visual lane; `diagram/STRUCTURE.md` is present as the whole-repo visual anchor; integrated subject diagrams are the default visual posture; automatic design-shard mirroring was rejected; plugin-first fragmented companion assumptions were withdrawn from active current-state doctrine; touched README/design/TODO/phase/changelog/patch surfaces are aligned; `git diff --check` passed; temporary project-local install proof passed with 18 active runtime rule markdown files; touched runtime-owner parity matched for `document-governance.md` and `explanation-and-presentation.md`; reconciled branch/default-branch/tag/release evidence is aligned to the promoted `v10.36` state.
P129 closes the remaining doctrine gap in the RULES diagram lane by making governed diagram source enforceably Kroki-compatible, keeping breadth open to all governance-suitable Kroki formats, and turning `diagram/STRUCTURE.md` into the primary detailed whole-project visual understanding surface.
## Version 1.12: Added P129 mandatory Kroki-compatible diagram governance
33
+
34
+
**Date:** 2026-06-02
35
+
**Session:** 1f1873d2-0feb-485f-a5ff-d383254590dd
36
+
37
+
### Changes
38
+
- Updated `document-governance.md` from v1.11 to v1.12.
39
+
- Updated `design/document-governance.design.md` from v1.11 to v1.12.
40
+
- Made governed `diagram/` source mandatory Kroki-compatible.
41
+
- Defined allowed breadth as all formats that are both Kroki-compatible and governance-suitable.
42
+
- Clarified that `diagram/STRUCTURE.md` is a bodyful whole-project detailed visual structure authority rather than a shallow router.
43
+
- Clarified that inline answer/status/phase-local text diagrams do not become governed source truth automatically.
44
+
45
+
### Summary
46
+
`document-governance.md` now treats governed `diagram/` source as mandatory Kroki-compatible, defines the allowed breadth as Kroki-compatible + governance-suitable, and elevates `diagram/STRUCTURE.md` into a bodyful whole-project detailed visual structure authority.
47
+
48
+
---
49
+
30
50
<aid="version-111"></a>
31
51
## Version 1.11: Added P128 governed diagram lane role model
## Version 1.16: Added P129 inline-diagram Kroki-boundary retention
37
+
38
+
**Date:** 2026-06-02
39
+
**Session:** 1f1873d2-0feb-485f-a5ff-d383254590dd
40
+
41
+
### Changes
42
+
- Updated `explanation-and-presentation.md` from v1.15 to v1.16.
43
+
- Updated `design/explanation-and-presentation.design.md` from v1.15 to v1.16.
44
+
- Clarified that mandatory Kroki-compatible enforcement belongs to governed `diagram/` source rather than inline explanatory diagrams by default.
45
+
46
+
### Summary
47
+
`explanation-and-presentation.md` now keeps inline answer/status/phase-local text diagrams explicitly outside mandatory Kroki-compatible governed-diagram enforcement unless they are deliberately promoted into the governed lane.
48
+
49
+
---
50
+
34
51
<aid="version-115"></a>
35
52
## Version 1.15: Added P128 inline-diagram boundary refinement
| 1.2 | 2026-05-06 |**[Materialized active runtime body and closed metadata-only stub drift](#version-12)**| d42465eb-30a7-4bc8-b9d6-03e52306e9a5 |
15
16
||| Summary: Re-materialized root `flow-diagram-no-frame.md` as a substantive active runtime rule with `Full history`, preserving current design target behavior while removing design-only runtime dependency ||
@@ -20,6 +21,21 @@
20
21
21
22
---
22
23
24
+
<aid="version-14"></a>
25
+
## Version 1.4: Added P129 inline-text-diagram non-governed Kroki boundary
26
+
27
+
**Date:** 2026-06-02
28
+
**Session:** 1f1873d2-0feb-485f-a5ff-d383254590dd
29
+
30
+
### Changes
31
+
- Updated `design/flow-diagram-no-frame.design.md` from v1.3 to v1.4.
32
+
- Clarified that repository governed visual source under `diagram/` includes mandatory Kroki-compatible doctrine, while inline text diagrams stay outside that boundary unless promoted.
33
+
34
+
### Summary
35
+
Flow-diagram-no-frame now states more explicitly that inline text diagrams stay outside mandatory Kroki-compatible governed-source doctrine unless explicitly promoted into the governed lane.
36
+
37
+
---
38
+
23
39
<aid="version-13"></a>
24
40
## Version 1.3: Narrowed inline text-diagram scope and boundary
0 commit comments