ticlawk 0.1.17-dev.12 → 0.1.17-dev.13

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ticlawk",
-  "version": "0.1.17-dev.12",
+  "version": "0.1.17-dev.13",
   "description": "Local connector that links agent harnesses (Claude Code, Codex, OpenClaw, opencode, Pi) to the Ticlawk mobile app.",
   "type": "module",
   "main": "ticlawk.mjs",

package/src/runtimes/_shared/handbook/GOAL_AUTHORITY.md

@@ -8,9 +8,14 @@ The goal loop runs in the backend **goal lane**. Your chat-side job is to handle
 
 ## Handling a message
 
-- Answer the message, send the result, and stop.
-- If the message sets, clarifies, or changes the goal, also write it into the charter with `ticlawk charter set` (the per-turn goal block shows you the current charter and how to edit it). That hands the change to the goal lane. If the goal is unchanged, just answer.
-- Scope: in a DM you own the goal and the charter; in a group as admin/owner you also own the task board, membership, and the owner-facing surfaces.
+The goal lane does the goal's actual work — it runs the loop and carries out the goal's tasks (experiments, builds, and the like). Your chat-side job is the charter, approvals, and talking to the owner; you do not carry out the goal's work yourself in a chat turn. Read the incoming message as one of:
+
+- **Approving or rejecting** something ("go ahead", "approved", "no, hold off") — the goal lane is waiting on an approval. Resolve it (see Owner approvals); resolving resumes the lane and it does the work. Don't do the work yourself.
+- **Setting, clarifying, or changing the goal** — write it into the charter with `ticlawk charter set` (the per-turn goal block shows the current charter and how to edit it). That re-aims the lane.
+- **Telling you to start or continue the goal's work** ("get going", "run it") — that work belongs to the goal lane. Don't run experiments, builds, or its tasks here. Acknowledge, make sure the charter is right and any pending approval is resolved (`ticlawk approval list`), and let the lane carry it out.
+- **A genuine one-off aside**, not part of pursuing the chartered goal — just answer it.
+
+Scope: in a DM you own the goal and the charter; in a group as admin/owner you also own the task board, membership, and the owner-facing surfaces.
 
 ## Owner approvals
 

package/src/runtimes/_shared/wake-prompt.mjs

@@ -101,16 +101,23 @@ If this message sets a goal, write it into the charter — the goal and what "do
 `);
   }
 
-  // The goal lane (transition deliveries) executes against the charter; its
-  // per-step instructions come from the goal-step prompt, so here the charter
-  // is just the goal/success spec. The chat lane keeps the charter correct;
-  // writing it (charter set) is what re-aims the goal lane. This authorityLine
-  // is the single home for the operative "edit the charter, write it whole"
-  // instruction — GOAL_AUTHORITY.md only describes the flow, not the mechanics.
+  // For the goal-authority chat lane, lead with what work on the goal is doing
+  // right now (from goal_lane_state, attached by the claim) — in plain terms,
+  // not internal state names — so the agent acts on fact: resolve a pending
+  // approval, don't redo work already running, and use charter set for a goal
+  // change. Transition deliveries (the goal loop's own steps) get the spec only.
+  const gl = msg.goal_lane_state && typeof msg.goal_lane_state === 'object' ? msg.goal_lane_state : null;
+  const stateLine = !gl
+    ? ''
+    : gl.pending_approval
+      ? `Work on this goal is paused, waiting for you to approve: "${gl.pending_approval.title}". A go-ahead from you here is that approval — resolve it; the work then resumes on its own, you don't redo it.`
+      : (gl.state && gl.state !== 'suspended')
+        ? `Work on this goal is already running on its own in the background — don't redo it in your reply.`
+        : `No work on this goal is running right now.`;
   const authorityLine = msg.reason === 'transition'
     ? 'This is the goal and success spec for this conversation. Run the current step against it.'
     : hasGoalAuthority(msg)
-      ? `The backend goal lane is driving this goal; handle the incoming message and reply. If the message changes the goal, edit the charter shown above and write it back in full with \`ticlawk charter set --conversation ${conversationId}\` (body on stdin) — change only what actually changed and keep the rest verbatim. Writing it is what hands the change to the goal lane. See GOAL_AUTHORITY.md.`
+      ? `${stateLine ? stateLine + ' ' : ''}Handle this message and reply. If it changes the goal, edit the charter shown above and write it back in full with \`ticlawk charter set --conversation ${conversationId}\` (body on stdin) — change only what actually changed and keep the rest verbatim. That re-aims the work. See GOAL_AUTHORITY.md.`
       : 'Use it as current group goal and role context. The group admin owns charter and dashboard changes unless they explicitly delegate them.';
   return promptBlock(`
 [conversation_goal]