- Introduced AGENTS.md, README.md, TASKS.md, and implementation_plan.md for Vexer, detailing mission, responsibilities, key components, and operational notes. - Established similar documentation structure for Vulnerability Explorer and Zastava modules, including their respective workflows, integrations, and observability notes. - Created risk scoring profiles documentation outlining the core workflow, factor model, governance, and deliverables. - Ensured all modules adhere to the Aggregation-Only Contract and maintain determinism and provenance in outputs.
35 lines
1.3 KiB
Markdown
35 lines
1.3 KiB
Markdown
# StellaOps Registry Token Service
|
||
|
||
The registry module issues scoped pull tokens for mirrored container registries while enforcing plan and licence constraints.
|
||
|
||
## Responsibilities
|
||
- Validate Authority-issued OpToks and tenant scopes before issuance.
|
||
- Mint time-bound registry tokens and record issuance ledgers.
|
||
- Expose revocation and audit endpoints for security teams.
|
||
- Integrate with Offline Kit for deterministic token manifests.
|
||
|
||
## Key components
|
||
- `StellaOps.Registry.TokenService` minimal API host.
|
||
- Mongo-backed issuance ledger.
|
||
- Tests under `src/Registry/__Tests`.
|
||
|
||
## Integrations & dependencies
|
||
- Authority for identity & scope verification.
|
||
- Export Center/Offline Kit for distribution.
|
||
- DevOps runbooks for deployment and rotation.
|
||
|
||
## Operational notes
|
||
- Operational guide at ./operations/token-service.md.
|
||
- Telemetry dashboards pending (see ../../TASKS.md).
|
||
|
||
## Related resources
|
||
- ./operations/token-service.md
|
||
|
||
## Backlog references
|
||
- DEVOPS-REGISTRY items in ../../TASKS.md (future work).
|
||
- Registry automation stories tracked in src/Registry/TASKS.md if present.
|
||
|
||
## Epic alignment
|
||
- **Epic 10 – Export Center:** provide signed, auditable registry token bundles for mirror distribution.
|
||
- **Epic 14 – Identity & Tenancy:** enforce tenant-aware scopes, PoE alignment, and revocation policies.
|