generated from coulomb/repo-seed
docs: persist user-engine vs net-kingdom integration assessment (new doc + cross-references in SCOPE, boundary contract, guidance, responsibility map, 0018/0019 workplans). Also updated user-engine integration doc to reference it.
This commit is contained in:
@@ -100,6 +100,8 @@ and what NetKingdom is responsible for (meta-orchestration).
|
||||
| **Repo owns** | the headless user-domain service, profile/catalog resolver, projection APIs, local persistence, outbox events, and implementation tests |
|
||||
| **NetKingdom orchestrates** | source-of-truth boundaries with IAM and flex-auth; tenant/platform administration boundaries; application onboarding bindings; membership synchronization rules; projection and claims-enrichment boundaries; audit correlation requirements |
|
||||
|
||||
See `docs/user-engine-netkingdom-integration-assessment.md` for current implementation status, gaps, and recommendations on integration.
|
||||
|
||||
---
|
||||
|
||||
## Resource Kinds NetKingdom Orchestrates (cross-cutting)
|
||||
|
||||
Reference in New Issue
Block a user