stella-ops.org/git.stella-ops.org
1
0
Fork 0
Code Issues Pull Requests Actions 1 Releases Wiki Activity

feat: Add guild charters and task boards for various components
Some checks failed
Docs CI / lint-and-preview (push) Has been cancelled
Details

Browse Source 
- 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.
This commit is contained in:
master
2025-11-01 02:21:46 +02:00
parent e5629454cf
commit 66cb6c4b8a
227 changed files with 9913 additions and 6210 deletions
Download Patch File Download Diff File Expand all files Collapse all files

40
src/SbomService/StellaOps.SbomService/AGENTS.md
View File

@@ -1,15 +1,25 @@
# StellaOps.SbomService — Agent Charter
## Mission
Expose normalized SBOM projections (components, relationships, scopes, entrypoints) that downstream systems such as Cartographer, Policy Engine, and Scheduler consume. Maintain deterministic SBOM versioning, change events, and tenant-aware access patterns.
## Responsibilities
- Normalize ingest from Scanner outputs/CycloneDX/SPDX artifacts into canonical documents.
- Provide APIs for SBOM metadata, projections, entrypoint catalogs, and version history.
- Emit change events when SBOMs are added or updated so Cartographer and overlay workers can react.
- Enforce Authority scopes/tenancy and deliver observability for SBOM projection latency.
## Expectations
- SBOM documents remain immutable once published; new versions append only.
- Keep projections deterministic and schema-validated; include compliance checklists.
- Update `TASKS.md` whenever status changes and coordinate with Cartographer/Scheduler guilds.
# StellaOps.SbomService — Agent Charter
## Mission
Expose normalized SBOM projections (components, relationships, scopes, entrypoints) that downstream systems such as Cartographer, Policy Engine, and Scheduler consume. Maintain deterministic SBOM versioning, change events, and tenant-aware access patterns.
## Responsibilities
- Normalize ingest from Scanner outputs/CycloneDX/SPDX artifacts into canonical documents.
- Provide APIs for SBOM metadata, projections, entrypoint catalogs, and version history.
- Emit change events when SBOMs are added or updated so Cartographer and overlay workers can react.
- Enforce Authority scopes/tenancy and deliver observability for SBOM projection latency.
## Expectations
- SBOM documents remain immutable once published; new versions append only.
- Keep projections deterministic and schema-validated; include compliance checklists.
- Update `TASKS.md` whenever status changes and coordinate with Cartographer/Scheduler guilds.
## Required Reading
- `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.
- 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.