stella-ops.org/git.stella-ops.org
1
0
Fork 0
Code Issues Pull Requests Actions 1 Releases Wiki Activity
Files
7b5bdcf4d3bee4e6f398d0226ba8cd3c2754e07a
git.stella-ops.org/docs/modules/orchestrator/AGENTS.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

951 B
Raw Blame History

Source & Job Orchestrator agent guide

Mission

The Orchestrator schedules, observes, and recovers ingestion and analysis jobs across the StellaOps platform.

Key docs

How to get started

  1. Read the design summaries in ./architecture.md (quota governance, job lifecycle, dashboard feeds).
  2. Open ../../implplan/SPRINTS.md and locate stories for this component.
  3. Check ./TASKS.md and update status before/after work.
  4. Review ./README.md for responsibilities and ensure changes maintain determinism and offline parity.

Guardrails

  • Uphold Aggregation-Only Contract boundaries when consuming ingestion data.
  • Preserve determinism and provenance in all derived outputs.
  • Document offline/air-gap pathways for any new feature.
  • Update telemetry/observability assets alongside feature work.