1 · Living Trust
Resolve a supported order, transaction or credential and show current vs historical status, evidence integrity and public proof.
This hub routes to production-safe or side-effect-free demonstrations. Provider-gated actions stay gated; public verification, policy, presentation and sandbox demonstrations are available now.
Resolve a supported order, transaction or credential and show current vs historical status, evidence integrity and public proof.
Open a confirmed Trust Receipt and inspect independent integrity evidence without exposing customer PII or treating an anchor provider as source authority.
Demonstrate ALLOW, DENY and STEP_UP behavior with deterministic fixtures and no production side effects.
Show how assurance, disclosure, branding and delivery profiles change presentation without changing canonical authority.
Show certificate, card, QR, API and portable representations over the same governed object.
AdaptSprint is a separate Fennorica product that uses selected CoreX capabilities through a white-label solution installation. Its brand, commerce, content, fulfilment and customer journey remain AdaptSprint-owned.
Follow a problem-specific path from outcome to inspectable evidence, value modelling and a governed pilot plan without turning the demo into a sales-only gate.
Public Verify, Trust Receipt and authenticated workspaces are deployed.
Public Verify and Trust Receipt are responsive; Studio/workspace responsive shell is activation-ready.
Responsive web layouts are compatible; dedicated tablet acceptance remains a release test rather than a new architecture.
QR-linked verification surfaces are implemented; credential QR issuance remains coupled to credential persistence readiness.
Mobile-first shell and offline semantics exist; installability/service-worker caching remains a separate activation step with strict trust-data cache boundaries.
W3C VC projection exists; live OpenID wallet transports/interoperability remain gated.
CoreX verification, trust infrastructure, credential and living-object APIs are deployed.
Signed lifecycle/webhook receiver paths exist; some source ingress remains externally gated.
Provider-neutral event/object architecture supports machine/device sources; device-specific adapters remain deployment-specific.
Offline verification policy semantics are activation-ready; offline results must never claim live lifecycle freshness.
Resilient sync contracts support offline/2G/3G queueing, idempotency, small-batch metadata-first transfer, compression guidance and deferred large binaries; installable client queue/service-worker transport remains to be activated per client surface.