NFLTR›Docs›Guides

Orchestration Trace Lab

Trace Lab answers the first operator questions about a completed or stalled run: what ran, where time was spent, which dependency chain controlled completion, what evidence points to the earliest failure, and how trustworthy the available event history is.

Analysis runs locally in the browser through a Rust-compiled WebAssembly module. Trace bytes are not uploaded for analysis, and the UI never claims a Wasm success when the module is unavailable.

Where to find it

  1. Open nfltr.xyz/dashboard and expand an orchestration card.
  2. Scroll to the Trace Lab panel under the graph and coordination panels.
  3. Choose Analyze trace. The dashboard projects the live DAG into the Trace Lab ABI and loads Wasm lazily.
  4. Read the concise summary first; open Technical evidence for counts, quiet interval, warnings, and root-cause candidates.
Keyboard and accessibility

The Analyze control is a normal button. Results update an aria-live region. Technical evidence sits behind a native <details> disclosure. Reduced-motion preferences disable decorative transitions on the panel.

What the analysis returns

Hostile or malformed projections fail closed with a typed error code and message. Incomplete but analyzable evidence surfaces warnings and a lowered confidence instead of inventing facts.

Reproduce the workflow with nfltr orch

This feature was planned and dogfooded as an orchestration goal against hosted relay nfltr.xyz / grpc.nfltr.xyz. Another operator can reproduce the shape without hardcoding a concrete model or reasoning-effort default:

# 1) Connect Cursor (or another) workers you own to the hosted relay
nfltr orch fleet setup --mode local --backend cursor \
  --proxy-url https://nfltr.xyz --server grpc.nfltr.xyz:443 --no-derive-proxy

# 2) Plan from a goal file that asks for the Trace Lab ABI + dashboard panel
#    Provide coordinator/planner credentials via your environment; omit model/effort
#    unless you intentionally override.
NFLTR_COORDINATOR_MODEL_PROVIDER=cursor \
nfltr orch start goal ./goal.md --watch \
  --proxy-url https://nfltr.xyz --server grpc.nfltr.xyz:443 --no-derive-proxy

# 3) On the dashboard, expand the resulting orchestration card and run Trace Lab

Required contracts for implementer phases: typed output_validation on structured results, independent review after mutation, focused gates such as make test-orchestration-trace-lab-wasm and the Trace Lab Vitest files, and no commit/push/deploy from workers.

Related