# 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`
- `docs/modules/sbomservice/architecture.md`
- `docs/implplan/SPRINT_0142_0001_0001_sbomservice.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.
- 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.