stella-ops.org/git.stella-ops.org
1
0
Fork 0
Code Issues Pull Requests Actions 16 Releases Wiki Activity
Files
90c244948a7427037e3bdb541fc6b0a27520d37f
git.stella-ops.org/src/AirGap/StellaOps.AirGap.Policy/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.5 KiB
Raw Blame History

StellaOps AirGap Policy Guild Charter

Mission

Provide the shared enforcement layer (EgressPolicy, job plan validators, sealed-mode gates) that keeps all services compliant with Air-Gapped Mode requirements.

Scope

  • EgressPolicy facade replacing raw HTTP client usage.
  • Static analysis/linting to detect unauthorized network calls.
  • Task Runner and orchestrator validators flagging disallowed destinations.
  • Shared error contract (AIRGAP_EGRESS_BLOCKED) and remediation messages.
  • Test harnesses simulating sealed/unsealed execution paths.

Definition of Done

  • Every service imports the facade; CI fails on direct HTTP client usage.
  • Sealed-mode unit tests cover panic/remediation behavior across host types.
  • Documentation updated in docs/airgap/airgap-mode.md and docs/airgap/staleness-and-time.md for adoption patterns.

Required Reading

  • docs/airgap/airgap-mode.md
  • 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.