Overview#
Argus spans investigations, emergency response, utilities, workforce, evidence, defence, and administration. The people evaluating and operating it rarely share a vocabulary. A procurement panel asks whether live SIEM connections, blockchain investigation, or MDOC partner bridges exist. A newly hired dispatcher asks where the tools for their shift live. A training lead needs a path through real software rather than a slide deck of aspirational modules. When the only answers are tribal knowledge and a mega-menu, demos stall and onboarding stretches.
The Platform Capability Catalogue is a browsable index of what a deployment actually offers. Entries group by domain, support search, and deep-link into live applications the operator can access or into the long-form module documentation when a capability is documented for buyers and builders. Access rules still apply. A catalogue row for a restricted tool leads to a shared denied state when grants are missing, rather than a mysterious empty page. Together with Navigation Operator Lens, the catalogue is the long tail: the lens keeps first paint calm; the catalogue and command palette remain how power users and evaluators discover breadth.
For solution architects comparing Argus to point products, the catalogue is also a honesty mechanism. Feature-flagged or unavailable capabilities can surface as non-actionable rather than as marketing ghosts. That posture travels well into security questionnaires and due-diligence rooms where "show me the thing" beats "trust the brochure".
Last Reviewed: 2026-09-15 Last Updated: 2026-09-15
Key Features#
-
Unified browsing by domain: Capabilities group across cyber, aviation, workforce, emergency, evidence, utilities, and related domains so explorers can think in missions rather than repo names.
-
Search that matches how people ask: Title and short description search help someone who knows the outcome ("impacted customers", "verifiable credential", "case queue") find the entry without knowing the internal application package name.
-
Deep links into live tools: Where a tool is mounted in the web applications, the catalogue opens it directly under the same gateway routing as the rest of the shell.
-
Documentation as a first-class target: Where the right next step is a module guide, the catalogue opens that guide so sales engineering and customer training stay inside the same corpus published to DOCS_KV.
-
Authority-honest results: Entries respect the signed-in authority catalogue. Denied, not-found, and failed states reuse shared UI patterns introduced across audited workspaces.
-
Feature-flag awareness: Capabilities governed by domain flags can appear without pretending they are callable when the flag is off, which keeps pilot tenants from clicking into unfinished rails.
-
Companion to operator lenses: Lenses limit first-paint intents; the catalogue carries the remainder. That pairing is the IA answer to both "too much navigation" and "I cannot find the module we bought".
-
Training and demo rehearsal: Instructors and solution engineers can walk a room through catalogue sections as a live curriculum instead of maintaining a parallel PDF inventory that drifts from production.
Use Cases#
-
New-tenant onboarding: An administrator tours the catalogue after go-live to see which domains are licensed and mounted before inviting the first operator wave.
-
Procurement and competitive proof: During a bake-off, evaluators search for contested capabilities and open either the live tool or the module page that states implementation status in plain language.
-
Cross-domain investigation: An analyst looking for live SIEM connections, blockchain workspaces, or partner intelligence tools finds the path without memorising rail labels.
-
Change management: After a release that adds utilities operator workflows or Multi Domain Operations Cloud (MDOC) workbench panels, training leads point staff at the new catalogue entries rather than emailing screenshots.
-
Least-privilege education: Showing a denied state from a catalogue link is a useful teaching moment: discovery is encouraged, authorisation still comes from RBAC.
Integration#
The catalogue lives in the Argus web applications alongside the app shell, command palette, and lens navigation. It reads authority from the authenticated session profile. Feature flags participate where entries are gated. Module documentation entries resolve to the published module guides. Shared denied and empty states keep catalogue outcomes visually consistent with investigation, cyber, and collaboration workspaces.
Open Standards#
- OpenAPI / GraphQL public descriptions: Catalogue entries can point at partner-facing API docs where a capability is exposed externally.
- WCAG 2.2: Search, filters, and links meet the shell accessibility baseline.
- ISO 21498-style capability registers (informational): Organisationally the catalogue plays the role of a maintained capability register for the deployment.