Dashboard Walkthrough
Use nfltr.xyz/dashboard to check readiness, start a run, follow its DAG, handle live human decisions, and inspect terminal evidence from desktop or mobile. The authenticated Operations surface is the Causal Operations Atlas: Needs you, Runs, Fleet, and Activity, plus a docked task drawer and Trace Lab under an expanded run.
1. Run the read-only preflight
$ nfltr orch doctor
$ nfltr orch fleet ping
$ nfltr orch fleet workers --json
$ nfltr orch fleet status --json
$ nfltr orch hitl --json
$ nfltr orch task list --active --output jsondoctor tells you whether coordinator and relay prerequisites are available. The worker commands distinguish verified workers from ordinary relay, planner, CLI, or unclassified peers. The dashboard Start form blocks safely when no verified worker advertises a worker capability or supported task mode.
2. Learn the Atlas workspace targets
| Target | What belongs there | CLI cross-check |
|---|---|---|
| Needs you (attention rail) | Live questions, approvals, active blockers, and paused work | nfltr orch hitl --json |
| Runs (causal canvas) | Start form, run cards, DAGs, task drawers, Live and History filters, and Trace Lab under an expanded card | nfltr orch task list --active --output json |
| Fleet | Connected peers, verified workers, unclassified peers, capabilities and labels | nfltr orch fleet workers --json |
| Activity | Recent lifecycle evidence across runs | nfltr orch task events --task TASK_ID --tail 50 --since 0 |
3. Start without surprises
Open Runs → Start. Supply an objective, a verified worker, a supported task mode, and worker instructions. The system-prompt field is required because it opens the task-scoped worker session. Optionally require approval and explain why. Opening or cancelling the form dispatches nothing; pressing Start creates work and may consume worker or LLM resources.
For a versioned multi-phase run, validate and start from the CLI:
$ nfltr orch spec validate ./run.json
$ nfltr orch start spec ./run.json --watch4. Read a run and its result
On the causal canvas, each run card contains a coordinator/worker DAG. Click a node to open the docked task drawer for objective, current operator contract, result or error, events, retries, tool calls, memory, cost, and workspace evidence. Expand a card to open Trace Lab when you want wall-time, critical-path, or earliest-failure evidence without leaving the browser. The URL becomes https://nfltr.xyz/dashboard#task=TASK_ID, so a teammate can open the same task directly.
$ nfltr orch task status --task TASK_ID --events 20
$ nfltr orch task result --task TASK_ID5. Work on questions and approvals
Needs you is the action queue. Answer a question inline, or use:
$ nfltr orch task answer --task TASK_ID --message "your answer"Open an approval to get a decision-first drawer. Review the request, objective, and any recorded issue, then Approve or Reject. Terminal tasks never show those controls: failed, cancelled, rejected, aborted, and completed attempts stay in History for inspection.
$ nfltr orch task approve --task TASK_ID --reason "evidence reviewed"
$ nfltr orch task reject --task TASK_ID --reason "evidence is incomplete"6. Treat control outcomes as evidence
Refresh, filters, opening cards, copying commands, and cancelling an unopened Start form are read-only. Starting, steering, pausing, resuming, cancelling, retrying, fulfilling artifacts, changing settings, deleting history or agents, and changing keys or fleet tokens affect external state. Check the control help, confirm the target, and keep the status line or audit event. Deleting run history does not cancel live work.
Next: Observe orchestration for drawer detail, Orchestration Trace Lab for Wasm analysis, and Team collaboration for shared run handoff.