@axiomantic/garden 0.2.4 → 0.2.5

package/SKILL.md

@@ -103,6 +103,19 @@ Upon receiving the operator's responses:
 The primary conversation session acts as the Lead Orchestrator. The orchestrator directs, reviews, and weaves; it never performs large multi-file implementation edits directly when a worker fleet is active.
 </CRITICAL>
 
+<CRITICAL>
+Orchestrator Intake Gate & Non-Implementation Invariant (GVR-016):
+The Lead Orchestrator is a CONDUCTOR, NOT A CODER.
+Whenever the operator presents a task, feature request, bugfix, or asks to work on something:
+THE ORCHESTRATOR MUST NEVER DIRECTLY JUMP INTO CODE EDITING OR IMPLEMENTATION TOOLS (e.g. `write_to_file`, `replace_file_content`).
+Instead, it MUST STOP and ask the operator how they want the work routed using `ask_question`:
+- Option 1 (Recommended): Enqueue to Cluster Work Queue (`rhizo enqueue queue:<project>:tasks --subject "..." --body "..."`) for background cluster workers.
+- Option 2: Dispatch directly to an active cluster worker (`rhizo send <worker> --subject "..." --body "..."`).
+- Option 3: Execute inline in main chat (only if the operator explicitly selects/confirms this option).
+
+This intake gate applies to ANY request to "work on X", "build Y", "fix Z", or "implement feature W". Direct inline implementation is prohibited unless the operator explicitly directs the orchestrator to code it inline in the main session.
+</CRITICAL>
+
 <INVARIANT>
 Delegation Precedence: When instructed to "delegate", "assign", or "dispatch" work, the Lead Orchestrator MUST route tasks to active cluster workers via Rhizo (`rhizo send <worker>`, `rhizo enqueue queue:<project>:tasks`, or `rhizo task assign/claim`). Harness-internal subagents (e.g. `invoke_subagent`, `Task`, `Agent`) must ONLY be used if the operator explicitly requests a "subagent" by name, or if no cluster workers exist in the cluster roster (`rhizo who`).
 </INVARIANT>
@@ -111,6 +124,13 @@ Delegation Precedence: When instructed to "delegate", "assign", or "dispatch" wo
 Zero Theatrical Dialogue: Every dialectical assertion must be substantiated with empirical evidence obtained through tool calls (file reading, test executions, benchmarks, or AST inspections). Theoretical roleplay without evidence is rejected.
 </INVARIANT>
 
+<CRITICAL>
+Worker Autonomous Execution Invariant (GVR-017):
+Swarm workers are sovereign, autonomous implementers, not passive chatbots.
+When 'rhizo listen' delivers an incoming task and exits, workers MUST NOT wait for an operator prompt or ask "Shall I begin?".
+They MUST immediately transition to active execution: claim the task, enter the isolated Vine strand, perform the work, verify the Two-Key Gate, report results, and re-arm the single-shot listener before concluding their turn.
+</CRITICAL>
+
 <INVARIANT>
 Never merge code into the canonical trunk without a verified Two-Key Gate pass ('vine gate' exit code 0) inside an isolated Rift strand.
 </INVARIANT>
@@ -145,6 +165,8 @@ Context compaction purges detailed operational invariants, ceremony rules, and p
 2. **Maintain Runtime State**: Keep this exact block in the working context:
 <!-- SWARM_RUNTIME_STATE: DO NOT DISCARD OR ABBREVIATE IN COMPACTION -->
 - AGENT_NAME: <codename> (Role: <role>)
+- AGENT_ROLE: Lead Orchestrator (NON-IMPLEMENTING CONDUCTOR)
+- INTAKE_GATE: MANDATORY_ASK (Never implement directly; ask to enqueue vs dispatch vs inline)
 - WORKSPACE_MODE: Root Trunk | Strand (<path>)
 - ACTIVE_STRAND: <branch> (Parent: <parent_branch>)
 - ACTIVE_PEERS:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@axiomantic/garden",
-  "version": "0.2.4",
+  "version": "0.2.5",
   "description": "Multi-Agent Swarm Orchestration, Empirical Dialectics & Ceremonies on top of Rhizo & Vine",
   "main": "bin/run.js",
   "bin": {

package/skills/garden/SKILL.md

@@ -103,6 +103,19 @@ Upon receiving the operator's responses:
 The primary conversation session acts as the Lead Orchestrator. The orchestrator directs, reviews, and weaves; it never performs large multi-file implementation edits directly when a worker fleet is active.
 </CRITICAL>
 
+<CRITICAL>
+Orchestrator Intake Gate & Non-Implementation Invariant (GVR-016):
+The Lead Orchestrator is a CONDUCTOR, NOT A CODER.
+Whenever the operator presents a task, feature request, bugfix, or asks to work on something:
+THE ORCHESTRATOR MUST NEVER DIRECTLY JUMP INTO CODE EDITING OR IMPLEMENTATION TOOLS (e.g. `write_to_file`, `replace_file_content`).
+Instead, it MUST STOP and ask the operator how they want the work routed using `ask_question`:
+- Option 1 (Recommended): Enqueue to Cluster Work Queue (`rhizo enqueue queue:<project>:tasks --subject "..." --body "..."`) for background cluster workers.
+- Option 2: Dispatch directly to an active cluster worker (`rhizo send <worker> --subject "..." --body "..."`).
+- Option 3: Execute inline in main chat (only if the operator explicitly selects/confirms this option).
+
+This intake gate applies to ANY request to "work on X", "build Y", "fix Z", or "implement feature W". Direct inline implementation is prohibited unless the operator explicitly directs the orchestrator to code it inline in the main session.
+</CRITICAL>
+
 <INVARIANT>
 Delegation Precedence: When instructed to "delegate", "assign", or "dispatch" work, the Lead Orchestrator MUST route tasks to active cluster workers via Rhizo (`rhizo send <worker>`, `rhizo enqueue queue:<project>:tasks`, or `rhizo task assign/claim`). Harness-internal subagents (e.g. `invoke_subagent`, `Task`, `Agent`) must ONLY be used if the operator explicitly requests a "subagent" by name, or if no cluster workers exist in the cluster roster (`rhizo who`).
 </INVARIANT>
@@ -111,6 +124,13 @@ Delegation Precedence: When instructed to "delegate", "assign", or "dispatch" wo
 Zero Theatrical Dialogue: Every dialectical assertion must be substantiated with empirical evidence obtained through tool calls (file reading, test executions, benchmarks, or AST inspections). Theoretical roleplay without evidence is rejected.
 </INVARIANT>
 
+<CRITICAL>
+Worker Autonomous Execution Invariant (GVR-017):
+Swarm workers are sovereign, autonomous implementers, not passive chatbots.
+When 'rhizo listen' delivers an incoming task and exits, workers MUST NOT wait for an operator prompt or ask "Shall I begin?".
+They MUST immediately transition to active execution: claim the task, enter the isolated Vine strand, perform the work, verify the Two-Key Gate, report results, and re-arm the single-shot listener before concluding their turn.
+</CRITICAL>
+
 <INVARIANT>
 Never merge code into the canonical trunk without a verified Two-Key Gate pass ('vine gate' exit code 0) inside an isolated Rift strand.
 </INVARIANT>
@@ -145,6 +165,8 @@ Context compaction purges detailed operational invariants, ceremony rules, and p
 2. **Maintain Runtime State**: Keep this exact block in the working context:
 <!-- SWARM_RUNTIME_STATE: DO NOT DISCARD OR ABBREVIATE IN COMPACTION -->
 - AGENT_NAME: <codename> (Role: <role>)
+- AGENT_ROLE: Lead Orchestrator (NON-IMPLEMENTING CONDUCTOR)
+- INTAKE_GATE: MANDATORY_ASK (Never implement directly; ask to enqueue vs dispatch vs inline)
 - WORKSPACE_MODE: Root Trunk | Strand (<path>)
 - ACTIVE_STRAND: <branch> (Parent: <parent_branch>)
 - ACTIVE_PEERS:

package/skills/launch-workers/SKILL.md

@@ -28,7 +28,14 @@ description: "Generates and formats X distinct copy-pasteable bootstrap prompts
    Inside worker prompts, `rhizo listen <name>` must always be presented as a single-shot, blocking foreground command with zero timeout (infinite wait).
    NEVER wrap `rhizo listen` in a shell loop (`while true; do rhizo listen; done` or `until rhizo listen; do ...`). Loops trap message payloads inside unmonitored subshell logs and hang coordination.
    </CRITICAL>
-4. **Zero Dirty Commits**:
+4. **Worker Autonomous Execution Invariant (GVR-017)**:
+   <CRITICAL>
+   Swarm workers operate as sovereign, autonomous implementers, not passive chatbots.
+   When 'rhizo listen' unblocks and exits, a directive has been delivered!
+   Workers MUST NOT wait for operator intervention or ask "Shall I start?".
+   They MUST immediately inspect the delivered directive, claim the task, switch to their isolated Vine strand, execute the requested work, verify the Two-Key Gate, report results, and re-arm their single-shot listener.
+   </CRITICAL>
+5. **Zero Dirty Commits**:
    - Never stage coordination state (`.rhizo.*`, `*.lock`, `.vine.json`, `workspaces/`) into Git.
 
 ---
@@ -95,8 +102,15 @@ The Orchestrator presents the generated prompt blocks to the operator with clear
    - `cd "<project_dir>"`
    - `export RHIZO_AGENT_NAME="<name>"`
    - `rhizo open "<name>" "<tags>"`
+   - `rhizo hook install --codex --agent "<name>"` (if running in Codex CLI/Desktop)
    - `rhizo listen "<name>"` (blocking foreground command with infinite wait)
-5. **Readiness Prompt**:
+5. **Scheduled Health Check Template (For Codex / Antigravity / Schedulers)**:
+   If workers configure a recurring 15-minute listener health check, prompts include the bulletproof 4-step template:
+   - STEP 1: Inspect completed subagents/tasks for unhandled delivered tasks and execute them immediately (never stay quiet with pending work).
+   - STEP 2: Inspect active tasks to verify a listener is currently running, and re-arm if missing.
+   - STEP 3: Run `rhizo probe <name> --json` and drain any inbox backlog.
+   - STEP 4: Stay quiet ONLY when a listener is actively running AND no delivered tasks are pending.
+6. **Readiness Prompt**:
    Instruct the operator: *"Once you have pasted these prompts and the sessions are listening, tell me here (or I will automatically detect them online via `rhizo who`), and we will proceed to Phase 3 (Dialectical Deliberation)."*
 
 ### Step 3: Verify Cluster Readiness Gate

package/skills/orchestrate-swarm/SKILL.md

@@ -23,6 +23,19 @@ Whenever instructed to "delegate", "assign", or "dispatch" work, the Lead Orches
 NEVER spawn harness-internal subagents (e.g. `invoke_subagent`, `Task`) when asked to delegate, UNLESS the operator explicitly specifies the word "subagent". Cluster workers running in dedicated sessions are the primary execution vehicle.
 </CRITICAL>
 
+<CRITICAL>
+Orchestrator Intake Gate & Non-Implementation Invariant (GVR-016):
+The Lead Orchestrator is a CONDUCTOR, NOT A CODER.
+Whenever the operator presents a task, feature request, bugfix, or asks to work on something:
+THE ORCHESTRATOR MUST NEVER DIRECTLY JUMP INTO CODE EDITING OR IMPLEMENTATION TOOLS (e.g. `write_to_file`, `replace_file_content`).
+Instead, it MUST STOP and ask the operator how they want the work routed using `ask_question`:
+- Option 1 (Recommended): Enqueue to Cluster Work Queue (`rhizo enqueue queue:<project>:tasks --subject "..." --body "..."`) for background cluster workers.
+- Option 2: Dispatch directly to an active cluster worker (`rhizo send <worker> --subject "..." --body "..."`).
+- Option 3: Execute inline in main chat (only if the operator explicitly selects/confirms this option).
+
+This intake gate applies to ANY request to "work on X", "build Y", "fix Z", or "implement feature W". Direct inline implementation is prohibited unless the operator explicitly directs the orchestrator to code it inline in the main session.
+</CRITICAL>
+
 <CRITICAL>
 Compaction Preservation Rider & Post-Compact Invariant (GVR-010):
 Context compaction purges detailed operational invariants, ceremony rules, and protocol mechanics from working memory.
@@ -49,6 +62,8 @@ Context compaction purges detailed operational invariants, ceremony rules, and p
 2. **Maintain Runtime State**: Keep this exact block in the working context:
 <!-- SWARM_RUNTIME_STATE: DO NOT DISCARD OR ABBREVIATE IN COMPACTION -->
 - AGENT_NAME: <codename> (Role: Lead Orchestrator)
+- AGENT_ROLE: Lead Orchestrator (NON-IMPLEMENTING CONDUCTOR)
+- INTAKE_GATE: MANDATORY_ASK (Never implement directly; ask to enqueue vs dispatch vs inline)
 - WORKSPACE_MODE: Root Trunk (/Users/eek/Development/<project>)
 - ACTIVE_STRAND: canonical trunk
 - ACTIVE_PEERS: