Om Cortex — Screen Catalog

Ordered by read-batch — Nishad's dev-optimized action-flow read order — core daily-use screens first, the Day-1 install arc last (you already know how Cortex gets turned on; you don't open those screens daily). Day 100 steady state — every day after, you open Cortex and land on Cortex Home — the Platform Control Center: a first-class Cortex dialogue plus a tile per platform subsystem (companies, agents, capabilities, KB graph, products, integrations, automation, governance, config). Day 1 — the install arc (B6, read last) — you turn Cortex on, it installs itself narrating every step, walks you through a handful of setup decisions, then hands you a running install. Same console, two different front doors depending on where you are in the life of the install (see CORTEX-CONSOLE-ENTRY-FLOW.md and OWNER-PORTAL-DISPOSITION-AUDIT-2026-07-24.md).

✓ CORTEX-SCAFFOLDING §6 (TECH-670, ratified): operational dashboards → om-forge; the "Om AI Solutions" company dashboard parks for om-business; om-cortex keeps platform screens + a thin D-3 umbrella — Round 2 (2026-07-23): that umbrella folded into the All-Company view (screen-1a) as a candidate steady-state Home — Round 3 (2026-07-24, OWNER-PORTAL-DISPOSITION-AUDIT §3/§4): the steady-state Home is now cortex-home.html, the Platform Control Center (embedded Cortex dialogue + 8 subsystem tiles + config); screen-1a stays live as the Companies/Installs drill-in, reached from the Control Center's Companies tile. See the Control Center IA.

Catalog = the canonical visual home; each screen's behavior home is its PRD/spec (the screen's Action-Flow footer links there). → = drill/next · + = sibling action.

B1 · Daily loop

Cortex · platform-tier — Home → Companies → Company → Task Board → Task Detail → Skill Edit (Round 3 steady state, v-PROPOSED)

Cortex Home — Control CenterThe steady-state landing: embedded Cortex dialogue + 8 platform-subsystem tiles + config.Home…this is your daily start: ask Cortex, then walk the platform.Round 3 resolution — v-PROPOSED → Companies / InstallsInstall health · fleet at a glance · every company's Due Today/Overdue/Needs-you/Blocked rollup.Screen 1a…you opened the Companies tile from Cortex Home to see every install's rollup. → Company DashboardKPI strip · dep tree · Needs-you Approve · Due/Overdue details · Voice + Website Analytics.Screen 1bbusiness KPIs — om-business tier (the seam)…you opened a company to see its business KPIs. → Task Board13-col board, presets/filters, bulk actions, approver-scoped gate affordance.Screen 2…you're looking at that company's live task board. → Task Detail + GateMeta + Description + Attachments + Artifacts; full Notes; resolveApprover gate.Screen 3…you opened one task for its full detail and approval gate. → Skill EditRead-only Input→Process→Who→Output, or SuperUser edit with customization warning + review badge.Skill Edit…the task runs a workflow step — this opens it, read-only or SuperUser-edit.

B2 · Fleet

Cortex · platform-tier — Agent Manager (merged manage + monitor) + provisioning + messaging + live ops + install/config

Agent ManagerOne roster: manage + live monitor; per-row Message; permissions → read-only.Agents…the three things you do on the platform. + Add AgentProvision flow: Role → Model → Capabilities → Name → Review at lowest cost.Add Agent…the three things you do on the platform. + Messages (A2A)WhatsApp-style agent-to-agent messaging; Cortex pinned.Messages…the three things you do on the platform. → Agent Monitor — Live OpsSessions · heartbeats · context-remaining · stalls/alerts (productized sentinel duty).Live Monitor…you opened the live fleet-ops view from Cortex Home.STUB — v-PROPOSED → Install Config + Approver AdminBootstrap read-only · human users · approver-policy grid.Screen 4…you came back to change a setting or a person.

B3 · Capabilities

Cortex · platform-tier (TECH-621) — Ledger → the Lab → Gaps → Onboarding → Envelope

Capability LedgerCapability → expandable multi-holder list (tier + confidence + envelope + cost).Ledger…the three things you do on the platform. → The LabPer-model report cards; per-script Run affordances.The Lab…the three things you do on the platform. → Gap ListNeeded-but-unproven capabilities — the demand-pulled roadmap.Gaps…the three things you do on the platform. → Model OnboardingRegister → Run scripts → rated → recorded.Onboarding…the three things you do on the platform. → Deployment EnvelopeWhich capabilities run in which envelope (cloud/on-prem/air-gapped).Envelope…the three things you do on the platform.

B4 · Subsystem stubs

Cortex · platform-tier — the Control Center's remaining net-new doors (Round 3, v-PROPOSED); each is a STUB, fuller design to follow

KB GraphGraph explorer · sources (FEATURE-1762 model) · ingest health/cost.KB Graph…you opened the knowledge-graph engine from Cortex Home.STUB — v-PROPOSED IntegrationsConnector framework: connected list · add integration · per-connector status.Integrations…you opened the connector framework from Cortex Home.STUB — v-PROPOSED ProductsForge / AI Quorum / Om WMS / Om Business as managed products; create/package doors.Products…you opened the managed-products registry from Cortex Home.STUB — v-PROPOSED Automation / OTAAvailable updates · canary rollout status · rollback.OTA…you opened the update engine from Cortex Home.STUB — v-PROPOSED GovernanceEnforced gates · recent decisions · producer≠reviewer / tester≠own-code made visible.Governance…you opened governance visibility from Cortex Home.STUB — v-PROPOSED

B5 · Build-a-product

Cortex · platform-tier — the recursion (relocated from om-forge J4; TECH-663 naming). Journey: CORTEX-BUILDS-A-PRODUCT.md

Create a ProductCortex defines Om WMS on the Company▸Product spine + attaches the Full Software Lifecycle & Screen Flow workflows — the Guided Setup split-pane.Create Product…the three things you do on the platform. → Package · Om WMSOm WMS packaged as a vertical configuration: base/overlay (customer-edits-win) + signed OTA + the recursion's second turn.Vertical config…the three things you do on the platform.

B6 · Install arc (read last)

Cortex · platform-tier — Day 1, in order (NEW, v-PROPOSED); you already know how this works, so it reads last

Turn on CortexDeployment-aware cold-open: license + payment confirmed, one primary action.First Open…you've licensed Cortex but it isn't running yet. → Live InstallAQ-query-style streaming step list — every step names WHAT and WHY, honest latency.Live Install…Cortex is installing itself and showing you what it's doing. → Guided SetupOne decision at a time — identity, first company, approver default, model default.Guided Setup…Cortex needs a few decisions from you to run your business. → Cortex is running"Cortex is now running your install." — plain recap + hand-off to Home.Install Complete…install + setup are done and Cortex has started working.

Cortex Home is the front door once install is done (see B1 above) — this arc is what got you there, kept last because you only walk it once per install.