Create shared execution coordination rule chain.

Add a first-class coordination owner for multi-session shared execution boards, bounded companion deferrals, 40-rule runtime sync, and release-ready governance artifacts.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: DarKWinGTM

README.md

@@ -47,7 +47,7 @@
     <img src="https://img.shields.io/badge/⚡_Quick_Start-5_seconds-brightgreen?style=for-the-badge&logo=data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHZpZXdCb3g9IjAgMCAyNCI+PHBhdGggZmlsbD0iIzI1RTEyNiIgZD0iTTEzIDJoLTh2MmMwIC4zNS4wNy42OS4xOCAxLjAzLjM1IDEuMDguOTkgMS44MyAxLjgzLjk5LjM0LjM1LjY5LjQyIDEuMDMuMTIuNDkuMDUuOTguMjIgMS40Ni40OWwtMS44My0uMzVjLS4zNS0uMDctLjY5LS4xNC0xLjAzLS4xOC0uMzUtLjA1LS42OS0uMTItMS4wMy0uMzUtMS4wOC0uOTktMS44My0xLjgzLS45OS0uMzQtLjM1LS42OS0uNDItMS4wMy0uMTItLjQ5LS4wNS0uOTgtLjIyLTEuNDYtLjQ5bDEuODMuMzV6Ii8+PC9zdmc+">
   </a>
   <a href="#-rule-files">
-    <img src="https://img.shields.io/badge/📁_Rules-39_Policies-orange?style=for-the-badge&logo=data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHZpZXdCb3g9IjAgMCAyNCAyNCI+PHBhdGggZmlsbD0iI0Y5NzgxNiIgZD0iTTEyIDJDNi40OCAyIDIgNi40OCAyIDEyszQuNDggMTAgMTAgMTAtNC40OCAxMC0xMFMxNy41MiAyIDEyIDJ6bS0yIDE1bC01IDUgNS01IDUtNS01IDV6Ii8+PC9zdmc+">
+    <img src="https://img.shields.io/badge/📁_Rules-40_Policies-orange?style=for-the-badge&logo=data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHZpZXdCb3g9IjAgMCAyNCAyNCI+PHBhdGggZmlsbD0iI0Y5NzgxNiIgZD0iTTEyIDJDNi40OCAyIDIgNi40OCAyIDEyszQuNDggMTAgMTAgMTAtNC40OCAxMC0xMFMxNy41MiAyIDEyIDJ6bS0yIDE1bC01IDUgNS01IDUtNS01IDV6Ii8+PC9zdmc+">
   </a>
   <a href="#-installation">
     <img src="https://img.shields.io/badge/📦_Install-Copy_&_Paste-blue?style=for-the-badge&logo=data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHZpZXdCb3g9IjAgMCAyNCAyNCI+PHBhdGggZmlsbD0iIzI1ODFGNiIgZD0iTTEyIDJDNi40OCAyIDIgNi40OCAyIDEydjJMMTQgN2g0bDItMnYtMmgybC0yIDJoLTRsLTItMnYtMmgybC0yIDJ2MmgybDItMnYtMmgybC0yIDJoLTRMNCAydjJ6Ii8+PC9zdmc+">
@@ -79,7 +79,7 @@
 
 ## ⚡ Quick Start
 
-Use the script for your platform. Both install the same 39 active runtime rules only.
+Use the script for your platform. Both install the same 40 active runtime rules only.
 
 ### Bash — Linux / macOS
 
@@ -134,6 +134,7 @@ rule_files=(
   high-signal-communication.md
   execution-continuity-and-mode-selection.md
   goal-set-review-and-priority-balance.md
+  shared-execution-coordination.md
 )
 
 for file in "${rule_files[@]}"; do
@@ -194,7 +195,8 @@ $ruleFiles = @(
   "zero-hallucination.md",
   "high-signal-communication.md",
   "execution-continuity-and-mode-selection.md",
-  "goal-set-review-and-priority-balance.md"
+  "goal-set-review-and-priority-balance.md",
+  "shared-execution-coordination.md"
 )
 
 foreach ($file in $ruleFiles) {
@@ -335,7 +337,7 @@ Please:
 
 ---
 
-### 🟡 Quality & Safety (28 rules)
+### 🟡 Quality & Safety (29 rules)
 
 > **Ensure consistent, safe, and well-documented outputs**
 
@@ -368,6 +370,7 @@ Please:
 | [`project-documentation-standards.md`](project-documentation-standards.md) | Project documentation standards | Standardized docs for all projects plus startup artifact gate, explicit live-task-list-vs-durable-TODO distinction, same-objective live task-list continuity, explicit execution-discovery surfaces during active execution, non-default startup patch posture for greenfield baseline formation, portable public onboarding/install guidance, and portable-by-default package-local support assets when they are reusable source content |
 | [`portable-implementation-and-hardcoding-control.md`](portable-implementation-and-hardcoding-control.md) | Portable implementation control | Keep shared artifacts, reusable support/package source artifacts, and public onboarding/install guidance portable by default, bind environment-specific values late, and prevent machine-local hardcoding drift |
 | [`execution-continuity-and-mode-selection.md`](execution-continuity-and-mode-selection.md) | Execution continuity and mode selection | Separates discussion mode from execution mode, keeps work moving when execution mode is active, and discovers the next unfinished slice from execution surfaces when that path is already visible |
+| [`shared-execution-coordination.md`](shared-execution-coordination.md) | Shared execution coordination | Makes the shared task list a first-class execution-coordination layer with session lease/handoff semantics, continuity-first retention, anti-overclear policy, optional memsearch support, and future-optional peer-messaging boundaries |
 | [`unified-version-control-system.md`](unified-version-control-system.md) | Unified version governance | Single deterministic UDVC-1 controller |
 
 ---
@@ -396,17 +399,17 @@ Please:
 | [`safe-file-reading.md`](safe-file-reading.md) | Plan-before-read | Efficient file handling |
 | [`safe-terminal-output.md`](safe-terminal-output.md) | Output management | No terminal flooding |
 
-**📊 Active Runtime Rules: 39**
+**📊 Active Runtime Rules: 40**
 
-Latest refinement: the active runtime set now includes bounded next-work discovery from execution surfaces across the continuity, task-list, phase, and repository-model owner set, while the active runtime count remains 39.
+Latest refinement: the active runtime set now includes a first-class shared execution coordination owner for multi-session shared boards, session lease/handoff behavior, continuity-first retention, anti-overclear policy, and optional memsearch / future optional peer-messaging boundaries.
 
 </div>
 
 ---
 
 ## 📦 Installation
 
-The Quick Start block above is still the canonical runtime-only install block. The methods below use the same active 39-rule set and describe when to use each path without repeating the long file list.
+The Quick Start block above is still the canonical runtime-only install block. The methods below use the same active 40-rule set and describe when to use each path without repeating the long file list.
 
 ### 🎯 Method 1: Full Installation (Recommended)
 
@@ -1147,8 +1150,8 @@ Personal rule set and configuration framework for Claude Code CLI.
 ---
 
 <p>
-  <b>Version</b>: 9.21 |
-  <b>Last Updated</b>: 2026-04-12 |
+  <b>Version</b>: 9.22 |
+  <b>Last Updated</b>: 2026-04-13 |
   <b>Framework</b>: Sophisticated AI Framework with Constitutional Governance
 </p>
 

TODO.md

@@ -1,11 +1,12 @@
 # Claude Code Rules - TODO
 
-> **Last Updated:** 2026-04-12
+> **Last Updated:** 2026-04-13
 
 ---
 
 ## ✅ Completed
 
+- [x] Create first-class `shared-execution-coordination` so multi-session shared execution boards now have one semantic owner for shared-board semantics, session lease/handoff behavior, continuity-first retention, anti-overclear policy, optional memsearch support, and future-optional peer-messaging boundaries; integrate bounded companion deferrals across task/phase/execution/memory/repository owners; update master surfaces; and resync installed runtime copies.
 - [x] Make execution-ready work discover the next unfinished slice from active execution surfaces by updating `execution-continuity-and-mode-selection`, `todo-standards`, `phase-implementation`, and `project-documentation-standards`; add bounded `phase-035` / `patch/next-work-discovery-from-execution-surfaces.patch.md` artifacts; update master surfaces; and resync installed runtime copies.
 - [x] Keep one live task-list surface across the same active objective by updating `todo-standards`, `phase-implementation`, `artifact-initiation-control`, and `project-documentation-standards`; add bounded `phase-034` / `patch/task-list-continuity-and-objective-boundary-retention.patch.md` artifacts; update master surfaces; and bundle the already-open `accurate-communication.md` micro-compression so the runtime copy falls below the 40.0k warning threshold.
 - [x] Create first-class `execution-continuity-and-mode-selection` and `goal-set-review-and-priority-balance` rule chains, integrate bounded companion updates without expanding `accurate-communication.md`, add the bounded `phase-033` / `patch/continuous-execution-and-goal-set-review.patch.md` wave artifacts, and update master inventory/install surfaces from 37 to 39 active runtime rules.
@@ -94,6 +95,7 @@
 
 | Date | Changes |
 |------|---------|
+| 2026-04-13 | Created first-class `shared-execution-coordination`, added bounded companion deferrals across `todo-standards`, `phase-implementation`, `execution-continuity-and-mode-selection`, `project-documentation-standards`, `memory-governance-and-session-boundary`, and `authority-and-scope`, then synchronized master surfaces and resynced installed runtime copies. |
 | 2026-04-12 | Added next-work discovery from execution surfaces across `execution-continuity-and-mode-selection`, `todo-standards`, `phase-implementation`, and `project-documentation-standards`; added bounded `phase-035` / `patch/next-work-discovery-from-execution-surfaces.patch.md` artifacts; synchronized master surfaces; and resynced the touched runtime rules. |
 | 2026-04-12 | Added same-objective task-list continuity and retention across `todo-standards`, `phase-implementation`, `artifact-initiation-control`, and `project-documentation-standards`; added bounded `phase-034` / `patch/task-list-continuity-and-objective-boundary-retention.patch.md` artifacts; and bundled `accurate-communication.md` micro-compression so the runtime copy now falls below the 40.0k warning threshold. |
 | 2026-04-12 | Created first-class `execution-continuity-and-mode-selection` and `goal-set-review-and-priority-balance` owner chains, added bounded `phase-033` / `patch/continuous-execution-and-goal-set-review.patch.md` artifacts, integrated bounded companion updates without expanding `accurate-communication.md`, and updated the active runtime inventory/install set from 37 to 39 rules. |

authority-and-scope.md

@@ -1,7 +1,7 @@
 # Authority and scope
 
-> **Current Version:** 2.2
-> **Design:** [design/authority-and-scope.design.md](design/authority-and-scope.design.md) v2.2
+> **Current Version:** 2.3
+> **Design:** [design/authority-and-scope.design.md](design/authority-and-scope.design.md) v2.3
 > **Session:** 11c4bd2f-216e-4779-81bf-26d34a4fcaeb
 > **Full history:** [changelog/authority-and-scope.changelog.md](changelog/authority-and-scope.changelog.md)
 
@@ -29,6 +29,7 @@ This rule defines precedence, tie-break behavior, and override handling so new u
 - Assistant-created team expansion is advisory and should not happen by default when an existing teammate already covers the same role or when the new teammate has no clearly distinct job.
 - Do not generate unnecessary user-choice branches when one continuation path is already implied by the request and can be executed safely.
 - Mode selection and continuous-execution defaults defer to `execution-continuity-and-mode-selection.md` when the question is whether work should keep going versus remain in discussion mode.
+- Shared-board multi-session coordination semantics such as session lease, handoff, retention/aging, and optional-extension support defer to `shared-execution-coordination.md` when the question is how several sessions coordinate work on one active execution board.
 - If the user issues a fresh directive that changes scope, task, or action, that fresh directive overrides previously offered assistant options immediately.
 - After compact or compacted-session resume, re-anchor to the latest active user directive and active governing basis before continuing.
 - Do not let stale assistant framing, stale option branches, or compressed-away detail become active truth after compact unless the surviving evidence still justifies it.

changelog/authority-and-scope.changelog.md

@@ -1,7 +1,7 @@
 # Changelog - Authority and Scope
 
 > **Parent Document:** [../authority-and-scope.md](../authority-and-scope.md)
-> **Current Version:** 2.2
+> **Current Version:** 2.3
 > **Session:** dd0bf4af-a66b-4b07-bb9d-a90a0e57b54e
 
 ---
@@ -10,6 +10,7 @@
 
 | Version | Date | Changes | Session ID |
 |---------|------|---------|------------|
+| 2.3 | 2026-04-13 | **[Deferred shared-board multi-session coordination semantics to the new coordination owner](#version-23)** | 11c4bd2f-216e-4779-81bf-26d34a4fcaeb |
 | 2.2 | 2026-04-12 | **[Deferred mode-selection semantics to the new execution-continuity owner](#version-22)** | 11c4bd2f-216e-4779-81bf-26d34a4fcaeb |
 | 2.1 | 2026-04-09 | **[Added path-scoped memory applicability boundary and current-scope-wins protection](#version-21)** | 11c4bd2f-216e-4779-81bf-26d34a4fcaeb |
 | 2.0 | 2026-04-09 | **[Added RULES-first-over-memory authority boundary](#version-20)** | 11c4bd2f-216e-4779-81bf-26d34a4fcaeb |
@@ -33,6 +34,23 @@
 
 ---
 
+<a id="version-23"></a>
+## Version 2.3: Deferred shared-board multi-session coordination semantics to the new coordination owner
+
+**Date:** 2026-04-13
+**Session:** 11c4bd2f-216e-4779-81bf-26d34a4fcaeb
+
+### Changes
+- Updated `authority-and-scope.md` from v2.2 to v2.3.
+- Updated `design/authority-and-scope.design.md` from v2.2 to v2.3.
+- Added explicit deferral that shared-board multi-session coordination semantics such as session lease, handoff, retention/aging, and optional-extension support now live in `shared-execution-coordination.md`.
+- Preserved overall precedence, user authority, and fresh-directive override behavior.
+
+### Summary
+Authority-and-scope now keeps top-level precedence and user-authority behavior while deferring shared-board coordination protocol details to the new coordination owner.
+
+---
+
 <a id="version-22"></a>
 ## Version 2.2: Deferred mode-selection semantics to the new execution-continuity owner
 

changelog/changelog.md

@@ -1,7 +1,7 @@
 # Master Changelog - Claude Code Rules
 
 > **Project:** Claude Code Rules System
-> **Current Version:** 9.21
+> **Current Version:** 9.22
 > **Session:** 11c4bd2f-216e-4779-81bf-26d34a4fcaeb
 
 ---
@@ -10,6 +10,7 @@
 
 | Version | Date | Changes | Session ID |
 |---------|------|---------|------------|
+| 9.22 | 2026-04-13 | **[Created shared execution coordination as a first-class rule chain](#version-922)** | 11c4bd2f-216e-4779-81bf-26d34a4fcaeb |
 | 9.21 | 2026-04-12 | **[Added next-work discovery from execution surfaces](#version-921)** | 11c4bd2f-216e-4779-81bf-26d34a4fcaeb |
 | 9.20 | 2026-04-12 | **[Added same-objective task-list continuity and retention](#version-920)** | 11c4bd2f-216e-4779-81bf-26d34a4fcaeb |
 | 9.19 | 2026-04-12 | **[Added first-class execution continuity and goal-set review owners](#version-919)** | 11c4bd2f-216e-4779-81bf-26d34a4fcaeb |
@@ -60,6 +61,23 @@
 
 ---
 
+<a id="version-922"></a>
+## Version 9.22: Created shared execution coordination as a first-class rule chain
+
+**Date:** 2026-04-13
+**Session:** 11c4bd2f-216e-4779-81bf-26d34a4fcaeb
+
+### Changes
+- Created `shared-execution-coordination` as a new first-class runtime/design/changelog chain for multi-session shared execution boards, session lease/handoff behavior, continuity-first retention, anti-overclear policy, optional memsearch support, and future-optional peer-messaging boundaries.
+- Updated `todo-standards`, `phase-implementation`, `execution-continuity-and-mode-selection`, `project-documentation-standards`, `memory-governance-and-session-boundary`, and `authority-and-scope` with bounded deferrals to the new coordination owner.
+- Updated master design/README/TODO/phase surfaces and expanded the active runtime install set from 39 to 40 rules.
+- Preserved the existing phase, tracking, memory, and execution-continuity owners rather than replacing them with one super-rule.
+
+### Summary
+The RULES repository now has one explicit coordination owner for multi-session shared execution boards, while the existing task, phase, memory, and execution owners keep their narrower roles.
+
+---
+
 <a id="version-921"></a>
 ## Version 9.21: Added next-work discovery from execution surfaces
 

changelog/execution-continuity-and-mode-selection.changelog.md

@@ -1,7 +1,7 @@
 # Changelog - Execution Continuity and Mode Selection
 
 > **Parent Document:** [../execution-continuity-and-mode-selection.md](../execution-continuity-and-mode-selection.md)
-> **Current Version:** 1.1
+> **Current Version:** 1.2
 > **Session:** 11c4bd2f-216e-4779-81bf-26d34a4fcaeb
 
 ---
@@ -10,12 +10,30 @@
 
 | Version | Date | Changes | Session ID |
 |---------|------|---------|------------|
+| 1.2 | 2026-04-13 | **[Deferred shared-board coordination semantics to the new coordination owner](#version-12)** | 11c4bd2f-216e-4779-81bf-26d34a4fcaeb |
 | 1.1 | 2026-04-12 | **[Added execution-surface-driven next-work discovery](#version-11)** | 11c4bd2f-216e-4779-81bf-26d34a4fcaeb |
 | 1.0 | 2026-04-12 | **[Created first-class execution continuity and mode-selection rule chain](#version-10)** | 11c4bd2f-216e-4779-81bf-26d34a4fcaeb |
 | | | Summary: Created a new rule chain that separates discussion mode from execution mode and keeps execution flowing once the active path is already sufficiently clear | |
 
 ---
 
+<a id="version-12"></a>
+## Version 1.2: Deferred shared-board coordination semantics to the new coordination owner
+
+**Date:** 2026-04-13
+**Session:** 11c4bd2f-216e-4779-81bf-26d34a4fcaeb
+
+### Changes
+- Updated `execution-continuity-and-mode-selection.md` from v1.1 to v1.2.
+- Updated `design/execution-continuity-and-mode-selection.design.md` from v1.1 to v1.2.
+- Clarified that session-lease, handoff, retention/aging, anti-overclear, and optional-extension coordination semantics defer to `shared-execution-coordination.md`.
+- Preserved execution-mode selection, stop-gate logic, and next-work discovery ownership.
+
+### Summary
+Execution continuity now keeps its continue/stop/discover role while deferring shared-board coordination protocol details to the new first-class coordination owner.
+
+---
+
 <a id="version-11"></a>
 ## Version 1.1: Added execution-surface-driven next-work discovery
 

changelog/memory-governance-and-session-boundary.changelog.md

@@ -1,7 +1,7 @@
 # Changelog - Memory Governance and Session Boundary
 
 > **Parent Document:** [../memory-governance-and-session-boundary.md](../memory-governance-and-session-boundary.md)
-> **Current Version:** 1.0
+> **Current Version:** 1.1
 > **Session:** 11c4bd2f-216e-4779-81bf-26d34a4fcaeb
 
 ---
@@ -10,11 +10,29 @@
 
 | Version | Date | Changes | Session ID |
 |---------|------|---------|------------|
+| 1.1 | 2026-04-13 | **[Added optional extension recall boundary for memsearch-style layers](#version-11)** | 11c4bd2f-216e-4779-81bf-26d34a4fcaeb |
 | 1.0 | 2026-04-09 | **[Created first-class memory-governance-and-session-boundary rule chain](#version-10)** | 11c4bd2f-216e-4779-81bf-26d34a4fcaeb |
 | | | Summary: Created a new design/runtime/changelog triad that governs memory role boundaries, root `MEMORY.md` index behavior, `global/path/archive` taxonomy, path-primary applicability, session provenance, canonical `SCOPE.md`, and archive lifecycle | |
 
 ---
 
+<a id="version-11"></a>
+## Version 1.1: Added optional extension recall boundary for memsearch-style layers
+
+**Date:** 2026-04-13
+**Session:** 11c4bd2f-216e-4779-81bf-26d34a4fcaeb
+
+### Changes
+- Updated `memory-governance-and-session-boundary.md` from v1.0 to v1.1.
+- Updated `design/memory-governance-and-session-boundary.design.md` from v1.0 to v1.1.
+- Added an explicit optional-extension recall boundary so memsearch-like extension/plugin layers are treated as supplemental context bridges rather than required infrastructure or semantic truth.
+- Added explicit deferral that coordination ownership for optional recall-layer usage lives in `shared-execution-coordination.md`.
+
+### Summary
+Memory-governance now keeps native memory authority boundaries explicit while modeling memsearch-style recall layers as optional supplemental context bridges rather than required core behavior.
+
+---
+
 <a id="version-10"></a>
 ## Version 1.0: Created first-class memory-governance-and-session-boundary rule chain