Console map
Every page on the console rail, in rail order, with its link name and what it reads. The structure
is defined in one place, flutter/lib/core/widgets/nav.dart, and pinned by
flutter/test/nav_ia_test.dart. The labels come from flutter/lib/l10n/app_en.arb.
Link to any page with ?tab=<name>, for example https://<your console>/?tab=runners. Names are
case-insensitive. An unknown name opens Overview.
Overview
| Page | ?tab= | Reads |
|---|---|---|
| Overview | overview | /api/dashboard, /api/agent-runs, /api/harness, /api/connections, /api/inference, POST /chat |
DevEx
| Page | ?tab= | Reads |
|---|---|---|
| Cluster › Namespaces | namespaces | /api/namespaces; the Nodes & placement sub-tab reads /api/cluster-nodes and /api/nodes/{name} |
| Cluster › Instances | instances | the instance rows of /api/dashboard |
| Cluster › Routing | routing | /api/routes (the edge routes and /forge/, traced to Service, endpoints and workload) |
| Platform audit | platformAudit | an assessment over existing endpoints (see below) |
| GitOps | gitops | /api/gitops |
| Audit chain | audit | /api/audit, /api/audit/{seq}, /api/audit/verify |
| Session admins | sessionAdmins | /api/session-admins |
| Doctor | doctor | /api/doctor (the ops doctor CronJob) |
| Metrics | metrics | /api/metrics |
| Agent runs › Runs | runs | /api/runs, one run’s log at /api/agent-runs/logs; the Schedules & arming tab reads /api/agent-schedules |
| Agent runs › Reviews | reviews | /api/reviews, /api/reviews/{type}/{runId}[/detail] |
DataEx
| Page | ?tab= | Reads |
|---|---|---|
| Model cards | modelCards | /api/models, /api/agents |
| Agents | agents | /api/agents, /api/swarm; the per-agent policy view adds /api/agent-config, /api/guardrails, /api/access |
| Inference | inference | /api/models, /api/agents (the inference tiers) |
| Connections | connections | the shared datasources ConnectionsService (gRPC-web) |
| Runners | runners | the shared datasources RunnersService (gRPC-web); /api/runners stays as a deprecated alias |
| Trust › Harness | harness | /api/harness, actions on POST /api/harness/{id}/act |
| Trust › Guardrails & autonomy | guardrails | /api/guardrails |
| Trust › Policy & ReBAC | policy | /api/access |
| Trust › Admin | admin | the shared access service; shown only to an admin of the chosen instance |
| Trust › Secrets & PKI | secrets | /api/security |
| Model & agent audit | modelAgentAudit | an assessment over existing endpoints (see below) |
| Judgements | judgements | /api/judgement, /api/judgements |
Intelligence
The Atlas pages are a page-for-page Flutter port of the partner product Atlas
(flutter/lib/features/intelligence/ATLAS_SOURCE.md). They read the console’s in-process gRPC-web
services. See the Intelligence API reference for every RPC.
| Page | ?tab= | Reads |
|---|---|---|
| Capital Governance Analyst | analystDashboard | CapexService.GetAnalystDashboard, plus /api/data-governance-findings, /api/governance-runs, /api/measures |
| CFO Cockpit | cfoDashboard | CapexService.GetCfoDashboard, plus /api/finops, /api/compliance |
| Director PMO | pmoDashboard | /api/dashboard, /api/data-governance-findings, /api/measures |
| DQ overview | dqOverview | CapexService.ListScanRuns, /api/governance-runs, /api/rules-recon |
| Capex Monitor | capexMonitor | CapexService.GetSummary, GetFeeds, ListFindings; uploads and clears go through the same service |
| Capex Lineage | capexLineage | CapexService.TraceFinding, GetRuleBook |
| Perspectives | perspectives | nothing: a framework page of fixed copy, with no data |
| Business Rules | rules | /api/rules-recon; its governance section calls GovernanceService (ListRuleChanges, ProposeRuleChange, DecideRuleChange, SetRuleOwner) |
| Orchestrator | orchestrator | PlaybookService |
| Lineage | lineage | /api/data-lineage, /api/data-governance-findings |
| Remediation | remediation | /api/rules-recon; its governance section calls GovernanceService (ListRemediations, DryRunRemediation, DecideRemediation, ListDecisions) |
| Progress | progress | CapexService.ListScanRuns, /api/governance-runs |
| Sources | sources | /api/connections, /api/connection-types, /api/domains, the connector probe (/api/connectors/status, refresh on demand), and the workspace grants (WorkspaceService) |
| Resolve | resolve | the shared estate service (runink.ui.estate.v1.EstateService) |
| Settings | settings | WorkspaceService, /api/github, /api/rules-recon |
| Data audit | dataAudit | an assessment over existing endpoints; the audit-time runner is picked here |
| Deploy lineage | deployLineage | /api/lineage (did a commit ship; not data lineage) |
FORGE
| Page | ?tab= | Reads |
|---|---|---|
| Studio | forgeStudio | the FORGE service, reverse-proxied at /forge/; the rail lists FORGE’s chats from runink.ui.chat.v1.ChatService/ListChats |
A Studio link can carry FORGE’s view parameters: /?tab=forgeStudio&chat=<id>, chat=new, and
panel=components|draft|details. See FORGE.
Footer
Account is the shared profile page: your sign-in method and session expiry, the instances you hold a live grant on, and CORE’s GitHub configuration, cloud providers and legal sections. Billing is its own page, pushed from Account.
The three audit pages
Platform audit (DevEx), Model & agent audit (DataEx) and Data audit (Intelligence) are
assessments, not the audit log. The audit log is DevEx › Audit chain. Each audit page opens on
one verdict over checks read from existing endpoints. A check it could not read goes into a
“not measured” list with its reason, never into the passes. Agent reviews start only through an
existing playbook’s PlaybookService.RunNow, never through a new dispatch path.
Link names that still work
These names were retired. A link that uses one opens the page that now owns its subject
(retiredTabNames in nav.dart):
Retired ?tab= | Opens |
|---|---|
services | Cluster › Namespaces |
placement, clusters, controlPlanes | Cluster › Namespaces, on Nodes & placement |
agentActivity | Agent runs › Runs |
codingSessions | Agent runs › Runs, on its coding-session queue |
codeReview | Agent runs › Reviews |
measures | Trust › Harness |
security, topology | Trust › Secrets & PKI |
swarm | DataEx › Agents |
dataDomains | Intelligence › Sources |
rulesRecon, governance | Intelligence › Business Rules |
compliance | Intelligence › Remediation |
maturity, governanceRuns | Intelligence › Progress |
forgeApps, forgePipelines | FORGE › Studio |
agentSchedules is a live link-only name: it opens Agent runs › Runs on its Schedules & arming
tab. mcpTools and modelRunners have no redirect, because their subjects were deleted rather than
moved.