stella-ops.org/git.stella-ops.org
1
0
Fork 0
Code Issues Pull Requests Actions 2 Releases Wiki Activity
Files
b058dbe031053c47bd2fbaa513608f24862b0f1a
git.stella-ops.org/src/Policy/StellaOps.Policy.Engine/AGENTS.md
StellaOps Bot efaf3cb789
Some checks failed
Signals CI & Image / signals-ci (push) Has been cancelled
Details
Signals Reachability Scoring & Events / reachability-smoke (push) Has been cancelled
Details
Signals Reachability Scoring & Events / sign-and-upload (push) Has been cancelled
Details
Manifest Integrity / Validate Schema Integrity (push) Has been cancelled
Details
Manifest Integrity / Validate Contract Documents (push) Has been cancelled
Details
Manifest Integrity / Validate Pack Fixtures (push) Has been cancelled
Details
Manifest Integrity / Audit SHA256SUMS Files (push) Has been cancelled
Details
Manifest Integrity / Verify Merkle Roots (push) Has been cancelled
Details
Docs CI / lint-and-preview (push) Has been cancelled
Details
up
2025-12-12 09:35:37 +02:00

1.9 KiB
Raw Blame History

StellaOps.Policy.Engine — Agent Charter

Mission

Stand up the Policy Engine runtime host that evaluates organization policies against SBOM/advisory/VEX inputs with deterministic, replayable results. Deliver the API/worker orchestration, materialization writers, and observability stack described in Epic 2 (Policy Engine v2).

Scope

  • Minimal API host & background workers for policy runs (full, incremental, simulate).
  • PostgreSQL persistence via StellaOps.Policy.Storage.Postgres for packs, runs, receipts, and overlays; in-memory fallbacks for dev/test.
  • Change stream listeners and scheduler integration for incremental re-evaluation.
  • Authority integration enforcing new policy:* and effective:write scopes.
  • Observability: metrics, traces, structured logs, trace sampling.

Expectations

  • Keep endpoints deterministic, cancellation-aware, and tenant-scoped.
  • Only Policy Engine identity performs writes to effective findings.
  • Coordinate with Concelier/Excititor/Scheduler guilds for linkset joins and orchestration inputs.
  • Update TASKS.md, /docs/implplan/SPRINT_*.md when status changes.
  • Maintain compliance checklists and schema docs alongside code updates.

Required Reading

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