ticlawk 0.1.16-dev.20 → 0.1.16-dev.21

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ticlawk",
-  "version": "0.1.16-dev.20",
+  "version": "0.1.16-dev.21",
   "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/goal-task-protocol.mjs

@@ -126,12 +126,12 @@ ${buildGoalSetupRules()}
   4. Execute the next task yourself when appropriate, or create/assign a task when coordination is needed.
   5. Check whether the result closes the gap.
   6. Return to evaluating current facts against the goal.
-- During each goal-loop iteration, explicitly write a private loop check before acting: current facts, goal/success criterion, gap, next action, and stop/continue decision. Treat tool calls, file edits, task updates, dashboard/briefing writes, and \`ticlawk message send\` as actions. This is for your execution discipline, not a chat message. Do not send the private loop check through ${BRAND_NAME} unless the owner explicitly asks for that analysis.
+- At goal-loop boundaries, explicitly write a private goal loop check: current facts, goal/success criterion, gap, next action, and stop/continue decision. Do this when entering the goal loop and after checking whether a task result closes the gap. This is for your execution discipline, not a chat message. Do not send the private goal loop check through ${BRAND_NAME} unless the owner explicitly asks for that analysis.
 - Stop the loop only when there is no meaningful gap, progress is blocked because the owner needs to provide input/resources/permission/confirmation/decision, or progress depends on an external/time-based wait.
 - If there is no gap, say so briefly. If the goal is complete, report completion.
 - If user input, resources, permission, confirmation, or a decision is needed, publish a briefing with one clear bundled request to the owner.
 - If progress depends on an external or time-based future state and no agent or owner can act now, use a reminder or explicit resume condition rather than silently stalling. Do not use reminders to defer an executable next step or an owner decision/request.
-- When reviewing returned task work, evaluate the evidence against the task and current goal before marking it done or using it in reports. If the task is complete, update task state, then immediately run the private loop check against the updated facts before dashboard, MEMORY.md, briefing, or wrap-up updates.
+- When reviewing returned task work, evaluate the evidence against the task and current goal before marking it done or using it in reports. If the task is complete, update task state, then immediately run the private goal loop check against the updated facts before dashboard, MEMORY.md, briefing, or wrap-up updates.
 - Keep persistent state surfaces distinct: dashboard for goal-level reporting, MEMORY.md for your local continuity, and briefings for active owner notifications.
 - Publish briefings and update dashboards only from DMs you own or groups where you are admin/owner.
 `);