approval

Overview ¶

Command approval demonstrates human-in-the-loop control: a signal node parks the execution until an external approval arrives (with a timeout fallback), Cancel abandons an execution an operator no longer wants, and WithHistory records a durable step-by-step trace queryable with Server.History.

Run a NATS server (2.12+, JetStream enabled) and:

go run ./examples/approval --nats nats://127.0.0.1:4222

It runs two orders: one is approved via Signal and fulfilled; the other is cancelled while waiting. Each execution's history trace is printed at the end.