33d50fb91e
Co-authored-by: Cursor <cursoragent@cursor.com>
4.6 KiB
Institutional registry — Sankofa / Sankofa Phoenix
Document ID: SANKOFA-REG-001
Version: 1.0
Date: 2026-06-04
Status: Publication reference (pending live ARIN / LEI / state entity IDs)
Organization identity
| Field | Value |
|---|---|
| Parent brand | Sankofa — sovereign authority governing identity, policy, compliance, and ecosystem structure |
| Cloud platform | Sankofa Phoenix — sovereign AI/cloud infrastructure |
| Operating entity | Sankofa Ltd — infrastructure, data exchange, platform orchestration |
| Primary domain | sankofa.nexus |
| Parent organization | Sovereign Hospitallers Order of St. John of Jerusalem |
| Gitea org | Sankofa_Phoenix on gitea.d-bis.org |
Canonical rule: Sankofa Ltd and Sankofa Phoenix are affiliated entities under the Sovereign Hospitallers Order of St. John of Jerusalem. Public copy, entity packs, and ARIN filings must state this affiliation.
Ecosystem role
| Layer | Function |
|---|---|
| Sankofa | Policy, standards, identity authority, marketplace oversight |
| Sankofa Phoenix | Sovereign cloud delivery (Keycloak, multi-tenancy, Proxmox) |
| Complete Credential | Sovereign credential issuance platform hosted on Sankofa Phoenix |
Joint venture: PanTel — telecommunications/6G infrastructure JV with PANDA.
Key infrastructure endpoints
| Service | Domain |
|---|---|
| Public portal | sankofa.nexus, www.sankofa.nexus |
| Phoenix platform | phoenix.sankofa.nexus |
| Proxmox | pve.sankofa.nexus, pve1.sankofa.nexus |
| Keycloak | keycloak.sankofa.nexus |
| Unified portal shell | portal.sankofa.nexus |
| Complete Credential operator | cc.sankofa.nexus |
| CC Keycloak (canonical) | auth.cc.sankofa.nexus |
| CC admin / entity portals | admin.cc.sankofa.nexus, entity.cc.sankofa.nexus |
Registry status
| Registry | Value |
|---|---|
| ARIN OrgId | Pending ARIN assignment |
| LEI | Pending |
| Colorado entity ID | Pending counsel publication |
| Suggested ARIN org name | SANKOFA LTD (or counsel-approved legal name) |
DBIS trust manifest: https://d-bis.org/.well-known/trust.json (entity sankofa, arinRegistrations.sankofa).
Master reference: INSTITUTIONAL_REGISTRY_MASTER.md §8 (gov-portals-monorepo).
ARIN organization registration
Primary organization description
Sankofa Ltd operates Sankofa Phoenix, a sovereign cloud infrastructure platform serving as the technical nexus for affiliated ecosystem operations. Sankofa is an affiliated entity under the Sovereign Hospitallers Order of St. John of Jerusalem. Sankofa Phoenix provides sovereign identity management (Keycloak), multi-tenant cloud orchestration, Proxmox-based compute, and secure networking for institutional platforms including Complete Credential, SMOA, and related settlement and identity services. Internet number resources requested under this organization record will be used exclusively to operate public and member-facing network services in the ARIN region, including institutional portals (
sankofa.nexus), sovereign identity endpoints, Proxmox hypervisor access, blockchain RPC and API infrastructure, Cloudflare tunnel ingress, operational monitoring, and secure administrative tooling supporting Sankofa Phoenix and hosted tenant workloads.
Resource utilization
Allocated IPv4/IPv6 address space will host production and staging services for the Sankofa Phoenix ecosystem: web portals, GraphQL/API gateways, Keycloak identity planes, Crossplane/ArgoCD/GitOps tooling, Grafana/monitoring stacks, Proxmox management interfaces, and tenant-isolated workloads. Address space will not be sub-allocated to unrelated third parties. All resources will be used in accordance with ARIN policy and the ARIN WHOIS Terms of Use.
Related portal links
| Institution | URL |
|---|---|
| Parent Order registry | https://xom.d-bis.org/legal/institutional-registry |
| DBIS institutional registry | https://d-bis.org/cb/dbis |
| Complete Credential entity packs | complete-credential/platform/entity-packs/INDEX.md |
Disclaimer
This document is a consolidated registry reference for internal coordination and ARIN filing preparation. It does not replace founding instruments or counsel-approved filings. ARIN OrgId, LEI, and state registry fields marked "pending" must be confirmed against live registry responses before regulatory or counterparty reliance.