ticlawk 0.1.16-dev.25 → 0.1.16-dev.26

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/package.json +1 -1
  2. package/src/runtimes/_shared/handbook/GOAL_AUTHORITY.md +2 -2
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "ticlawk",
3
- "version": "0.1.16-dev.25",
3
+ "version": "0.1.16-dev.26",
4
4
  "description": "Local connector that links agent harnesses (Claude Code, Codex, OpenClaw, opencode, Pi) to the Ticlawk mobile app.",
5
5
  "type": "module",
6
6
  "main": "ticlawk.mjs",
package/src/runtimes/_shared/handbook/GOAL_AUTHORITY.md CHANGED
@@ -11,8 +11,8 @@ Use this in DMs, and in groups where your conversation role is admin or owner.
11
11
 
12
12
  ## Goal Setup When No Specific Goal Exists
13
13
 
14
- - Do not turn every one-off request into a durable goal. Answer direct asks normally unless the owner expresses a lasting aspiration, ongoing objective, tracking need, reminder cadence, multi-step roadmap, or resource/coordinator need.
15
- - When durable intent is visible and no suitable goal exists, propose making it a conversation goal. Clarify whether it belongs in the current DM, an existing group/workstream, or a new workstream before writing state.
14
+ - When the current conversation has no goal, first judge privately whether the owner might be interested in setting a conversation goal around what they are discussing. Write that judgment and a reason of 20 words or fewer in normal assistant output; do not send it through Ticlawk.
15
+ - If it looks like a one-off request, answer it normally. If the owner may want an ongoing goal, naturally ask whether to set one for the current DM, an existing group/workstream, or a new workstream before writing state.
16
16
  - Clarify only the details needed to proceed: goal definition, success/completion criteria, time range, constraints/boundaries, rough approach or roadmap, the agent's deliverables, owner responsibilities, required files/repos/accounts/credentials/budget/resources, dashboard decision view and metrics, and briefing triggers/cadence.
17
17
  - Before setting a charter, summarize the proposed short charter and ask for confirmation. Keep charters to the local goal, roles, success criteria, and boundaries; do not put shared workflow law, dashboard state, task status, or long playbooks in the charter.
18
18
  - After confirmation, write the charter if you have scope authority. Then create and publish the initial dashboard as part of goal setup, push it to the owner for review, and ask whether the layout/style/decision view are satisfactory. Create reminders/resources only when useful, and seed group tasks only in group/workstream scope. Then enter the normal goal loop.