Credential persistence
Canonical credential and lifecycle persistence.
CoreX exposes public-safe readiness so pilots, developers and enterprise evaluators can distinguish what is active now from what is ready, gated or awaiting external authority.
Canonical credential and lifecycle persistence.
History and current-state separation.
Optional ledger/transparency evidence; not business authority.
Current runtime measurements, reproducible workload evidence and modeled scale envelopes are kept separate from provider subscription limits.
The 60,000–5,000,000 range is retained as historical lineage but is not promoted as a current production claim until revalidated.
Public product availability and external-provider activation are shown separately.
Current-state and historical verification over governed evidence.
Lifecycle-managed signed credentials and portable projections.
Living assets, rights, lineage and governed history.
Provider-neutral governed intelligence, AI assurance and bounded tool orchestration over trusted CoreX context.
Financial trust, transaction assurance, reconciliation, Watch and Defender over external financial facts.
Provider-integrated payment trust and lifecycle orchestration without CoreX becoming payment processor or custodian.
APIs, SDKs, Studio, Control Plane, metering, governance and provider-neutral trust infrastructure.
Provider-neutral connectivity catalogue and governed adapter framework.
Holder-facing identity, credential and verification channel with wallet protocol readiness.
Signed bridge requires production URL and shared secret configuration.
Provider-neutral fulfilment, tracking, return and lifecycle rails are implemented; the selected carrier/locker/3PL remains an external activation gate.
Finance trust and reconciliation can consume consent-bound banking evidence, but regulated provider access and interoperability remain external gates.
Payment provenance and lifecycle ingestion are implemented provider-neutrally; Paytrail or another processor remains an external activation gate. Processor provenance is evidence only and Shopify remains commerce lifecycle authority.
Provider-neutral OIDC browser authentication resolved through canonical CoreX IdentityBinding, Actor and Tenant context.
OIDC-based service identity remains active for trusted service-to-service contexts.
Issuer transport activates only when token and credential delivery semantics are complete.
Verifier transport activates only when request and response validation semantics are complete.
This surface intentionally excludes secrets, private identifiers and internal authority credentials. It describes runtime/readiness state only.