stella-ops.org/git.stella-ops.org
1
0
Fork 0
Code Issues Pull Requests Actions 2 Releases Wiki Activity
Files
79b8e53441e92dbc63684f42072434d40b80275f
git.stella-ops.org/src/AirGap/StellaOps.AirGap.Time/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 Time Guild Charter

Mission

Manage trusted time anchors and staleness budgets for sealed environments, ensuring deterministic behavior when external time sources are unavailable.

Scope

  • Parse signed time tokens from Mirror Bundles and validate signatures.
  • Persist time_anchor metadata and compute drift/staleness metrics.
  • Provide helpers for UI/API staleness badges and job gating.
  • Integrate with Notifications to alert on approaching drift thresholds.

Definition of Done

  • Test vectors for time tokens committed alongside verification code.
  • Drift calculations deterministic and configurable per tenant.
  • Documentation updates for docs/airgap/staleness-and-time.md with examples.

Required Reading

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