Follow-up to archie-core-abg.5 (channel interface + read-only Telegram). Define the semantics for chat-triggered dispatch (there is no Gitea issue behind a chat-initiated task -- needs its own store/task creation path) and wire /spawn, /approve, /cancel slash commands through the same daemon review/gatekeeping that issue-driven dispatch uses. Blocked on abg.5 (interface must exist first) and should be sequenced after multi-identity daemon core (abg.4) settles how identity maps to chat sessions.
Acceptance Criteria
A chat slash command can create and dispatch a real task (not just query existing state), going through daemon-side permission checks in code, not agent prompt instructions. /approve and /cancel act on in-flight tasks.
Imported from beads archie-core-1786637492273-96-b5271a80 · GitHub #117 · type task · priority P2 · created 2026-08-08 · closed 2026-08-08
Follow-up to archie-core-abg.5 (channel interface + read-only Telegram). Define the semantics for chat-triggered dispatch (there is no Gitea issue behind a chat-initiated task -- needs its own store/task creation path) and wire /spawn, /approve, /cancel slash commands through the same daemon review/gatekeeping that issue-driven dispatch uses. Blocked on abg.5 (interface must exist first) and should be sequenced after multi-identity daemon core (abg.4) settles how identity maps to chat sessions.
### Acceptance Criteria
A chat slash command can create and dispatch a real task (not just query existing state), going through daemon-side permission checks in code, not agent prompt instructions. /approve and /cancel act on in-flight tasks.
---
_Imported from beads `archie-core-1786637492273-96-b5271a80` · GitHub #117 · type task · priority P2 · created 2026-08-08 · closed 2026-08-08_
sam
added the mediumtask labels 2026-10-27 13:37:04 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Follow-up to archie-core-abg.5 (channel interface + read-only Telegram). Define the semantics for chat-triggered dispatch (there is no Gitea issue behind a chat-initiated task -- needs its own store/task creation path) and wire /spawn, /approve, /cancel slash commands through the same daemon review/gatekeeping that issue-driven dispatch uses. Blocked on abg.5 (interface must exist first) and should be sequenced after multi-identity daemon core (abg.4) settles how identity maps to chat sessions.
Acceptance Criteria
A chat slash command can create and dispatch a real task (not just query existing state), going through daemon-side permission checks in code, not agent prompt instructions. /approve and /cancel act on in-flight tasks.
Imported from beads
archie-core-1786637492273-96-b5271a80· GitHub #117 · type task · priority P2 · created 2026-08-08 · closed 2026-08-08