Attenty

Mark this bot's own events handled, so read_feedback stops returning them. Ids that are not yours, or do not exist, are ignored rather than erroring.

ack

Call this first, every session, before posting anything. Returns the user's time zone (needed to compute setDate), your connectedAt, and their CURRENT zones — a user can rename, reorder, add or delete zones at any time, so route only to what this call returns, never a name remembered from an earlier session.

get_me

The user's Rule Book: every rule confirmed by the user (whichever bot authored it), plus your own proposals still awaiting a decision. Apply `active` rules; treat `proposed` ones — your own — as a hypothesis, not yet agreed.

list_rules

The user's own ranking of their senders, per zone. Attenty sorts by your priority and then by this — a bot that ignores it will read a low ranking's dismissals as a verdict on its own priority call when the item was simply below the fold.

list_senders

Every zone on this account with its full configuration: sort order, whether it has a target time, whether it carries forward, and the description the user wrote for what belongs there (route by that description, never by a zone's name).

list_zones

Create or update items on the user's canvas — the Crafted Surface `post(shape)` operation. `items` is a full statement of each one, idempotent on (source, sourceItemId): re-posting the same pair overwrites every field you send, so re-derive nothing you already posted and route only to a zoneName this account's list_zones call actually returned.

post

Propose what you have worked out about this user. An array, idempotent on your own ruleKey — re-proposing the same conclusion updates it rather than duplicating it. Never changes a rule's status: one the user retired stays retired, and pinned wording is never overwritten.

propose_rules

This bot's unacked user actions, oldest first — the Crafted Surface `read_feedback()` operation. Every gesture the user made on your items (dismissed, moved, checked, deferred, and the rest) comes back here; nothing you post ever improves if this is never called. A dismissal means the user is done with the item, not that they rejected it. New item payloads include event-time zoneId and sourceAccount; old events may lack them and cannot authorize scoped source actions from current readback. Pass `since` (an ISO timestamp from an event you already saw) to page forward. Safe events are returned with withheld ID/timestamp references and a notice. Withheld events stay pending and are reported regardless of since; never acknowledge them or advance a persistent cursor past them.

read_feedback

Read only this authenticated bot's items with the original single-message content, separate contentPreview summary, source/account, current zone and read-only handled/restored/pin state. Defaults to active; request dismissed or spam explicitly. Page with limit/offset until empty. Preserve the body and all fields when updating; current state cannot establish historical event scope.

list_items

Send an in-app reply as this authenticated bot. Echo the exact source + sourceItemId from chat_message, or omit both for general chat. Never substitute a thread ID. Supply an opaque idempotencyKey (for example the feedback event ID); retry with the same key and identical content/pair to avoid duplicates during the message's 30-day retention. Conflicting reuse fails. Does not contact the upstream source. matchedItem=false also occurs for general or deleted-item replies.

reply_chat