29 lines
1.6 KiB
Markdown
29 lines
1.6 KiB
Markdown
# 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/modules/airgap/guides/airgap-mode.md` and `docs/modules/airgap/guides/staleness-and-time.md` for adoption patterns.
|
|
|
|
## Required Reading
|
|
- `docs/modules/airgap/guides/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.
|
|
- 2. Review this charter and the Required Reading documents before coding; confirm prerequisites are met.
|
|
- 3. Keep changes deterministic (stable ordering, timestamps, hashes) and align with offline/air-gap expectations.
|
|
- 4. Coordinate doc updates, tests, and cross-guild communication whenever contracts or workflows change.
|
|
- 5. Revert to `TODO` if you pause the task without shipping changes; leave notes in commit/PR descriptions for context.
|
|
|