How does Catalyst ensure verifiability when an agent runs multiple steps concurrently with interleaved outcomes?

Catalyst signs each step independently and embeds causal ordering via cryptographic pointers to predecessor steps, not through wall-clock timestamps. This creates a directed acyclic graph of step hashes that preserves the concurrency structure and prevents undetected reordering. It does not certify the relative timing of interleaved events. The verifiable record proves which steps happened before others, but cannot show the exact real-time overlap of concurrent operations. Additionally, the causal graph depends on the agent correctly declaring dependencies; missing a dependency may result in a valid but misleading verification.