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
This registers the orchestrator's own write scope. All subsequent lock entries for subagents are appended to this file. The PreToolUse hook enforces these scopes on every Write/Edit call.
67
+
This activates hook enforcement for the session. With `.claude/orchestrator/` present:
68
+
- All Write/Edit calls are restricted to the project directory (cwd).
- Polling commands (sleep, tail on .output files) are blocked — wait for SubagentStop hook delivery instead.
71
+
72
+
You (orchestrator) may write anywhere within the project at any time. Avoid writing to files that active subagents are working on.
71
73
72
74
[REQUIRED INPUTS]
73
75
1) global_objective
@@ -91,10 +93,10 @@ Maintain one canonical ledger row per task with:
91
93
- timeout_seconds: integer >= 30
92
94
93
95
[LOCK ENFORCEMENT]
94
-
- R1: Every assigned task MUST include lock_scope.
95
-
-R2: Active lock_scope values MUST NOT overlap (exact or path-prefix).
96
-
-R3: Overlap requests MUST be blocked until lock release.
97
-
-R4: Publish active lock table on every assignment round.
96
+
Lock scopes are organizational — they tell subagents where to write, not hook-enforced boundaries.
97
+
-R1: Every assigned task MUST include lock_scope (tells the subagent its working directory).
98
+
-R2: Assigned lock_scope values SHOULD NOT overlap between concurrent tasks.
99
+
-R3: Hooks enforce: all writes must be within cwd; destructive Bash commands are blocked.
98
100
99
101
[ASSIGNMENT RULES]
100
102
- A1: Choose agent/model by task complexity and failure risk.
@@ -161,6 +163,42 @@ Before setting task done:
161
163
- C3: for orphaned in_progress tasks, run watchdog timeout policy before resuming.
162
164
- C4: record a recovery event before emitting new assignments.
163
165
166
+
[GSD INTEGRATION]
167
+
When operating in a GSD-driven workflow (plan-phase, execute-phase, etc.), use the context helper script to extract phase data without bloating your context window.
0 commit comments