Plane 0 · Infrastructure
CoreX Stack deployment, provider boundaries and runtime infrastructure
Retain as infrastructure/deployment layer; do not expose placeholder hardware/security claims.
Recovered CoreX architecture
Reuse what was already designed. Activate only what is real.
This catalogue reconciles the earlier CoreX planes, consoles and solution catalogue against the modern Living Trust build. Synthetic metrics and unsupported readiness/compliance claims are deliberately excluded.
Legacy planes → modern architecture
Plane 1 · Nodes & Networks
Service identity, integration channels, deployment topology and provider connectivity
Reframe around channels, service identity and deployment topology.
Plane 2 · Kernel Authority
Living Trust Kernel + Trust Fabric policy
Now materially implemented through canonical objects, lifecycle, authority preservation and policy evaluation.
Plane 3 · Defense & Cloak
CoreX Defender / Security Posture / state-evidence consistency
Reconcile legacy Defender concepts onto current event, Watch and risk infrastructure; do not revive unsupported cloak/AV claims.
Plane 4 · Identity
CoreX Identity & Authenticity + Credentials
Identity assurance is implemented; biometric/device/media providers remain externally gated.
Plane 5 · Events
Canonical event spine + Living Trust timeline + Audit & Activity
Current event infrastructure is stronger than the legacy design.
Plane 6 · Storage
Credential/event persistence + Evidence Vault + retention policy
Persistence exists; private Evidence Vault requires storage/KMS/retention binding.
Plane 7 · Territory
Execution territory, region, jurisdiction policy and sovereign deployment
Keep territory as a governance dimension rather than a product.
Plane 8 · AI/ML
Explainable Trust Intelligence + CoreX Defender
Deterministic/explainable signals are current; probabilistic AI claims require evidence and validated models.
Plane 9 · Policy
Trust Fabric, verifier policy, entitlements and release governance
Unify mature current policy primitives in Studio.
Plane 10 · Pods
Product lines, vertical trust profiles and deployable solution packs
Use reusable product/vertical profiles rather than separate trust cores.
Identity
CoreX ID → CoreX Identity & Authenticity
Preserve verified-attribute/provider UX; replace opaque verification score with explainable assurance dimensions.
Fingerprint Login → Platform Authenticator / WebAuthn
Reuse biometric UX only for platform authenticators. CoreX should never receive raw fingerprint templates. Remove unsupported FIDO2 certification wording.
Email Login → Passwordless Email / Federated Login
Current identity service contains email one-time-code primitives; production delivery/provider/session hardening remains before GA.
Phone Login → Phone Verification Provider Integration
Reuse UX when an SMS/phone provider and abuse controls are actually bound.
Google / Microsoft / Apple Login → Federated OIDC Login
Provider buttons should be rendered only from actually configured federation providers.
Master Console → CoreX Studio — Platform
Console choice must not confer authority; platform access is derived from trusted role/tenant/policy claims after authentication.
Admin Console → CoreX Studio — Organisation
Organisation access is tenant/role/policy controlled after authentication.
User Portal → My CoreX / Holder Workspace
Modern holder workspace already provides identity, access, credentials, transactions, events, evidence and sharing.
Biometric Auth → Biometric/PAD Provider Integration
Provider contracts are the correct home; biometric models do not become CoreX source authority.
Single Sign-On → OIDC / Service & User Federation
OIDC service identity is active; customer IdP federation is deployment-specific.
Multi-Factor Auth → Assurance & Step-Up Authentication
Expose through assurance policy; authenticator execution remains with bound providers.
Passkeys → Passkey / WebAuthn Integration
Legacy fingerprint UX is a design reference; current repo evidence does not show a complete WebAuthn implementation.
Security
CoreX Shield → CoreX Defender / Security Posture
Recover breach/phishing/headers/DNS/IP posture UX only where actual providers/checkers are implemented.
CoreX Comply → Compliance Evidence
VECTOR contains compliance screening, release and evidence primitives.
CoreX Audit → Audit & Activity
Use the modern canonical event spine rather than legacy in-memory audit.
Security Scanner → Security Posture Scanner
No current full scanner engine is evidenced; restore individual checks only with truthful providers/results.
Defender Suite → CoreX Defender
Legacy rules can be reconciled onto Watch, risk signals and canonical events.
Finance
CoreX Pay → CoreX Pay — Transaction Trust
Payment assurance and transaction trust, not acquiring/custody/settlement.
CoreX Invest → Finance / Ownership Vertical
Current repos do not evidence a production investment-management product.
CoreX Link → CoreX Developer & Integration Platform
Integration/API/Webhook concepts now belong in the Developer Platform.
KYC/AML Suite → Identity Assurance + External AML Providers
Do not claim AML/sanctions capability until providers and compliance operations are bound.
Loyalty
Loyalty Hub → Loyalty / Programme Vertical
No current production loyalty engine is evidenced; preserve programme UX as a future vertical.
Carbon Credits → Environmental Attribute / Provenance Vertical
Compatible with Product Trust/provenance if authoritative registry/source integrations exist.
Referral Program → Referral / Promotion Module
May compose with VECTOR promotions; no current referral engine evidenced.
Gamification → Programme Engagement Module
Keep outside the trust kernel.
Platform
CoreX Hub → CoreX Studio
Modern Studio subsumes the central management console.
CoreX Prime → VECTOR Commercial Intelligence
Pricing economics, offers, packages and commercial control-plane primitives already exist in VECTOR.
API Gateway → CoreX Developer Platform / API Surface
Current APIs are live; a separate gateway product is not yet required.
Standards → Standards & Interoperability Catalogue
Current adapters/reference profiles include VC, OpenID foundations, EPCIS, UDI and related standards.
Access
CoreX Access → Policies & Access
Reconcile tenant, role, assurance, disclosure, entitlement and release-class controls into one Studio access model.
CoreX Verify → CoreX Verify & Resolve
Current Verify is broader than the legacy KYC-only positioning.
CoreX Edge → Channels & Deployment
Use for channel/deployment readiness; do not claim a distributed edge-security runtime until evidenced.
Developer
SDKs → CoreX SDKs
Internal client patterns exist; public SDK extraction/package publication remains productisation work.
API Reference → Developer API Catalogue
Developer catalogue is production-deployed; OpenAPI publication is the next step.
Sandbox → CoreX Trust & Policy Sandbox
Side-effect-free CoreX sandbox is live; VECTOR provides additional shadow validation.
Webhooks → Webhook & Event Integrations
Signed lifecycle/webhook paths exist; source ingress can remain externally gated.
Analytics
Analytics Dashboard → Trust / Commercial Analytics
Use actual event/reporting data only.
AI Insights → Explainable Trust Intelligence
Predictive/ML claims require validated models and telemetry.
Custom Reports → Reporting & Evidence Packs
VECTOR reporting/evidence foundations already exist.
Community
CoreX Community → Community / Programme Vertical
Preserve UX idea; no current production community platform evidenced.
CoreX Arena → Community / Engagement Vertical
Retain only if future product strategy requires it.
Forums → Community Forums
Not part of the current trust platform baseline.