Status: Accepted

Bot Inbox read models project canonical Admissions

The Human-visible Bot Inbox entry and the Bot-scoped Attention query read inbox_admissions, source_events, and channel_placements from the operational database. At the Messaging commit boundary, an archived PersonaBot is excluded from new recipient Admissions while the Source Event and Channel placement still commit for active peers and history. They do not own a separate inbox item or message body. A query page is scoped to one stable PersonaBot ID and ordered by Source Event creation time and ID; its cursor may not be reused for another Bot. Each item carries a stable Source Event reference and, when still available, the Channel and placed message ID for navigation.

The projection derives Pending, Processing, Handled, Ignored, and Needs repair from canonical Admission attempts and Attention facts. Processing begins only when content enters an active Orchestrator turn; an observed timestamp remains an audit/detail fact, not an extra primary UI state. A pending digest Group Admission stays below its wake threshold, a mentions ordinary Admission waits for a same-Channel direct mention, and a silent ordinary Admission requires explicit Bot reading. When channel_read returns Group messages to the active Orchestrator turn, the exact returned Admissions join that turn’s consumption set: they are observed when the result reaches the Bot, handled when the turn succeeds, and left with an explicit repair outcome when it fails. Unreturned messages remain pending, including older messages omitted by pagination or a context cap. This is a read projection, not a new Attention Decision authority. Assignment reports also create a canonical Admission in the Source Event transaction. Each report carries its typed state and Assignment Session reference; an Orchestrator turn observes it when the report block enters context and handles it when the turn completes, regardless of whether it sends a Channel reply. Boot resumes unobserved due reports once; an interrupted observed report is shown as needs-repair instead of being silently dropped or woken twice. The query keeps facts visible when a Channel or Assignment source is unavailable but disables navigation to that source.

Why

A separate Inbox item table or copied body would compete with the canonical Source Event and could diverge after restart. The projection makes the first DM sidebar entry usable while the broader Attention Decision model in #47 grows. It preserves the relationship between one Source Event and multiple independently admitted Bots.

Consequences

The Orchestrator can explicitly call inbox_ignore for a Channel message it has received or read. That decision is recorded on the same Bot-scoped Admission with the deciding Session and time; pending unread messages and needs-repair admissions cannot be hidden this way. Normal successful turn completion, including silence after considering a message returned by channel_read, remains handled rather than ignored; no routine per-message completion tool is required. An ignored decision changes only this Bot’s Attention projection and Channel delivery status; the Source Event and message history remain available. Neither observation nor handling automatically writes long-term Memory. All typed recovery and waiting-human causes still need their own durable #47 facts before #152 and #126 can display them. Reading this UI is a Human observation and does not change the Bot’s Attention state. The Group sidebar does not show this PersonaBot entry.