Execute & Traces
Tracing
Capture correlated traces from the SUT for later assurance.
Assurance needs structured evidence: messages, spans, tool calls, latency, and metadata keyed by a correlation ID (typically the case id).
Supported today
- Langfuse emission from the reference SUT and from the SDK tracer
- Local JSON / JSONL fallbacks for offline debugging
- Studio paste of conversation or trace payloads
Correlation
Carry the originating case id on every trace so scores map back to suite, dimension, and intent.
OpenTelemetry
Full OTel instrumentation across the Studio pipeline is part of the broader observability story; tutorials in this wave focus on Langfuse because that path is operational for the reference loop.