Check a credential, reference or proof
Resolve current status and available evidence.
AdaptSprint remains an independent customer-facing product and brand. This page shows the reusable CoreX Living Trust capabilities available to its deployment without collapsing AdaptSprint into CoreX or inventing authority that belongs to AdaptSprint, Shopify or other source systems.
This reference deployment exposes practical entry points instead of only describing infrastructure. Actions remain governed by the authority of the underlying source system.
Resolve current status and available evidence.
See issuance, lifecycle and QR-backed credential capabilities available to the tenant.
Commerce and fulfilment remain AdaptSprint-owned while CoreX supplies trust and verification rails.
Review what is active, ready, externally gated or still progressing through controlled activation.
Sign in to see tenant-scoped identity, access, credentials, transactions, events, evidence and controlled sharing using live persisted data where available.
The same solution-pack compiler used for reusable deployments now describes this reference tenant. Compilation remains side-effect free.
23 capability bindings are represented in the compiled desired state.
2 current provider or authority dependencies remain explicit and fail closed.
Capability state is read from the activation registry rather than hard-coded as a claim.
Generic input/activity/output/outcome/impact framework compiler preserves indicator evidence sources, methodology, attribution class, disaggregation and evidence cutoffs.
Provider-neutral public reference verification with minimum disclosure.
Signed CoreX VECTOR proof-ingest receiver is deployed; sender is integrated into VECTOR production.
Canonical credential issuance, cryptographic proof and lifecycle semantics require both signer and persistence readiness.
Human-readable certificate, JSON projection and QR verification surfaces are implemented and depend on the credential persistence spine.
Suspend, reinstate, revoke, supersede and expiry-aware verification are implemented but require persistent credential state.
Tenant trust profiles, brand presentation and disclosure-policy separation are production-active; customer-specific domains and provider bindings remain deployment configuration.
Durable event subscriptions, leased delivery workers, retry, dead-letter, replay and scheduled backlog draining are production-active.
Bounded scheduled Trust Epoch sealing, checkpoint submission and reconciliation are active.
CoreX Watch is implemented as governed durable event subscriptions. Use remains entitlement- and tenant-policy controlled.
Activation boundary: tenant WATCH.ENABLED commercial entitlement and destination policy
CoreX Defender deterministic delivery-risk assessment is implemented over Watch delivery evidence; it does not autonomously block or use AI authority.
Activation boundary: tenant DEFENDER.ENABLED commercial entitlement
Idempotent tenant/workspace usage observations and bounded summaries are deployed; observations are not billing authority.
Entitlement-first quota evaluation is deployed and fails closed when authoritative quota policy is unavailable.
Activation boundary: authoritative tenant/workspace entitlement and quota policy binding
Capabilities such as Verify, evidence lineage, credential lifecycle, Watch, Defender, event delivery, resilient synchronization and outcome infrastructure should surface through the AdaptSprint experience when its tenant configuration and authority permit them. AdaptSprint-specific commerce, content and operational policy remain solution-owned.