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

927 B
Raw Blame History

Vulnerability Explorer agent guide

Mission

Vulnerability Explorer delivers policy-aware triage, investigation, and reporting surfaces for effective findings.

Key docs

How to get started

  1. Review ./architecture.md for ledger schema, workflow states, and export requirements.
  2. Open ../../implplan/SPRINTS.md and locate stories for this component.
  3. Check ./TASKS.md and update status before/after work.
  4. Read README/architecture for design context and update as the implementation evolves.

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.