Start with the outcome. Inspect the machinery behind it.
This map connects market-facing products to the capabilities, adapters, channels and external gates that actually support them. It is generated from current platform registries rather than maintained as a separate marketing inventory.
Four ways to start
The eight product doors remain intact; these four paths reduce first-screen choice overload.
How do we issue, manage and present trusted credentials or holder proofs?
How do we connect commerce and finance events without moving source authority into CoreX?
How do we deploy, govern, monitor and scale the trust infrastructure?
Connect without moving authority
Adapter state is explicit so a connector can be technically available without being mistaken for provider activation.
shopify commerce
Reference commerce adapter. Shopify remains authoritative for current order/payment/fulfilment source state.
Authority: SHOPIFY
payment provider
Provider-neutral payment adapter contract. Paytrail onboarding is external-gated; CoreX does not process or custody money.
Authority: BOUND_PAYMENT_PROCESSOR
accounting erp
Declarative adapter target for ERP/accounting systems; customer/provider-specific API binding remains deployment work.
Authority: BOUND_ACCOUNTING_OR_ERP_SYSTEM
open finance
Engineering profile only. Production activation requires regulated provider/API access and applicable consent/interoperability evidence.
Authority: REGULATED_BANK_OR_OPEN_FINANCE_PROVIDER
identity provider
Authentication evidence feeds CoreX IdentityBinding; external authentication never creates CoreX authority.
Authority: BOUND_IDENTITY_PROVIDER
logistics provider
Provider-neutral logistics adapter; real carrier/locker/3PL activation remains external.
Authority: BOUND_CARRIER_OR_3PL
registry source
Registry adapters preserve statutory/source authority and project only governed evidence into CoreX.
Authority: BOUND_REGISTRY
structured data source
Generic structured-data ingestion for Google/Microsoft forms and sheets, CSV files, databases, object stores or direct CoreX uploads. Provider-specific authentication remains deployment configuration.
Authority: BOUND_DATA_CONTROLLER_OR_SOURCE
api webhook source
Provider-neutral API/event ingestion path over the CoreX Integration Edge.
Authority: BOUND_API_OR_WEBHOOK_SOURCE
communications provider
Credential and trust-event distribution adapter. External provider remains delivery authority and delivery does not alter credential lifecycle state.
Authority: BOUND_COMMUNICATIONS_PROVIDER
location presence provider
Optional provider/source adapter for presence evidence. CoreX presence policy combines signals without treating any one provider as universal location truth.
Authority: BOUND_LOCATION_OR_SITE_SIGNAL_SOURCE
SECURITY
security access privacy kernel
W2 converges default-deny RBAC/ABAC/ReBAC requirements, purpose, consent, delegation, assurance, commercial entitlement, risk and disclosure into one deterministic policy contract without replacing the bound Kernel policy provider.
security discovery read separation
Discovery/search authorization is explicitly independent from known-reference read/verification authorization.
security break glass governance
Break-glass semantics require high assurance, explicit reason, bounded expiry, audit evidence and post-access review; they never create cross-tenant or legal authority.
security disclosure receipts
Deterministic disclosure receipts record policy/version, disclosed and withheld claims, and decision lineage without copying sensitive evidence payloads.
signer provider fabric
Signer-purpose contract is frozen; current value-network adapters do not reuse credential or holder keys and signed transaction submission is disabled by default.
security recovery assurance
Canonical negative-authorization, tenant-isolation, disclosure, provider-failure, webhook-replay and non-destructive recovery rehearsal matrix is release-gated; production fault injection remains separately governed and unauthorized by this capability.
trust presence multisignal
Multi-signal presence assurance combines GNSS/fused location, geofence, device integrity, QR/NFC/BLE/Wi-Fi, challenges and authority witness without making one signal universal truth.
privacy presence minimisation
Presence/location policy enforces purpose, minimisation, authority/consent and retention controls, with continuous tracking disabled by default.
privacy cross ecosystem learning
Cross-ecosystem learning inputs are gated against direct identifiers, raw unredacted free text and unaggregated cross-tenant data.
security kernel route authorization
Reusable route middleware delegates protected action decisions to the CoreX Kernel policy provider using actor, tenant, workspace, territory, assurance and contextual selectors.
security delegated access grants
Revocable time-bounded delegated grants support governed acting-on-behalf-of use cases without transferring canonical subject or tenant authority.
security adaptive authentication profile
Risk-aware authentication profiles prefer phishing-resistant WebAuthn/passkeys, preserve provider-neutral OIDC compatibility and require step-up for consequential actions.
security privacy access baseline
Default-deny privacy access assessment enforces tenant/workspace match, purpose limitation, least privilege, step-up for consequential actions, minimum disclosure and separately authorized export.
security key lifecycle baseline
Managed key lifecycle assessment requires purpose/tenant scope, rotation and revocation, rejects static cloud credentials and prefers workload identity for managed signing/encryption keys.
security defender
CoreX Defender deterministic delivery-risk assessment is implemented over Watch delivery evidence; it does not autonomously block or use AI authority.
COMMERCE
commerce vector
Provider-neutral commerce/entitlement orchestration is available through VECTOR; source payment/order authority remains with the bound commerce provider.
commercial subscription control
Canonical provider-neutral subscription lifecycle now owns draft, payment-pending, active, past-due, suspended, non-renewing and terminated commercial state over existing CoreX plan/offer/price/subscription/entitlement models.
commercial billing provider adapter
Billing providers may supply checkout, payment, customer, subscription and invoice facts but never become CoreX tenant, role, commercial-plan or entitlement authority.
commercial settlement policy
Declarative settlement acceptance profiles project through Product Fabric so products and verticals can accept approved value rails without embedding network-specific code or automatic commercial satisfaction.
commercial token entitlement
Token-holding conditions may be projected into commercial policy but cannot directly create tenant membership, role, publication or entitlement authority.
FINANCE
finance transaction trust
Provider-neutral financial fact, transaction, payment, invoice, refund and reversal trust profiles are implemented without CoreX becoming payment or banking authority.
finance reconciliation
Deterministic financial reconciliation detects conflicting provenance, missing payment links, refund/payment mismatches and authority gaps without moving money or making regulated financial decisions.
finance watch
Finance Watch templates reuse governed durable event subscriptions for payment, refund, invoice, reconciliation and provider-health changes.
finance defender
Finance Defender adds deterministic financial-risk signals; it is advisory, does not autonomously block funds and has no AI authority.
pay provider orchestration
CoreX Pay provider-orchestration contracts are implemented; external processors remain payment authority and CoreX never holds customer funds.
settlement intent
Tenant-scoped payment intents persist through the canonical event spine and validate accepted asset, network, account and regulatory references before creation.
settlement quote
Settlement quote recording is implemented with expiry, intent binding and explicit quote-source authority; CoreX does not fabricate exchange rates.
settlement observation
Network evidence observation is implemented independently from commercial settlement semantics, including native/token transfer extraction for EVM and Solana RPC adapters.
settlement finality
Network-specific finality is normalized before Finance reconciliation; non-final transactions remain pending and never release entitlement.
settlement reconciliation
Settlement reconciliation checks exact asset representation, destination, atomic amount, duplicate transaction use, compliance state and existing CoreX Finance rules.
settlement receipt
Auditable settlement receipts persist through the event spine while preserving Finance -> commercial satisfaction -> entitlement authority sequencing.
finance acceptance harness
Synthetic payment/refund/reconciliation acceptance scenarios validate CoreX Finance/Pay behavior before live PSP activation.
NETWORK
network registry
Runtime network registry and capability discovery are active with immutable CoreX network IDs and replaceable adapter bindings.
network caip identifiers
CAIP-2, CAIP-10 and CAIP-19 compatible identifiers provide chain-agnostic external addressing while immutable internal CoreX IDs remain canonical lifecycle identifiers.
network adapter fabric
Provider-neutral adapter routing is active. Named ledgers, payment rails and any future CoreX-native network remain replaceable implementations and never become product or entitlement authority.
network capability negotiation
Each registered network declares the account, balance, transfer, simulation, execution, finality and settlement-proof capabilities actually bound in the current runtime.
network evm adapter
Generic EVM balance, transfer-evidence, finality, native-transfer simulation and signed-payload broadcast contracts are implemented; current production Polygon remains a configured EVM network rather than a platform dependency.
network solana adapter
Solana RPC balance, token-account, parsed transfer evidence and finalized-state observation are implemented without coupling CoreX business logic to Solana; transaction construction/signing remains externally gated.
cross network transport
Cross-network asset transport is deliberately separate from semantic and execution interoperability; bridges and representation movement are never implicit wallet behavior.
CONTROL PLANE
infrastructure portability baseline
Canonical provider-neutral infrastructure baseline freezes compute, persistence, storage, scheduler, queue, workload-identity, signer, telemetry, RPC and integrity-anchor authority boundaries across managed, sovereign, hybrid and future CoreX-native deployment profiles.
infrastructure provider fabric
Infrastructure providers are replaceable implementations and never become identity, product, custody, legal, settlement or entitlement authority.
operations durable work leasing
Production schema prerequisite is satisfied and the runtime implements atomic SKIP LOCKED claim, lease renewal, stale-lease rejection, bounded retry, completion and dead-letter lifecycle. Queue/lease state is execution transport and never business authority.
product fabric declarative
Declarative product definitions compose capability, integration, channel and authority metadata into governed product projections.
solution pack registry
Governed reusable solution-pack registry exposes deployment compositions without creating tenant, provider, commercial or legal authority.
solution pack compiler
Side-effect-free compiler turns a governed solution pack into product manifests, templates, capabilities, external gates and tenant desired state for the existing release path.
infrastructure provider acceptance framework
Generic provider acceptance lifecycle standardizes discovery, configuration, binding verification, preflight, live acceptance, evidence digest, approval, activation and observation while refusing to infer approval or live acceptance.
ai shared contracts
Stable Platform↔AI Trust Context, Action Receipt, Evaluation and Tool Manifest contracts are machine-discoverable and preserve Platform truth authority.
ai governed runtime
Provider-neutral AI governance, advisory runtime contract and synthetic evaluation suite are implemented; AI remains advisory and non-authoritative.
programme participation outcome
Canonical Programme, Cohort, Participation and Programme Session persistence composes capture, presence, attendance, evidence, competency, credential and outcome primitives into a reusable cross-vertical participation/outcome fabric.
programme source finality
Programme data-loop closure is derived from a declared collection cutoff, completed processing, sealed required sources, evidence-backed provenance and reconciliation state. Human ceremony or partner sign-off does not govern whether the data loop is closed.
programme kpi automation
Deterministic KPI snapshots compute from evidence-backed observations through versioned definitions and cutoff timestamps, eliminating spreadsheet/manual calculation as the authoritative KPI path while preserving source measurement authority.
decision evidence matrix
Deterministic evidence matrix supports required, weighted and informational criteria plus exceptional-case review without creating award or eligibility authority.
ai cross ecosystem learning
Governed AI learning can compare evidence quality, operational responsiveness and capability performance across deployments without cross-tenant PII leakage or canonical mutation.
control plane guided operator experience
Guided operator blueprints hide trust-engine mechanics behind use-case, source, evidence, authority and presentation configuration while preserving an expert mode for advanced administrators.
studio capture builder
No-code Studio builder creates immutable versioned direct-capture definitions with field privacy, source-authority and evidence semantics; private value storage remains Evidence Vault and tenant-policy gated.
studio visual composition
CoreX-owned page/component/navigation/theme contracts, revisioned persistence, responsive preview and a visual recovery editor are active; embedded Puck/Tiptap editor primitives remain implementation details over the same governed contract.
studio navigation theme
Navigation and theme documents are versioned through CoreX Content Control with tenant/workspace scoping, protected trust semantics and role-gated publication.
studio visual navigation manager
Visual navigation administration manages hierarchical items, navigation modes, revisions and role-gated publication while server validation preserves URL and visibility boundaries.
studio visual theme manager
Visual theme administration exposes governed tokens, brand presets, live preview and revisions while protected trust semantic mappings remain read-only and server-enforced.
studio visual shell manager
Visual shell administration composes governed navigation and media references into reusable headers, announcements and footers without transferring authority from their source registries.
media library
Media metadata, revisions, privacy classification and stable asset references are active. A provider-neutral HTTPS upload-broker adapter is implemented and fails closed until explicitly configured.
studio presentation governance
SEO metadata, safe redirects, locale fallback policy, controlled revision rollback and portable export/import operate through CoreX Content Control; imports create drafts only and never bypass publication authority.
studio presentation reuse
Reusable sections, page templates and shell/header/footer profiles are revisioned through CoreX Content Control and can materialize new page drafts without creating customer-specific kernel logic.
studio reuse aware builder
The native Site Builder consumes reusable sections, templates and shell profiles from CoreX Content Control; published shell selection drives header/footer navigation without changing authorization semantics.
studio schema driven builder
The native visual builder renders component property controls from the canonical registry schema, exposes SEO, responsive/style overrides, governed media/data binding and publication-quality preflight, while retaining an expert raw escape hatch over the same document contract.
studio nested composition
The native builder composes registered components into declared child slots, supports nested selection/reordering/removal and preserves the same canonical component tree consumed by validation and rendering.
studio native rich text
Native visual rich-text editing serializes only allow-listed structured nodes and marks into the existing Tiptap-compatible JSON contract; unsupported HTML is discarded and arbitrary scripts are never persisted.
studio page revision manager
The visual builder can open governed page revisions, create and duplicate pages, preview drafts, save immutable revisions and publish role-authorized drafts while enforcing route-collision protection inside the same Content Control authority.
studio live draft preview
Unsaved page documents can be server-rendered through the same validated production presentation renderer inside an authenticated sandboxed preview without creating a revision or published state.
studio visual reuse authoring
Selected visual component subtrees can become reusable section drafts and current page compositions can become page-template drafts through the existing CoreX Content Control reuse contracts.
studio editor contract
Editor manifest, structured rich-text validation, safe data-binding checks and presentation preflight are active. Native builder is self-hosted; Puck/Tiptap remain replaceable package bindings over CoreX-owned documents.
studio ecosystem presentation
Published presentation documents can drive existing solution surfaces such as AdaptSprint and CoreX Verify through explicit bindings with deterministic native fallback; presentation does not acquire trust, commercial or source authority.
studio presentation profile scaffold
COREX, ADAPTSPRINT and DARE_NEXUS presentation profiles can scaffold governed page/navigation/theme/shell drafts for review; no automatic publication or authority transfer occurs.
studio visual presets
Brand-token-derived dark/light visual presets can create governed theme drafts and drive the shared customer shell while protected trust semantics and publication authority remain unchanged.
studio guided control center
Task-oriented Site, Brand, Content, Data, Publishing, Solutions, Quality and Advanced controls converge existing presentation capabilities without creating a second content authority.
studio corexos reference migration
CoreXOS migration registry classifies public and protected surfaces as governed, governed-with-fallback, candidate, native high-assurance or deferred so presentation can migrate without moving trust, registry, identity or policy authority.
studio progressive disclosure modes
Guided, Standard and Expert Studio modes progressively disclose configuration depth while preserving identical role and policy authority.
studio solution setup
Guided solution setup creates draft-only CoreX, AdaptSprint, DARE Nexus or custom white-label page/navigation/theme/shell compositions for deliberate review and publication.
studio data binding planner
Registered presentation components can be paired with registered data sources through data-class compatibility checks; bindings do not create source, trust or authorization authority.
studio publication quality gate
Pre-publication inspection reports composition blockers and SEO, accessibility, responsiveness and data-binding warnings without changing published state.
studio resource descriptor registry
CoreX-owned presentation/discovery metadata drives role-aware Studio navigation, resource search, quick-create handoffs, help and developer references without granting authorization or source authority.
studio unified shell
Authenticated Studio surfaces share one resource-descriptor-driven shell with tenant/workspace/solution/environment context, breadcrumbs and command navigation; context selection never creates authority.
studio resource index
Disposable PostgreSQL full-text/trigram discovery projection is production-active after governed application and verification of migration 20260925154500_add_corex_resource_index. Canonical state, entitlement and access authority remain with owning resources.
studio action projection
Normalized Action Projection presents setup, review, sync, provider, publication, evidence, access and quota attention states while every mutation remains with its owning governed capability.
studio resource explorer
Reusable Resource Explorer is production-active with Resource Index storage ready, providing search/filter/sort/status/scope/owner views, safe details drawer and bounded pagination without generic bulk mutation authority.
studio resource index prewarm
Authenticated Studio shell load performs bounded tenant-scoped Resource Index freshness checks so first-use discovery is populated without a new scheduler or authority path.
studio universal resource detail
Universal resource detail and activity projections expose safe discovery metadata and payload-free canonical event metadata, while opening the owning route re-enforces authorization and mutation authority.
studio resource handoff
Stable role-checked Studio resource handoffs expose owning routes, support references and authorised audit deep links for operational continuity without transferring access or creating parallel assignment, approval, comment, entitlement or source authority.
studio adaptive interaction kernel
Local-first tenant/actor-scoped Studio preferences synchronize favorites, recents, saved Resource Explorer views, Guided/Standard/Expert depth and navigation state with optimistic conflict handling; preference state never becomes canonical, entitlement, authorization, publication or source authority.
studio guided continuity
Role-filtered, resumable onboarding and contextual help reuse the Resource Descriptor Registry and existing revision/rollback workflows. Progress is personal presentation state only and recovery links never duplicate mutation or publication authority.
studio human status language
Canonical human status language translates internal lifecycle/readiness states into consistent labels, explanations and next-action classes while exact technical state remains available on deliberate request.
studio interaction feedback state
Shared interaction feedback grammar covers loading, saving, conflict, stale, degraded, gated, step-up, long-running, partial and failure states with accessible human guidance; it is presentation-only and creates no canonical, authorization, entitlement or source authority.
platform feature rollout control
Provider-neutral feature rollout decisions support deterministic defaults, staged percentages and replaceable providers. Rollout decisions never grant entitlement, authorization, commercial rights or source authority.
control plane capability state reconciliation
Advisory capability-state consistency checks detect duplicate IDs, unsafe ACTIVE states and poorly explained gates without auto-activating capabilities or fabricating external readiness.
studio configuration schema 2020 12
JSON Schema Draft 2020-12 is the portable configuration-validation baseline. CoreX UI metadata for Guided/Standard/Expert modes, help, sensitivity and secret references is separate and never carries authorization or trust authority.
experience wcag 2 2 aa engineering baseline
Shared human surfaces carry the CoreX WCAG 2.2 AA engineering baseline, required acceptance viewports, keyboard/focus/reflow/reduced-motion contracts and explicit separation between engineering acceptance and any formal conformance claim.
developer human api reference
Self-hosted human API reference renders the existing public OpenAPI contract into searchable, linkable operation documentation while the canonical machine JSON remains unchanged and developer-only.
studio case evidence workspace
Tenant-scoped Studio workspace projects event-sourced cases/CAPA and canonical evidence chronology without creating automatic sanctions, legal classifications or a parallel case authority.
analytics governance responsiveness
Measured acknowledgement, decision, ownership, escalation and backlog signals support diagnosis without creating an automatic governance verdict.
analytics outcome attribution
Outcome attribution distinguishes observed change, association and contributory evidence from causal claims that require an approved evaluation design.
decision versioned policy
Decision criteria and exceptional-review rules are versioned and hash-addressed so material criteria cannot be silently changed retrospectively.
channel low bandwidth
Constrained-network profiles prioritize compact HTML/JSON, progressive disclosure, deferred heavy media and queue-first capture so core workflows remain usable on 2G/3G and intermittent links.
outcomes loop kernel
Generic Loop profiles, progressive disclosure and automation planning provide programme-neutral evidence-to-outcome composition without hard-coded customer or programme names.
channel pwa resilient client
Installable PWA foundation provides an offline fallback, explicit encrypted same-origin request queue, queue expiry, idempotent replay, conflict/auth holds and image downscaling without caching protected trust APIs.
acceptance low bandwidth field
Engineering support is active; real field-network acceptance remains external evidence and must not be inferred from laboratory/client implementation.
outcomes results framework
Generic input/activity/output/outcome/impact framework compiler preserves indicator evidence sources, methodology, attribution class, disaggregation and evidence cutoffs.
outcomes competency graph
Provider-neutral competency definitions support framework, level, evidence threshold, occupation and cross-framework equivalence references without hard-coding a named curriculum.
outcomes opportunity graph
Generic opportunity requirements can be matched against established competency evidence without creating placement, employment or funding authority.
outcomes partner delivery trust
Partner delivery profiles evaluate configured scope, evidence coverage, unresolved cases and validity without replacing contracting or statutory approval authority.
outcomes portfolio rollup
Organisation/portfolio/programme/project/cohort/region/partner hierarchies can roll up governed measurements while preserving source-level authority.
infrastructure rebase registry
Discoverable cross-repository rebase registry classifies reusable primitives, vertical/profile ownership, compatibility wrappers, deprecation lineage and promotion priorities.
workflow governed lifecycle
Generic evidence- and authority-gated lifecycle state machine supports domain profiles without rebuilding transition semantics per vertical.
control plane capability auditor
Automated capability reconciliation detects unregistered references and low-discoverability active capabilities without activating external authority.
control plane runtime
Tenant-scoped control-plane snapshot and governed capability/install/commercial composition are deployed without becoming payment or source authority.
control plane tenant release reconciliation
Bounded scheduled tenant-release reconciliation is mounted; it reconciles declared desired state and does not create authority roles or mutate capability grants.
VALUE
value control plane p0
Production schema prerequisite is satisfied. Value Control Plane P0 can be enabled internally for governed registry, policy, intent, simulation and approval staging; signing/submission and live value movement remain separately gated.
asset registry
Economic asset, network representation, settlement account and regulatory-profile registries are implemented and fail closed when production bindings are absent.
asset representation
Economic asset identity is separated from network representation; representations require explicit network and equivalence policy.
account registry
Network account bindings and custody models are implemented without creating custody, tenant or identity authority.
regulatory asset profile
Regulatory asset/service profiles are explicit external-authority bindings. CoreX software never self-classifies a token as legally permitted, exempt or regulated.
HOLDER
wallet custody policy
Self-custody, external-provider, merchant-treasury and CoreX-managed models are distinct policy bindings; technical wallet capability does not silently activate custody or transfer-on-behalf-of-client.
pass holder
CoreX Pass holder product is composed over identity, credentials, QR verification and wallet protocol readiness; certified-wallet claims remain gated.
INTEGRATION
connect adapter fabric
CoreX Connect exposes a provider-neutral adapter catalogue covering commerce, payments, finance/ERP, identity, logistics and registry-source integration classes.
connect adapter factory
Universal adapter manifest factory standardizes identity, authority, token, webhook, retry, drift, reconciliation, deletion and tenant-isolation contracts.
integration structured data ingress
Provider-neutral structured-data ingress supports forms, spreadsheets, CSV, databases, object stores and direct uploads through verified Integration Edge semantics.
media http upload broker
CoreX can bind binary media upload intents to any approved storage broker over a strict HTTPS contract without coupling presentation documents to a storage vendor.
data native capture
Native governed data-capture definitions validate direct CoreX/white-label submissions and emit canonical capture events without making external forms mandatory.
connectivity resilient sync
Idempotent metadata-first synchronization supports offline, 2G and 3G operation through small batches, compression guidance, deferred binaries, retry with jitter and non-destructive reconciliation.
connectivity offline capture receipt
Offline capture receipts preserve payload integrity, sequence and reconciliation intent while explicitly preventing offline submissions from becoming canonical state or expanded authority.
OPERATIONS
operations autonomous activation executor
Autonomous activation executor completes internal declarative/configuration work, skips external hard stops and never fabricates source authority, credentials, spend or Shopify cutover.
operations activation control center
Protected Activation Control Center reconciles capability, provider-binding and external-gate state into evidence-driven next actions without creating provider, tenant, commercial, legal or regulatory authority.
operations product experience analytics
Privacy-minimised product-experience events use CoreX structured telemetry by default and can feed optional sinks without raw queries, identity/tenant/workspace identifiers, evidence, form values or session replay.
operations request observability
Infrastructure-wide W3C trace context, correlation/support IDs and privacy-minimised structured telemetry provide request observability without logging bodies, query strings, cookies, authorization material or identities.
operations production database migration control
Manual-dispatch migration control compares repository Prisma history with production, refuses unexpected pending or divergent migrations, serializes applies, requires an exact confirmation phrase, runs Prisma migrate deploy under Node 22 and verifies post-apply storage readiness without printing database credentials.
operations production migration ledger reconciliation
Exceptional manual-dispatch control for auditing and reconciling legacy Prisma migration history. It can repair only a fixed three-index legacy drift allowlist after duplicate-data preflight and exact confirmation; otherwise it cannot deploy schema migrations, excludes the Resource Index migration from reconciliation, and verifies that only the Resource Index migration remains pending afterward.
operations investigation lifecycle
Investigation state changes use canonical events, preserve evidence/history and require authority for consequential resolution, dismissal or escalation.
operations delivery receipts
Credential/evidence delivery status is recorded independently from credential lifecycle state.
operations case resolution
Generic case/CAPA contract supports triage, containment, root cause, corrective action and effectiveness review without automatic legal or sanction authority.
presence target resolver
Generic presence-target resolution supports assets, facilities, events, worksites, deliveries and inspections; location evidence remains minimised and does not itself establish attendance or legal presence.
operations nervous system
Unified operational projection converges activation, provider gates, Watch/Defender-style signals and recommended actions without autonomous blocking.
performance scale automation
Evidence-driven scale recommendations identify binding constraints without automatic paid capacity changes.
operations event delivery
Durable event subscriptions, leased delivery workers, retry, dead-letter, replay and scheduled backlog draining are production-active.
operations trust epoch reconciliation
Bounded scheduled Trust Epoch sealing, checkpoint submission and reconciliation are active.
operations data retention
Bounded scheduled retention reconciliation is mounted and provider-neutral; current Shopify Level-1 retention processing remains a safety control and does not broaden Shopify data scope.
watch event driven
CoreX Watch is implemented as governed durable event subscriptions. Use remains entitlement- and tenant-policy controlled.
TENANCY
tenancy deployment factory
Tenant/pilot deployment factory generates governed desired-state, acceptance and external-gate plans without creating tenant/source authority.
tenancy white label deployment factory v2
White-label deployment factory composes tenant deployment planning with Guided/Standard/Expert operator experience, presentation configuration, provider/domain gates and acceptance/recovery checklists without executing external authority transitions.
tenancy white label
Tenant trust profiles, brand presentation and disclosure-policy separation are production-active; customer-specific domains and provider bindings remain deployment configuration.
VERTICAL
profile education programme
Education/Campus is an active profile over the shared Programme & Participation fabric; it owns no parallel identity, event or persistence authority.
vertical deployment factory
Education, property, supply-chain, finance and workforce blueprints compose existing Product Fabric and preserve external authority.
vertical property
Property Source Trust production template is compiled from shared registry, verification, presence, reconciliation and trust-event primitives. Live property/title/source claims remain externally authority-bound.
vertical education
Education Portable Trust production template is compiled from shared credential, evidence, outcomes, lifecycle and identity-assurance primitives. Live institution, qualification and accreditation claims remain externally authority-bound.
vertical programme activation
Incubating Programme Activation & Delivery factory composes programme, identity, evidence, credential, Watch, Defender and AI foundations. Internal contracts are active; live DARE claims remain gated by customer/source authority and real-pilot acceptance.
vertical medical supply
Medical-supply provenance and controlled-chain profiles are encoded over the same trust primitives, with no implied regulatory approval.
vertical logistics
Last-mile and high-value delivery proof profiles are encoded as reusable custody/evidence policies rather than a separate platform.
vertical supply chain
General provenance passports can compose source, transformation, custody, certification, sensor and delivery events.
IDENTITY
identity provider passwordless
Passwordless email or magic-link authentication is supported only through the registered human identity provider adapter. CoreX consumes the upstream assertion and resolves it to CorexIdentityBinding/CorexActor; legacy LoginCode/Session authority is not revived.
identity provider adapters
Provider-neutral human OIDC adapter is configured through AUTH0_COREX_PROD; canonical CoreX authority still requires IdentityBinding.
identity oidc service
OIDC-based service identity boundary is implemented for trusted service-to-service contexts.
EVIDENCE
trust attendance proof
Reusable attendance evidence composes presence, check-in, site-signal, source-register, witness and interaction proofs; attendance does not automatically imply completion.
evidence explainable trail
Compact evidence reports can expose a collapsible derivation trail linking source observations, reconciliation, deterministic rules, authority decisions and the current canonical state, with optional deep-analysis links for contested or complex cases.
evidence strength taxonomy
Common evidence-strength levels separate source declaration, verification, corroboration, authority verification and independently verifiable proof without conflating evidence assurance with outcome desirability.
trust event projection
Generic audience-tiered event/object trust projection replaces brand-specific projection logic while preserving customer wrappers as profiles.
evidence bundle
Generic closed-loop evidence bundle supports source records, discrepancy resolution, review and sign-off across audits, programmes, grants, inspections and delivery.
reconciliation entity source
Generic tokenized entity/source reconciliation detects repeated identifiers and authoritative binding conflicts while prohibiting automatic merge or wrongdoing inference.
reconciliation rule engine
Generic deterministic fact reconciliation executes provider-neutral validation plus domain rule packs while preserving source authority and prohibiting automatic fraud/legal conclusions.
evidence funding expenditure
Generic funding/expenditure evidence records planned, incurred, approved and paid observations with budget variance and eligibility references without creating payment or grant authority.
evidence private vault
Private evidence vault bound in eu-central-1.
CREDENTIAL
credential distribution
Provider-neutral credential distribution plans email, SMS, CMS, holder portal, wallet, QR, webhook and download delivery while preserving credential lifecycle authority.
credential adaptive presentation
Credential presentation can adapt between mobile, tablet, desktop, print and embed surfaces while preserving explicit user override and alternate projections.
credential persistence
Credential/event persistence is declared ready for this environment.
credential signed
Canonical credential issuance, cryptographic proof and lifecycle semantics require both signer and persistence readiness.
credential certificate qr
Human-readable certificate, JSON projection and QR verification surfaces are implemented and depend on the credential persistence spine.
credential lifecycle status
Suspend, reinstate, revoke, supersede and expiry-aware verification are implemented but require persistent credential state.
credential public independent proof
Confirmed production ledger receipts expose transaction/block/registry/explorer evidence without exposing PII or canonical hashes.
INTEROP
wallet interop harness
OID4VCI/OID4VP interoperability harness and synthetic matrix are implemented without claiming external wallet qualification.
interop w3c vc
Privacy-minimal W3C VC 2.0 projection is deployed over canonical CoreX credentials. Projection availability is active; formal conformance/qualification is not claimed.
interop openid4vci vp
OpenID4VCI pre-authorized issuance transport and OpenID4VP request/ES256 response validation are implemented. Runtime activation remains fail-closed until the production trust-profile and endpoint configuration is explicitly enabled; no qualification claim is made.
interop gs1 epcis
Supply-chain trust events can map to GS1/EPCIS-style identifiers and event semantics without changing CoreX canonical authority.
interop udi medical device
Medical-device profiles reserve UDI/product, lot/serial and authority evidence fields; regulatory truth remains with competent sources.
METERING
commercial entitlement blueprints
Product/offer definitions derive entitlement, quota, integration and metering desired state without creating price, billing or payment authority.
metering usage
Idempotent tenant/workspace usage observations and bounded summaries are deployed; observations are not billing authority.
metering quota enforcement
Entitlement-first quota evaluation is deployed and fails closed when authoritative quota policy is unavailable.
VERIFY
verify public reference
Provider-neutral public reference verification with minimum disclosure.
verify vector proof sync
Signed CoreX VECTOR proof-ingest receiver is deployed; sender is integrated into VECTOR production.
TRUST ANCHOR
trust anchor ledger
Ledger adapter bound: COREX_POLYGON_POS_REGISTRY_V2 on polygon-pos.
trust anchor transparency merkle
Persistent historical-integrity records are batched into Merkle Trust Epochs and checkpointed through COREX_POLYGON_POS_TRUST_EPOCH_V1 on polygon-pos.
Operational in the platform, subject to tenant/policy gates where applicable.
Engineering exists and can be activated when its declared boundary is satisfied.
A real provider, evidence, certification or authority boundary remains.
This public map exposes no secrets and creates no authority. External banks, PSPs, registries, identity providers and other source systems remain authoritative for their facts.