Dry-run or dispatch a binding against a stored capture #144
Notifications
Due Date
No due date set.
Blocks
Reference: sam/archie#144
Reference in new issue
Block a user
Goal
An operator picks a captured event and either dry-runs a binding (mapped inputs, filter result, target) or dispatches it once through the ledger.
Evidence
Captures are typed only on arrival (internal/domain/storecontract/storecontract.go:304-307); testing a binding means resending the webhook.
Rules
Read CLAUDE.md. Do only what the Goal and Stop when need. File anything else you notice as a bead; do not fix it. Run
task checkonce at the end; if it fails twice on the same problem, comment on this bead and stop.Stop when
Then commit (Conventional Commits, scoped by package),
bd closethis bead and stop.Imported from beads
archie-core-bdb5.12· GitHub #1306 · type feature · priority P2 · created 2026-10-05sam wrote (originally 2026-10-05):
Needs a design call before building: dispatch (mapping, filter, target, authorization, enqueue) lives in archied's daemon, the buttons in archie-ui. Options: (a) a dry-run in webui from domain functions (mapping.Resolve, binding.CompileFilter) plus a narrow 'reevaluate this capture' that just makes the daemon offer it again (e.g. clear the pair's non-dispatched ledger row); (b) a new archied RPC that runs dispatchOneBinding for one pair. (a) adds no process boundary; (b) is the only way to dry-run the target and authorization exactly.