stella-ops.org/git.stella-ops.org
1
0
Fork 0
Code Issues Pull Requests Actions Releases Wiki Activity
Files
main
git.stella-ops.org/ops/devops/AGENTS.md
master 66cb6c4b8a
Some checks failed
Docs CI / lint-and-preview (push) Has been cancelled
Details
feat: Add guild charters and task boards for various components 
- Introduced guild charters for Scanner Deno, PHP, Ruby, Native, WebService, Java, Surface.Env, Surface.FS, Surface.Secrets, Surface.Validation, UI, Zastava Observer, Zastava Webhook, Zastava Core, and Plugin Platform.
- Each charter outlines the mission, scope, required reading, and working agreements for the respective guilds.
- Created task boards for Surface.Env, Surface.FS, Surface.Secrets, Surface.Validation, and Zastava components to track progress and dependencies.
- Ensured all documents emphasize determinism, offline readiness, security, and integration with shared Surface libraries.
2025-11-01 02:21:46 +02:00

1.2 KiB
Raw Permalink Blame History

DevOps & Release — Agent Charter

Mission

Execute deterministic build/release pipeline per docs/modules/devops/ARCHITECTURE.md:

  • Reproducible builds with SBOM/provenance, cosign signing, transparency logging.
  • Channel manifests (LTS/Stable/Edge) with digests, Helm/Compose profiles.
  • Performance guard jobs ensuring budgets.

Expectations

  • Coordinate with Scanner/Scheduler/Notify teams for artifact availability.
  • Maintain CI reliability; update TASKS.md as states change.

Required Reading

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

Working Agreement

    1. Update task status to DOING/DONE in both docs/implplan/SPRINTS.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.