@shardworks/guild-starter-kit 0.1.52 → 0.1.53

package/curricula/guild-operations/content.md

@@ -278,6 +278,9 @@ Tools that animas wield during work. Each tool ships with instructions delivered
 - **clock-list** — show pending events
 - **clock-tick** — process the next pending event
 - **clock-run** — process all pending events
+- **clock-start** — start the clockworks daemon
+- **clock-stop** — stop the clockworks daemon
+- **clock-status** — check if the clockworks daemon is running (PID, uptime, log file)
 
 ### Utility Tools
 - **signal** — signal a custom guild event for the Clockworks
@@ -410,7 +413,9 @@ The event name must be declared in `guild.json clockworks.events`. Framework nam
 
 ### Processing Events
 
-Events are not processed automatically. The operator controls when the Clockworks runs:
+Events can be processed manually or automatically via the daemon.
+
+**Manual processing:**
 
 | Command | What it does |
 |---------|-------------|
@@ -418,6 +423,16 @@ Events are not processed automatically. The operator controls when the Clockwork
 | `nsg clock tick [id]` | Process the next pending event, or a specific one by id |
 | `nsg clock run` | Process all pending events until the queue is empty |
 
+**Daemon (automatic processing):**
+
+| Command | What it does |
+|---------|-------------|
+| `nsg clock start [--interval <ms>]` | Start the daemon (polls every 2s by default) |
+| `nsg clock stop` | Stop the daemon |
+| `nsg clock status` | Check if the daemon is running |
+
+The daemon runs as a background process, polling the event queue and processing events as they arrive. Use the `clock-status` tool to verify the daemon is active before dispatching work that depends on automatic event processing.
+
 ### Error Handling
 
 When a standing order fails, the system signals a `standing-order.failed` event. Guilds can respond to this with their own standing orders. A loop guard prevents cascading failures — `standing-order.failed` events triggered by other `standing-order.failed` events are skipped automatically.
@@ -587,3 +602,6 @@ The primary interface is the `nsg` command, organized by noun groups:
 | `nsg clock list` | Show pending events |
 | `nsg clock tick [id]` | Process next pending event (or specific id) |
 | `nsg clock run` | Process all pending events |
+| `nsg clock start [--interval <ms>]` | Start the daemon |
+| `nsg clock stop` | Stop the daemon |
+| `nsg clock status` | Show daemon status |

package/nexus-bundle.json

@@ -21,6 +21,9 @@
     { "package": "@shardworks/nexus-stdlib@0.x", "name": "clock-list" },
     { "package": "@shardworks/nexus-stdlib@0.x", "name": "clock-tick" },
     { "package": "@shardworks/nexus-stdlib@0.x", "name": "clock-run" },
+    { "package": "@shardworks/nexus-stdlib@0.x", "name": "clock-status" },
+    { "package": "@shardworks/nexus-stdlib@0.x", "name": "clock-start" },
+    { "package": "@shardworks/nexus-stdlib@0.x", "name": "clock-stop" },
     { "package": "@shardworks/nexus-stdlib@0.x", "name": "nexus-version" },
     { "package": "@shardworks/nexus-stdlib@0.x", "name": "signal" },
     { "package": "@shardworks/nexus-stdlib@0.x", "name": "work-create" },

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@shardworks/guild-starter-kit",
-  "version": "0.1.52",
+  "version": "0.1.53",
   "description": "Default bundle for new Nexus guilds — tools, training, and migrations",
   "repository": {
     "type": "git",