Dry-run or dispatch a binding against a stored capture #144

Open
opened 2026-10-27 13:35:08 +00:00 by sam · 1 comment
Owner

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 check once at the end; if it fails twice on the same problem, comment on this bead and stop.

Stop when

  • Dry-run and dispatch-once endpoints.
  • Buttons in CaptureDetail and BindEvent.
    Then commit (Conventional Commits, scoped by package), bd close this bead and stop.

Imported from beads archie-core-bdb5.12 · GitHub #1306 · type feature · priority P2 · created 2026-10-05

## 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 check` once at the end; if it fails twice on the same problem, comment on this bead and stop. ## Stop when - [ ] Dry-run and dispatch-once endpoints. - [ ] Buttons in CaptureDetail and BindEvent. Then commit (Conventional Commits, scoped by package), `bd close` this bead and stop. --- _Imported from beads `archie-core-bdb5.12` · GitHub #1306 · type feature · priority P2 · created 2026-10-05_
sam added the mediumfeature labels 2026-10-27 13:35:08 +00:00
sam self-assigned this 2026-10-27 13:35:08 +00:00
Author
Owner

sam 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.

_sam 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.
sam added a new dependency 2026-11-14 14:45:10 +00:00
sam added the deferred label 2026-11-15 17:26:26 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Reference: sam/archie#144