Registered nodes
0
Live node inventory and heartbeat posture
Operator control surface
See what is running, where leases might stall, and which events just changed operator posture.
This slice extends the current dashboard with execution tracking. It prefers live backend reads for runs, attempts, and events, then falls back to careful derivation from nodes and queue data when those endpoints are not present yet.
nodes: livework items: livefile scopes: livefile requests: liveruns: liveattempts: derivedevents: derived
Operator snapshot
0 active runs
Live backend
Mixed tracking
Healthy nodes
0
Blocked runs
0
Pending file access
0
Tracking slices live
1/3
Execution tracking
Some execution tracking slices are live and the rest are derived from current foundation data.
Active runs
0
0 visible runs currently executing or derived from the queue.
Lease review
0
Nodes with stale or degraded lease posture stay visible.
API state
Live backend
All current foundation slices are receiving live scaffold data
Nodes
Node health, capacity, and file-scope coverage
Heartbeat freshness stays visible, and every node now shows whether it has declared usable file-access scopes.
No nodes registered yet.
Work items
Operator queue
A minimal live queue view for the current backend, with explicit empty and offline states.
No work items yet.
Runs
Active and recent run posture
Live run records appear when the backend exposes them. Otherwise the panel derives operator-safe visibility from queue state and node heartbeats.
No runs are visible yet.
Attempts
Lease and attempt summary
This view stays compact on purpose: which nodes are carrying active leases, where posture looks stale, and whether the backend is sending real attempt records yet.
No attempts or lease posture are visible yet.
Events
Recent timeline
Operators get a short event trail for quick situational awareness, sourced from live events when available and derived from current activity otherwise.
No recent events are visible yet.
File access
Declared scopes and recent requests
File access remains an operator surface: what nodes say they can touch, which paths are gated, and what requests are waiting.
No file-access capabilities or requests yet.