Platform Component Map

Audience: anyone orienting in the Stella Ops codebase. This is a one-line-per-module map of every top-level component under src/ — what it does and how it connects to the rest of the platform.

Use this as a quick orientation map before diving into the per-module dossiers listed in architecture/README.md. When a description here disagrees with a module dossier or the code under src/, the dossier and code win.

Advisory & Evidence Services

Scanning, SBOM & Risk

Policy & Governance

Identity, Signing & Provenance

Scheduling, Orchestration & Automation

Notification & UI

Runtime & Registry

Offline, Telemetry & Infrastructure

CLI, SDK, Web Gateway

Remaining Shared Libraries

How It All Connects

High-level flows (see docs/ARCHITECTURE_OVERVIEW.md for the 10-minute tour):

  1. Ingest — Concelier and Excititor use AOC to ingest advisories/VEX; Scheduler observes deltas.
  2. Scan & Evaluate — Scanner generates SBOM evidence and hands to Signer/Attestor; Policy Engine merges SBOM, advisory, VEX, runtime signals; RiskEngine prioritises.
  3. Store & Export — EvidenceLocker and Export Center package results; Registry serves artefacts; AirGap bundles offline editions.
  4. Observe & Notify — Telemetry captures metrics/traces/logs; Notifier (via the shared StellaOps.Notify.* libraries) delivers alerts; UI/CLI/Web expose operations; TimelineIndexer builds audit trails.
  5. Govern & Secure — Authority, IssuerDirectory, Signer, and Attestor maintain trust; Policy governance and console experiences let teams manage waivers and approvals.

Refer back to module-specific documentation for APIs, configuration, schema details, and operational runbooks. Keep this component map updated alongside module architecture changes whenever modules are introduced, consolidated, or deprecated.