Registry of Registries
Canonical layers
The four canonical layers of the federation. KARTEL Core is the authority for each; platforms consume. Each layer is described in one structure — readable by people and shaped for machines.
Identity Registry
active- Purpose
- One federated identity across every platform — a single person is the same subject everywhere.
- Canonical key
- CPIF Subject ID (cpifSubjectId)
- Authority
- KARTEL Core
- Steward
- Keycloak realm kartel-ecosystem
- Consumers
- MoyPolk · RusJAz · Community Group
- Contract
- IdentityContract
Geography Registry
active- Purpose
- One canonical UK region taxonomy. Platforms consume; they never self-author regions.
- Canonical key
- CanonicalRegionCode (ITL1, e.g. TLI)
- Authority
- KARTEL Core
- Steward
- MoyPolk (taxonomy API)
- Consumers
- MoyPolk · RusJAz · Community Group
- Contract
- GeographyContract
Organisation Registry
active- Purpose
- One canonical organisation hierarchy: CEA → Foundation → School → Venue.
- Canonical key
- canonicalOrgCode (readable, not UUID)
- Authority
- KARTEL Core
- Steward
- KARTEL Core (Core-owned registry)
- Consumers
- RusJAz · Community Group
- Contract
- OrgAnchor
Campus Registry
active- Purpose
- One canonical identity per accredited operating centre. A campus may be SCHOOL-tier (owns accreditation, classes, governance); orthogonal to its institution, not a child of it.
- Canonical key
- campusCode (readable, e.g. ZNANIYE-CHELSEA)
- Authority
- KARTEL Core
- Steward
- KARTEL Core (Core-owned registry)
- Consumers
- RusJAz
- Contract
- CampusAnchor
Federation Registry
active- Purpose
- The integration gate every project passes before production — the federation's rule of admission.
- Canonical key
- Federation Integration Gate (8 items)
- Authority
- KARTEL Core
- Steward
- KARTEL Core
- Consumers
- all projects
- Contract
- Federation Gate
Public registry — status and architecture only. Operational detail and any personal data live in the access-controlled internal surface, never here.