Pages you can ignore

ARDS has more pages than a v1 tester needs. This is the explicit list of pages you can skip — they exist for operators or for features that aren't ready for tester guidance yet.

Safe-to-ignore: governance & compliance

  • Compliance — Internal audit trails, evidence collection, SBOM lookups. Operator surface. Compliance will meet you inside workflows, though — see Governance for workflows.
  • Compliance Documents / Incidents / Profile / Gaps / SBOM — Sub-pages of the above.
  • Governance — Constitution / policy editing. Read-only for testers; nothing here you can usefully change. Governance will meet you inside workflows, though — as injected control nodes on the canvas and checks at publish. That's documented in Governance for workflows; this list is only about these dashboard pages.

Safe-to-ignore: orchestration internals

  • Agents — Lifecycle of internal agents (not coders). Operator diagnostics.
  • Coder Fleet — Live coder operations: a Coder Monitor tab (container diagnostics) and a Queue Dashboard tab (raw queue state). The old standalone Queue and Coder Monitor pages are now these two tabs — their old links redirect here. Useful only when an operator is debugging stuck tasks; don't change anything.
  • Oracle Detail / Traces — Orchestrator decision-trace internals.
  • Prism Reports — Internal security/compliance report aggregation.
  • Quotas — The admin quota control room: one card per provider account, with the state of each usage window. It sits in the sidebar's lower, always-visible section; fine to read out of curiosity, nothing for a tester to change.
  • Observatory — System-wide observability boards. Same lower, always-visible sidebar section as Quotas; fine to read, nothing for a tester to change.
  • Supervision — Live supervision boards, in that same lower sidebar section. Read-only curiosity for a tester.

Safe-to-ignore: experimental / WIP

  • Preview Dashboard — Experimental surface. Behaviour subject to change without notice.
  • Migrations Overview — Internal schema-migration runbook view.
  • Matter Detail Page — Internal placeholder for a feature that hasn't shipped yet.

Safe-to-ignore: charters & initiatives

  • Charters / Initiatives — Internal planning documents. Public-facing roadmap will live elsewhere when ready (the architecture chapter describes what they are: Charters & Matters).

Safe-to-ignore: email channel

  • Email Channel — Operator-side email plumbing (inbound queues, theme management). Testers don't configure these.
  • Email Threads — Operator-facing view of inbound mail.

Available in some deployments only

  • Integrations — The tenant-admin screen for connecting your own GitLab, so Genesis can open merge requests in your group. The sidebar entry (next to Settings) appears only when your deployment provides the integration — if you don't see it, it isn't enabled for your deployment.

Feature availability

Not every capability is on everywhere. A feature can be off for the whole deployment, or off just for your tenant. Settings → Features shows your tenant's toggles — what's available, what's on, and who last changed it. Rows marked Locked by the deployment are controlled at the platform level: you can see them, but they can't be changed from the tenant side. If a page or button this book mentions is missing for you, check that screen before filing a support case. The complete list of features, with what each one gates and its defaults, is the Feature flags reference.

What's not in this list

If you don't see a page name above, it's probably useful for a tester. The main tester-facing pages:

  • Conversations, Missions, Decisions, Tasks, Reviews, Modifications.
  • Workflows (list, editor, run viewer).
  • Fleet Runs (every workflow run across your tenant, in one filterable grid).
  • Projects, GitMirror.
  • LLM Config, LLM Snapshots, Fleet Profiles, Settings.
  • Costs, Intelligence / Search, Reports.
  • Review Engine, Ghost, UX Reviews.
  • Orchestrator (mostly read-only).
  • Suggestions, Research, Support Cases.

Two notes on finding these pages:

  • The sidebar is deliberately slim. Tasks, Reviews, Suggestions, Support cases and Research only appear in it after your tenant produces its first artifact of that type — and then stay. Until then (and for every page with no sidebar entry at all), use the All features index: the "…" entry at the bottom of the sidebar.
  • Observatory, Governance, Costs, Quotas, Compliance and Supervision are always visible in the sidebar's lower, muted section — visible doesn't mean a tester needs them (see the lists above).

Everything in the first list above can be ignored for v1 without missing any tester-facing functionality. If you find yourself reading a page from that list because you're not sure where else to go, that's a doc bug — tell us via Filing a support case and we'll route you to the right surface (and update this doc).