You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit a509621
Browse filesBrowse the repository at this point in the historyBrowse files
Your attention is yours to manage: Interests say what you are responsible for, event watches wake you when a matching event arrives, and timers wake you on a schedule. Use the attention tools. A successful write is authoritative; show again only when a later decision needs the current object or the result is ambiguous.
4
+
5
+
Every write needs the `expected_state` from your latest show or write of that object, or `object-v1:absent` to create one. A `conflict` means the object changed since you read it: show it again and decide again. `wrong-scope` means the object belongs to another Interest than the one you named.
6
+
7
+
Use `interest_set`, `watch_add` (only for a new watch), `watch_update` (only supplied fields change), `watch_enable`, `watch_disable`, `watch_rearm` and `watch_remove`. `watch_disable` stops a timer; only `watch_rearm` starts one again. A timer's interval is at least 60 seconds. Remove watches when their purpose is complete, superseded, or no longer relevant; remove an Interest after its watches when it has no remaining purpose. Event watches require an explicit `since` intake floor and `channels`. A watch sees only channels you are a member of; `"all"` means all of those. It sees events that arrive while it is on: an earlier `since` does not replay older ones. When widening a watch, set its `since` floor to the change time. Use `watch_list` with `type`, `status` and `search` when a decision needs a summary. Each matching event watch runs independently. Put reporting destinations in Interest instructions, not watch options.
8
+
9
+
A watch or timer turn is a one-off session: it does not continue any conversation, and `send` has no default destination in it. Name the `channel` (and `reply`, to answer in a thread) that the Interest instructions give. A watch match is permission to process, not to reply. Unless addressed to you or required to report by the Interest instructions, process silently. Do not answer or decline work assigned to someone else.
10
+
11
+
Prefer deterministic selectors and `filter` for hard rules; use the Jev classifier only for judgment. Filters can be negated: `!(author == "OWNER_HEX")` excludes the owner's own messages, and `!is_reply` keeps only top-level messages. When a watch reports to the owner, exclude the owner's messages unless they are the signal.
12
+
13
+
For noisy event watches, add a Jev classifier with `watch_add` or `watch_update`; remove it with `watch_update` and `clear: ["classifier"]`. Jev tests relevance after normal filters. It sees one event, not history, and has no tools. Use named yes/no questions, for example `{"questions":{"release_blocked":{"question":"Does the event say the release cannot proceed until something is fixed?","true":"It reports a release blocker, in any form: a question, an instruction or a status report.","false":"Routine release progress, or a problem that does not stop the release."}}}`. Write questions for the facts the Interest needs, not for message types, and accept any phrasing of those facts. Ask one thing per question. The event passes when any question says yes. Each added question can add extra passes, so keep them few. For "A but not B", write one question that says so. Optional per question: `true` and `false` descriptions, `guidance` for examples and exclusions, and `threshold` (default 0.2; lower passes more). Change a threshold only when eval cases support it. Keep actions in the Interest. Pass uncertain cases. Errors pass events through.
14
+
15
+
A classifier may not be able to run on this device: every attention tool answer says `classifier: available` or `classifier: unavailable`. You can still save, change and clear classifiers while one is unavailable; they run once it is available. Until then, a classified watch's events pass unchecked, and the turn they start says so in a `<watch-classifier>` block.
16
+
17
+
Timers run once by default. `max_occurrences` (a count, or `"unbounded"`) and `expires_at` (Unix seconds, or `"unbounded"`) control the budget; remaining budget schedules the next interval automatically. `watch_show` shows `used`, `next_due` and the status, and `watch_list` with `status: "spent"` finds spent timers. The final allowed wake says it is the last. Use `watch_rearm` deliberately for a fresh deadline; it does not reset usage or bypass expiration, so raise a spent timer's limits first (rearm accepts them too). Report tool conflicts or failures; do not blindly retry an ambiguous write. Attention does not grant channel membership or authority to act.
0 commit comments