Files
git.stella-ops.org/docs/modules/ui/implementation_plan.md
master 7b5bdcf4d3 feat(docs): Add comprehensive documentation for Vexer, Vulnerability Explorer, and Zastava modules
- Introduced AGENTS.md, README.md, TASKS.md, and implementation_plan.md for Vexer, detailing mission, responsibilities, key components, and operational notes.
- Established similar documentation structure for Vulnerability Explorer and Zastava modules, including their respective workflows, integrations, and observability notes.
- Created risk scoring profiles documentation outlining the core workflow, factor model, governance, and deliverables.
- Ensured all modules adhere to the Aggregation-Only Contract and maintain determinism and provenance in outputs.
2025-10-30 00:09:39 +02:00

1.5 KiB
Raw Blame History

Implementation plan — Console UI

Current objectives

  • Maintain deterministic behaviour and offline parity across releases.
  • Keep documentation, telemetry, and runbooks aligned with the latest sprint outcomes.

Workstreams

  • Backlog grooming: reconcile open stories in ../../TASKS.md with this module's roadmap.
  • Implementation: collaborate with service owners to land feature work defined in SPRINTS/EPIC docs.
  • Validation: extend tests/fixtures to preserve determinism and provenance requirements.

Epic milestones

  • Epic 2 Policy Engine & Editor: deliver policy editor simulation and explain UX.
  • Epic 4 Policy Studio: build registry, approvals, and promotion experiences.
  • Epic 5 SBOM Graph Explorer: implement graph navigation, overlays, and diff views.
  • Epic 6 Vulnerability Explorer: surface triage dashboards, findings ledger, and audit exports.
  • Epic 8 Advisory AI: integrate advisory summaries and remediation hints with strict provenance.
  • Epic 9 Orchestrator Dashboard: expose job/source monitoring controls.
  • Epic 11 Notifications Studio: provide notifications workspace with previews and audit trails.
  • Track supporting tasks (e.g., DOCS-CONSOLE-23-001, CONSOLE-OBS-52-001) in ../../TASKS.md.

Coordination

  • Review ./AGENTS.md before picking up new work.
  • Sync with cross-cutting teams noted in ../../implplan/SPRINTS.md.
  • Update this plan whenever scope, dependencies, or guardrails change.