State Machine
Tracks workflow state and receipts. Every execution produces a deterministic state transition the consensus layer can verify.
What We Store
The minimal ledger we maintain today.
- Workflow registry: name, current YAML hash, current bytecode hash.
- Receipt log: per execution receipts (step outputs, Smart Action attestations, timestamps).
- Account pointers: references to payer balances / escrows used during execution.
State Transition
For each workflow execution we append a receipt and update any mutable pointers.
The transition is a pure function of the previous state, the workflow bytecode, and the Smart Action receipts produced by the runtime. Consensus nodes can replay the bytecode deterministically, compare receipts, and reach the same new state. No hidden side effects.