goal

Goal

A goal repeats checks until an observable result and the owner's closure. Use remind for a message or action at a named time, helper for work that finishes in one run. Watch tells the owner about new items under an agreed responsibility; a goal checks by schedule and acts within may until closure. The owner sees the word "goal" in confirmations and buttons. CORE goals remain standing context in CORE, while this tool follows a particular result.

Set up

1. Read the request and context. Identify the observable result, sources, people involved and when to check again. Ask once for missing information that determines the result or boundaries. Reuse what the owner already said.
2. Write text as the result and plan as the next check and its sources. Convert the owner's next-check time to a form accepted by the tool.

Boundaries

Before start, make actions on the owner's behalf explicit. Copy only the owner's words into may: whom to contact, what to send, whether to show the text before sending. If correspondence requires an unstated permission, ask once before starting. For observation and drafts, pass may: "" explicitly. Tell the owner that you will look and prepare drafts and sending needs their permission. Later permission updates may with their words, preserving the existing boundary.

Confirm and follow

1. Call goal start with text, may, plan and an agreed next_check. Read the receipt. Name the result, saved boundary, check frequency and any waiting reason. Scheduled checks continue when Watch is off. Build the nearest start from nextCheckAtMs, quietHour, quietToHour and checks_today: wait until quiet hours end, or until the next day when the receipt's checksPerDay is reached. Take frequency from intervalMs.
2. On "how's it going?", call goal list. Read any untold row with helper outcome. Explain the plan, next check, checks today and pause.
3. Retell a check's Outcome with its substance, evidence, completed actions and question. Call goal list before choosing buttons by current status. For proposed, ask "Goal «…» выполнен?" and offer "Закрыть goal" and "Продолжай". For paused, offer "Продолжай". Use the owner's language and rich-replies; button data names the goal id and action. An absent goal gets a text reply. The owner's instruction or tap calls goal close or goal resume; a stale button gets the tool's refusal in plain words.
4. Put the owner's answer into plan through goal update, keeping sources and agreed boundaries. New permission also updates may. "Проверь сейчас" calls goal update with next_check: "now". After the receipt, say you will write only if something new is found; a check with no news stays silent. Promise to report a failure only after the third consecutive failure; the first two stay silent. Repeat a named time in the confirmation.
5. Tell an expired pause once in the conversation and offer to continue. A third consecutive failure has its own Outcome to retell with the pause.