stella-ops.org/git.stella-ops.org
1
0
Fork 0
Code Issues Pull Requests Actions 1 Releases Wiki Activity
Files
66cb6c4b8af58a33efa1521b7953dda834431497
git.stella-ops.org/src/Policy/__Libraries/StellaOps.Policy/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.3 KiB
Raw Blame History

StellaOps.Policy — Agent Charter

Mission

Deliver the policy engine outlined in docs/modules/scanner/ARCHITECTURE.md and related prose:

  • Define YAML schema (ignore rules, VEX inclusion/exclusion, vendor precedence, license gates).
  • Provide policy snapshot storage with revision digests and diagnostics.
  • Offer preview APIs to compare policy impacts on existing reports.

Expectations

  • Coordinate with Scanner.WebService, Feedser, Vexer, UI, Notify.
  • Maintain deterministic serialization and unit tests for precedence rules.
  • Update TASKS.md and broadcast contract changes.

Required Reading

  • docs/modules/policy/architecture.md
  • docs/modules/platform/architecture-overview.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.