21 lines
1.0 KiB
Markdown
21 lines
1.0 KiB
Markdown
# Implementation plan — Registry Token Service
|
||
|
||
## Current objectives
|
||
- Maintain deterministic behaviour and offline parity across releases.
|
||
- Keep documentation, telemetry, and runbooks aligned with the latest sprint outcomes.
|
||
|
||
## Workstreams
|
||
- Backlog grooming: reconcile open stories in ../../TASKS.md with this module's roadmap.
|
||
- Implementation: collaborate with service owners to land feature work defined in SPRINTS/EPIC docs.
|
||
- Validation: extend tests/fixtures to preserve determinism and provenance requirements.
|
||
|
||
## Epic milestones
|
||
- **Epic 10 – Export Center:** deliver signed registry token bundles supporting mirror/Offline Kit workflows.
|
||
- **Epic 14 – Identity & Tenancy:** integrate tenant-aware scope validation, revocation, and audit trails.
|
||
- Track follow-ups in ../../TASKS.md and src/Registry/TASKS.md.
|
||
|
||
## Coordination
|
||
- Review ./AGENTS.md before picking up new work.
|
||
- Sync with cross-cutting teams noted in ../../implplan/SPRINTS.md.
|
||
- Update this plan whenever scope, dependencies, or guardrails change.
|