Point identity and evidence mappings to current canon owners
Assistant: codex Assistant-Model: gpt-6-astra Assistant-Session: 01a070b5-4994-7271-bd8b-7c3dbcedec4b
This commit is contained in:
parent
c431915d56
commit
b9ae48b00c
9 changed files with 86 additions and 13 deletions
|
|
@ -161,7 +161,7 @@ NetKingdom IAM, identity providers, provisioning sources, directories,
|
|||
authorization systems, security controls, event sinks, audit infrastructure, and
|
||||
optional UI surfaces while remaining useful in simple standalone deployments.
|
||||
|
||||
It may implement identity-canon entities when they are user-domain facts or
|
||||
It may implement InfoTechCanon entities when they are user-domain facts or
|
||||
identity-context mappings. It should reference, map to, or consume adjacent
|
||||
canon entities when their source of truth belongs to NetKingdom infrastructure,
|
||||
security, access-control, governance, or organization systems.
|
||||
|
|
@ -180,7 +180,7 @@ point by compilation or by local evaluation.
|
|||
- operators and tenant administrators managing scoped user populations;
|
||||
- agentic systems that need structured access to user preferences and profile
|
||||
context;
|
||||
- domain services that need identity-canon aligned user, actor, principal,
|
||||
- domain services that need InfoTechCanon aligned user, actor, principal,
|
||||
subject, tenant, team, membership, and evidence references without depending
|
||||
on technical IAM implementation details;
|
||||
- `access-engine`, as a PIP consumer of subject, membership, and
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue