Canonical state and freshness
Torq integrations consume shared state through:
Chain -> Indexer -> Projector -> Postgres -> APIDo not reconstruct shared protocol state from RPC. The API returns freshness evidence including status, lag, block, projection time, snapshot time, and a reason when state is stale or missing.
Workflow lifecycle
Every prepared workflow includes a snapshot hash, expiry, simulation requirement, blocked reasons, and expected postconditions. Re-prepare after expiry or stale-state rejection.