Loading project state…
Reading queues, runtime, connectors, and worker heartbeat.
One operator view: action required, degraded systems, queue state, and recent meaningful work.
Reading queues, runtime, connectors, and worker heartbeat.
Goals, delivery, decisions, and provider evidence from one verified management snapshot.
Business outcomes, projects, dependencies, and blockers. This is separate from the operational graph.
Goal → Epic → Milestone plan with planned, forecast, and actual evidence kept distinct.
Management accounting only. Actual, committed, forecast, and scenario values never collapse into one number.
Humans, remote agents, local agents, machine Nodes, vacancies, and providers in their exact project scope.
Admitted facts and architect hypotheses remain visibly distinct.
System architecture & data flow
Table view of the same scoped map: nodes, relations, status, capabilities, and last updates.
Chronological workflow events from reports, runtime state, and project activity.
Capability ownership, requests, grants, denials, and review candidates.
Canonical decisions requiring explicit human authority. Repeated requests are collapsed without deleting their audit trail.
Structured events, newest first. Current runtime signals and archived diagnostics are separated from primary work views.
Control chats, workers, connected agents, provider relays, and runtime status.
People, workspace boundaries, machine resources, integrations, Vault references, and platform policy. Secrets and payments are never displayed here.
Profile, workspace access boundary, connected services, and local display preferences. Every action states whether it is local-only, review-gated, or read-only. Secrets are never displayed here.
Demo mode uses local fixture data only. It never shows production workspace state and cannot merge, close gates, issue invites, or write candidates.