[koistya]

That's a really cool approach, love it! Treating agent steps as build artifacts (OCI layers) makes total sense for coding agents or offline evaluations where you need filesystem-level reproducibility.

Verist, on the other hand, is aiming for the application layer: lightweight, low-latency observability for production user-facing apps where spinning up containers per-step isn't feasible. I think there's space for both: Dagger/OCI for heavy 'environment' replay, and Verist for semantic 'decision' replay.