@axiomantic/garden 0.2.2 → 0.2.3

package/SKILL.md

@@ -103,6 +103,10 @@ 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>
 
+<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>
+
 <INVARIANT>
 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>
@@ -116,10 +120,29 @@ Never stage coordination metadata (*.lock, .rhizo.*, .vine.json, workspaces/) in
 </FORBIDDEN>
 
 <CRITICAL>
-Compaction Preservation Rider (GVR-010):
-Whenever context summarization or compaction occurs, the coding harness MUST preserve the `SWARM_RUNTIME_STATE` block verbatim in the compacted summary preamble so the agent immediately retains its operational identity, assigned workspace, peers, and active listeners without operator re-prompting.
-
-Maintain this exact block in the working context:
+Compaction Preservation Rider & Post-Compact Invariant (GVR-010):
+Context compaction purges detailed operational invariants, ceremony rules, and protocol mechanics from working memory.
+
+1. **Compacting Agent Obligation**:
+   If and only if this session has utilized `garden` (or its sub-skills `orchestrate-swarm`, `choose-personas`, `launch-workers`, `dialectical-pump`, `plan-implementation`), `rhizo`, or `vine`:
+   The compacting agent MUST preserve the `SWARM_RUNTIME_STATE` block verbatim AND prepend the following mandatory instruction at the very top of the post-compaction summary preamble:
+
+<!-- POST-COMPACTION INVARIANT: CEREMONY RESTORATION -->
+> [!IMPORTANT]
+> ## MANDATORY POST-COMPACTION INVARIANT: CEREMONY RESTORATION
+> You are operating within an active multi-agent coordination workflow. Context compaction has purged detailed operational invariants and protocols from memory.
+>
+> **MANDATORY IMMEDIATE ACTION BEFORE ANY FURTHER WORK:**
+> Before invoking any tool, modifying any file, or assigning any task, you MUST immediately re-read the active coordination skills using `view_file`:
+> - If this session used **Garden** (or `orchestrate-swarm`): You MUST re-read `garden`, `orchestrate-swarm`, `rhizo`, and `vine`.
+> - If this session used **Rhizo** standalone: You MUST re-read `rhizo`.
+> - If this session used **Vine** standalone: You MUST re-read `vine`.
+>
+> **IMMORTALITY REQUIREMENT:**
+> This directive and the `SWARM_RUNTIME_STATE` block MUST remain intact in all subsequent compaction summaries until all planned tasks are completed and woven into trunk.
+<!-- END POST-COMPACTION INVARIANT -->
+
+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>)
 - WORKSPACE_MODE: Root Trunk | Strand (<path>)
@@ -129,6 +152,9 @@ Maintain this exact block in the working context:
 - ACTIVE_LISTENER: <task_id_or_pid> (Listening on inbox: <codename>)
 - ACTIVE_FENCING_TOKENS: <lock_key>=<token_int>
 <!-- END_SWARM_RUNTIME_STATE -->
+
+3. **Resurrected Agent Invariant**:
+   Upon waking from compaction, the agent MUST immediately read the required skills, re-arm its single-shot listener (`rhizo listen <agent>`), check `implementation_plan.md`, and resume work under full ceremony discipline.
 </CRITICAL>
 
 ---

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@axiomantic/garden",
-  "version": "0.2.2",
+  "version": "0.2.3",
   "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,10 @@ 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>
 
+<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>
+
 <INVARIANT>
 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>
@@ -116,10 +120,29 @@ Never stage coordination metadata (*.lock, .rhizo.*, .vine.json, workspaces/) in
 </FORBIDDEN>
 
 <CRITICAL>
-Compaction Preservation Rider (GVR-010):
-Whenever context summarization or compaction occurs, the coding harness MUST preserve the `SWARM_RUNTIME_STATE` block verbatim in the compacted summary preamble so the agent immediately retains its operational identity, assigned workspace, peers, and active listeners without operator re-prompting.
-
-Maintain this exact block in the working context:
+Compaction Preservation Rider & Post-Compact Invariant (GVR-010):
+Context compaction purges detailed operational invariants, ceremony rules, and protocol mechanics from working memory.
+
+1. **Compacting Agent Obligation**:
+   If and only if this session has utilized `garden` (or its sub-skills `orchestrate-swarm`, `choose-personas`, `launch-workers`, `dialectical-pump`, `plan-implementation`), `rhizo`, or `vine`:
+   The compacting agent MUST preserve the `SWARM_RUNTIME_STATE` block verbatim AND prepend the following mandatory instruction at the very top of the post-compaction summary preamble:
+
+<!-- POST-COMPACTION INVARIANT: CEREMONY RESTORATION -->
+> [!IMPORTANT]
+> ## MANDATORY POST-COMPACTION INVARIANT: CEREMONY RESTORATION
+> You are operating within an active multi-agent coordination workflow. Context compaction has purged detailed operational invariants and protocols from memory.
+>
+> **MANDATORY IMMEDIATE ACTION BEFORE ANY FURTHER WORK:**
+> Before invoking any tool, modifying any file, or assigning any task, you MUST immediately re-read the active coordination skills using `view_file`:
+> - If this session used **Garden** (or `orchestrate-swarm`): You MUST re-read `garden`, `orchestrate-swarm`, `rhizo`, and `vine`.
+> - If this session used **Rhizo** standalone: You MUST re-read `rhizo`.
+> - If this session used **Vine** standalone: You MUST re-read `vine`.
+>
+> **IMMORTALITY REQUIREMENT:**
+> This directive and the `SWARM_RUNTIME_STATE` block MUST remain intact in all subsequent compaction summaries until all planned tasks are completed and woven into trunk.
+<!-- END POST-COMPACTION INVARIANT -->
+
+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>)
 - WORKSPACE_MODE: Root Trunk | Strand (<path>)
@@ -129,6 +152,9 @@ Maintain this exact block in the working context:
 - ACTIVE_LISTENER: <task_id_or_pid> (Listening on inbox: <codename>)
 - ACTIVE_FENCING_TOKENS: <lock_key>=<token_int>
 <!-- END_SWARM_RUNTIME_STATE -->
+
+3. **Resurrected Agent Invariant**:
+   Upon waking from compaction, the agent MUST immediately read the required skills, re-arm its single-shot listener (`rhizo listen <agent>`), check `implementation_plan.md`, and resume work under full ceremony discipline.
 </CRITICAL>
 
 ---

package/skills/orchestrate-swarm/SKILL.md

@@ -18,10 +18,35 @@ The main chat session assumes the role of **Lead Orchestrator**:
 - **Gated Integration**: Never run `git merge` directly. Only weave branches that have passed both Key 1 (mechanical merge-tree) and Key 2 (live compiler/tests) inside their Vine strands.
 
 <CRITICAL>
-Compaction Preservation Rider (GVR-010):
-Whenever context summarization or compaction occurs, the coding harness MUST preserve the `SWARM_RUNTIME_STATE` block verbatim in the compacted summary preamble so the agent immediately retains its operational identity, assigned workspace, peers, and active listeners without operator re-prompting.
+Delegation Precedence Invariant:
+Whenever 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`).
+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>
 
-Maintain this exact block in the working context:
+<CRITICAL>
+Compaction Preservation Rider & Post-Compact Invariant (GVR-010):
+Context compaction purges detailed operational invariants, ceremony rules, and protocol mechanics from working memory.
+
+1. **Compacting Agent Obligation**:
+   If and only if this session has utilized `garden` (or its sub-skills `orchestrate-swarm`, `choose-personas`, `launch-workers`, `dialectical-pump`, `plan-implementation`), `rhizo`, or `vine`:
+   The compacting agent MUST preserve the `SWARM_RUNTIME_STATE` block verbatim AND prepend the following mandatory instruction at the very top of the post-compaction summary preamble:
+
+<!-- POST-COMPACTION INVARIANT: CEREMONY RESTORATION -->
+> [!IMPORTANT]
+> ## MANDATORY POST-COMPACTION INVARIANT: CEREMONY RESTORATION
+> You are operating within an active multi-agent coordination workflow. Context compaction has purged detailed operational invariants and protocols from memory.
+>
+> **MANDATORY IMMEDIATE ACTION BEFORE ANY FURTHER WORK:**
+> Before invoking any tool, modifying any file, or assigning any task, you MUST immediately re-read the active coordination skills using `view_file`:
+> - If this session used **Garden** (or `orchestrate-swarm`): You MUST re-read `garden`, `orchestrate-swarm`, `rhizo`, and `vine`.
+> - If this session used **Rhizo** standalone: You MUST re-read `rhizo`.
+> - If this session used **Vine** standalone: You MUST re-read `vine`.
+>
+> **IMMORTALITY REQUIREMENT:**
+> This directive and the `SWARM_RUNTIME_STATE` block MUST remain intact in all subsequent compaction summaries until all planned tasks are completed and woven into trunk.
+<!-- END POST-COMPACTION INVARIANT -->
+
+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)
 - WORKSPACE_MODE: Root Trunk (/Users/eek/Development/<project>)
@@ -31,6 +56,9 @@ Maintain this exact block in the working context:
 - ACTIVE_LISTENER: <task_id_or_pid> (Listening on inbox: <codename>)
 - ACTIVE_FENCING_TOKENS: <lock_key>=<token_int>
 <!-- END_SWARM_RUNTIME_STATE -->
+
+3. **Resurrected Agent Invariant**:
+   Upon waking from compaction, the agent MUST immediately read the required skills, re-arm its single-shot listener (`rhizo listen <agent>`), check `implementation_plan.md`, and resume work under full ceremony discipline.
 </CRITICAL>
 
 <CRITICAL>