Playbook binding: matcher + mapping + workflow, editable at runtime #465
Notifications
Due Date
No due date set.
Blocks
Depends on
Reference: sam/archie#465
Reference in new issue
Block a user
The object that ties it together. A binding is: a matcher (which inbound events does this apply to), a mapping (which fields the workflow receives), and a target agentic workflow.
Runtime-editable is the whole point -- creating or changing a binding must not require a redeploy or a daemon restart. That has real consequences the design must face:
Acceptance criteria
A binding can be created, edited and disabled from the UI while the daemon runs; a task records the binding version that started it; overlapping matchers resolve by a defined and documented rule; a binding naming a missing workflow is rejected when saved.
Notes
2026-08-22: the draft -> pending_approval -> armed state machine from t2db.5's decision belongs to the binding entity this bead defines, not to a shared package -- 7d5u.3 was narrowed to exclude it since there is exactly one consumer today. Implement the state transitions here.
Close reason
Closed
Imported from beads
archie-core-t2db.4· GitHub #537 · type feature · priority P1 · created 2026-08-21 · closed 2026-09-02