What happens to your choices

1. Saved at once, twice. Every tap and every keystroke in a note is written to this phone first, then to the board's shared store, and retried until the store confirms it. The line under the title says "All saved ✓" once nothing is waiting. If it says otherwise, keep the page open; "Copy unsaved" gives you the pending actions as text to paste into the session.
2. Nothing is overwritten. Each tap is a separate, permanent record. Undo adds a new record rather than erasing the old one, and Claude never rewrites what you sent. Your card keeps its place after a tap until you switch filters, so the next tap cannot land on a different task.
3. Queued for Claude. Each Done, Skip, answer, "Post note only" or "Have an agent do it" adds an entry to an outbox. The card shows its receipt: "Saved · waiting for Claude", then "On GitHub ↗" (a link to the comment), or "Sent to a worker".
4. Recorded on GitHub. The board's Claude session checks the outbox every few minutes ("Claude checked N min ago" under the title). It posts your answer or note as a comment on the issue, and closes the issue only when you press "Done & close issue". It never comments in an organisation marked read-only.
5. Done by a worker. Decisions and "Have an agent do it" go to one worker session per repository, a few at a time, and only while the machine has spare memory. The rest wait in the queue for the next check.
6. Notes are drafts until you press a button. A typed note is saved but not posted on its own. It goes out with the next Done, Skip, answer or "Post note only".

The session also copies the whole store to disk on every check, so a lost artifact would not lose your answers.

Shrinking the pile

• Items that look done or obsolete are gathered in Runs → "Close what is already done": skim, Skip any you want kept, then close the rest in one go.
• Decisions are on the Decide tab as single taps: ★ accept the recommendation, pick another option, or "You decide".
• Repeated chores (the same web form for many packages, server chores, API keys) are grouped on the Runs tab, so they become one sitting or one session prompt instead of many.
• Listening, recording and device tests are one headphones sitting: filter on the Physical tier.

What helps on the phone

• GitHub Mobile covers the "tap" tier: comment on an issue, close it, review a PR, approve and merge. It does not open repository settings (secrets, Pages, environments); use the phone browser for those, with the desktop site if a page is cramped.
• A Claude app with Remote Control is the "session" tier: paste a card's prompt into the session on the machine it names.
• A passkey for package registries and consoles signs you in on the phone without a password manager round trip.

Back at a desk

• The Mac only filter is the desk-day list. Every card keeps its links and prompt, so nothing has to be rediscovered.