eda: wire InvokeOnce into the first side-effecting action position #456
Notifications
Due Date
No due date set.
Depends on
Reference: sam/archie#456
Reference in new issue
Block a user
t2db.24 ships the record-then-invoke helper (internal/domain/eda/playbook/coordinator.go InvokeOnce) and the cross-process ledger, but nothing calls InvokeOnce: no daemon/app seam lifts a storecontract.PlaybookDispatcher onto the daemon (internal/app/archied/bootstrap.go lifts BindingDispatcher/BindingTaskCreator but no Playbook*), and the first side-effecting position (module/channel/forge) still does not ship. Wire InvokeOnce at the first side-effecting action invocation, lifting PlaybookDispatcher onto the daemon the same way BindingDispatcher is lifted. Raised by the 5-angle + re-review of t2db.24.
Close reason
Shipped. InvokeOnce is wired into the module action position: internal/domain/eda/playbook/run.go runPlaybook evaluates each action through InvokeOnce with a Decision carrying PlaybookID/Version/ActionID/ActionPosition, then Invoke + DecodeResult into actions..result. Verified: TestRunInvokesEachActionOncePerEvent plus the InvokeOnce suite.
Imported from beads
archie-core-t2db.31· GitHub #1115 · type task · priority P2 · created 2026-09-21 · closed 2026-09-29