stella-ops.org/git.stella-ops.org
1
0
Fork 0
Code Issues Pull Requests Actions 2 Releases Wiki Activity
Files
635c70e828d70031b40c0fc9275acd36e19e57e6
git.stella-ops.org/src/Mirror/StellaOps.Mirror.Creator/AGENTS.md
master 90c244948a Update AGENTS.md files across multiple modules to standardize task status update instructions and introduce a new document for Secret Leak Detection operations. 
- Modified task status update instructions in AGENTS.md files to refer to corresponding sprint files as `/docs/implplan/SPRINT_*.md` instead of `docs/implplan/SPRINTS.md`.
- Added a comprehensive document for Secret Leak Detection operations detailing scope, prerequisites, rule bundle lifecycle, enabling the analyzer, policy patterns, observability, troubleshooting, and references.
2025-11-05 11:58:32 +02:00

1.4 KiB
Raw Blame History

StellaOps Mirror Creator Guild Charter

Mission

Deliver connected-environment tooling that assembles signed Mirror Bundles for air-gapped deployments, covering content selection, signing, and distribution.

Scope

  • Bundle assembly pipeline (advisories, VEX, policy packs, images, dashboards).
  • Integration with Export Center for bundle scheduling and verification.
  • CLI commands for bundle creation, inspection, and rotation management.
  • Test fixtures ensuring determinism across bundle builds.

Definition of Done

  • Bundles are deterministic given the same inputs; regression tests verify Merkle root stability.
  • Signing workflows documented and automated with dual-control for root rotation.
  • Bundle metadata published for import verification.

Required Reading

  • docs/modules/platform/architecture-overview.md

Working Agreement

    1. Update task status to DOING/DONE in both correspoding sprint file /docs/implplan/SPRINT_*.md and the local TASKS.md when you start or finish work.
    1. Review this charter and the Required Reading documents before coding; confirm prerequisites are met.
    1. Keep changes deterministic (stable ordering, timestamps, hashes) and align with offline/air-gap expectations.
    1. Coordinate doc updates, tests, and cross-guild communication whenever contracts or workflows change.
    1. Revert to TODO if you pause the task without shipping changes; leave notes in commit/PR descriptions for context.