Implementation plan — CLI

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.
  • Documentation sync: keep module docs aligned with active sprint docs/implplan/SPRINT_0316_0001_0001_docs_modules_cli.md.

Epic milestones

  • Epic 2 – Policy Engine & Editor: deliver deterministic policy verbs, simulation, and explain outputs.
  • Epic 4 – Policy Studio: add registry/promotion workflows, lint tooling, and approvals UX.
  • Epic 6 – Vulnerability Explorer: integrate ledger/triage operations.
  • Epic 10 – Export Center: automate export verification and Offline Kit flows.
  • Epic 11 – Notifications Studio: manage rule/channel authoring and previews via CLI.
  • Track CLI-specific work (e.g., CLI-CORE-41-001, DOCS-CLI-OBS-52-001) in …/…/TASKS.md and src/Cli/**/TASKS.md.

Coordination

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