Playbook binding: matcher + mapping + workflow, editable at runtime #465

Closed
opened 2026-10-27 13:36:26 +00:00 by sam · 0 comments
Owner

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:

  • Bindings are persisted state, not config. They live in the store, not config.toml, because operators create them from the UI while the daemon runs.
  • They need versioning. A binding that starts a task should record WHICH version ran, or a later edit makes historical task provenance a lie.
  • Matcher ambiguity needs a defined resolution: two bindings matching one event either both run, or the more specific wins, or it is an error. Pick one and say so.
  • A binding referencing a workflow that no longer exists must fail visibly at bind time, not at 3am when the event arrives.

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

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: - Bindings are persisted state, not config. They live in the store, not config.toml, because operators create them from the UI while the daemon runs. - They need versioning. A binding that starts a task should record WHICH version ran, or a later edit makes historical task provenance a lie. - Matcher ambiguity needs a defined resolution: two bindings matching one event either both run, or the more specific wins, or it is an error. Pick one and say so. - A binding referencing a workflow that no longer exists must fail visibly at bind time, not at 3am when the event arrives. ### 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_
sam added the highfeature labels 2026-10-27 13:36:26 +00:00
sam self-assigned this 2026-10-27 13:36:26 +00:00
sam closed this issue 2026-10-27 13:36:26 +00:00
sam added a new dependency 2026-10-27 13:42:05 +00:00
sam added a new dependency 2026-10-27 13:42:06 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Reference: sam/archie#465