coulomb/user-engine
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Point identity and evidence mappings to current canon owners
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 2s
Details
Build and Publish Container Image / build-and-push (push) Successful in 33s
Details

Browse source 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a070b5-4994-7271-bd8b-7c3dbcedec4b
This commit is contained in:
tegwick 2026-09-06 01:39:09 +02:00
parent c431915d56
commit b9ae48b00c
9 changed files with 86 additions and 13 deletions
Download patch file Download diff file Expand all files Collapse all files

22
docs/canon-mapping.md
View file

@ -4,12 +4,12 @@ Status: candidate
Updated: 2026-06-05
This document maps current `user-engine` implementation concepts to
identity-canon and InfoTechCanon concepts. It is intentionally explicit about
InfoTechCanon identity, organization, access and evidence concepts. It is intentionally explicit about
owned facts, consumed facts, references, and gaps.
## Mapping Stance
`identity-canon` treats `User` as a convenience term, not the root concept.
`InfoTechCanon` treats `User` as a convenience term, not the root concept.
`user-engine` keeps the existing `User` implementation class for compatibility,
but exposes canon-facing context through `identity_context` so consumers can see
the distinct account, actor, subject, principal, tenant, membership, profile,
@ -101,3 +101,21 @@ They verify that:
- cross-tenant identity context is denied without platform scope;
- claims-enrichment context can be read without implying token issuance
ownership.
## Federation source references — 2026-09-06
Current owners: [itc-ident](../../info-tech-canon/infospace/models/identity/InfoTechCanonIdentityModel.md)
for identity, Scope and the User convenience mapping;
[itc-org](../../info-tech-canon/infospace/models/organization/InfoTechCanonOrganizationModel.md)
for actors and membership; [itc-access](../../info-tech-canon/infospace/models/access-control/InfoTechCanonAccessControlModel.md)
for Subject and Principal; and [itc-evid](../../info-tech-canon/infospace/models/evidence/InfoTechCanonEvidenceModel.md)
for Evidence assertions and addressable Evidence Source containers.
[CommerceCanon](../../commerce-canon/infospace/models/counterparty/CommerceCanonCounterpartyModel.md)
owns Customer, Vendor and Legal Entity semantics.
This is a source-coordinate review under CFED-WP-0001-T09. Existing emitted
labels and scenario/test identifiers remain compatibility surfaces; the older
entity mappings above are not silently promoted to conformance with the newly
published draft models. Evidence references do not by themselves establish an
assertion/source distinction in every adapter. A full consumer adoption review
remains demand-driven.