master
7b5bdcf4d3
- 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.
22 lines
1.2 KiB
Markdown
22 lines
1.2 KiB
Markdown
# Implementation plan — Scheduler
|
||
|
||
## 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 incremental policy run orchestration, change streams, and explain trace propagation.
|
||
- **Epic 6 – Vulnerability Explorer:** ensure findings updates and remediation triggers integrate with scheduler outputs.
|
||
- **Epic 9 – Orchestrator Dashboard:** provide job telemetry and control surfaces consumed by the orchestrator UI/CLI.
|
||
- Track additional work (SCHED-MODELS-20-001, observability follow-ups) in ../../TASKS.md and src/Scheduler/**/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.
|