diff options
| author | Craig Jennings <c@cjennings.net> | 2026-05-31 00:07:03 -0500 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2026-05-31 00:07:03 -0500 |
| commit | 8c0eca8375db2c2d346f5fd08ac752209349f94e (patch) | |
| tree | d62abf74ad991ca54f1dcdcc1b3f225c4e8633a1 /.ai/protocols.org | |
| parent | ddcde66a768758844a5be705de6a89e68697fa1a (diff) | |
| download | rulesets-8c0eca8375db2c2d346f5fd08ac752209349f94e.tar.gz rulesets-8c0eca8375db2c2d346f5fd08ac752209349f94e.zip | |
feat(workflows): add monitor-inbox workflow + inbox-status script
Handoffs that arrive mid-session used to sit unseen until the next startup or a manual check. Today's burst of cross-project handoffs made that gap obvious. I added monitor-inbox.org, the cadence-and-decision layer over process-inbox: check the inbox at every task boundary, decide act-now (just do it) versus file (ask, with filing as option 1), and reply to the sender. An opt-in background-monitor /loop recipe covers unattended watching.
inbox-status (with bats tests) is the cheap check the cadence calls. It lists unprocessed handoffs and exits nonzero when any are pending, using the same artifact exclusions as the wrap-up sanity check. protocols.org gets a short cadence note so the habit fires every session, and INDEX.org lists the new workflow. The act-vs-file rule (act-now is silent, filing asks with file as option 1, ambiguity asks) is the decision protocol we settled today.
Diffstat (limited to '.ai/protocols.org')
| -rw-r--r-- | .ai/protocols.org | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/.ai/protocols.org b/.ai/protocols.org index 1499fbb..25e634a 100644 --- a/.ai/protocols.org +++ b/.ai/protocols.org @@ -180,6 +180,16 @@ When the user starts a new task that will produce file artifacts, propose the =w Canonical rule: =~/code/rulesets/claude-rules/working-files.md=. +** Inbox Monitoring Cadence — Check at Task Boundaries + +Check =inbox/= at every task boundary (after finishing a unit of work, before reporting back or asking "what's next") — not only at startup or when asked. Handoffs arrive mid-session; this keeps them from piling up unseen. The check is one command: + +#+begin_src bash +.ai/scripts/inbox-status -q +#+end_src + +Exit 1 means handoffs are pending — process them per =process-inbox.org=. For each accepted handoff, the act-vs-file rule: *act now* when it's clear, bounded, low-risk, in-scope, and cheaper than deferring — just do it, no asking; *file* otherwise — ask first, with filing as option 1 and "do it now" as option 2; *ask* if unsure. Always reply to a handoff's sender (confirm on accept, the why on reject). Full process, the reply discipline, and the opt-in background-monitor =/loop= recipe live in =monitor-inbox.org=. + * Important Terminology ** "Let's run the [X] workflow" vs "I want to create an [X] workflow" |