Customer Home
Outcome-first organisation view for setup, launch readiness, next actions and everyday work.
Most organisation users begin with Customer Home: what is configured, what needs attention and the next useful action. Organisation, platform and developer depth remain available without becoming the default experience.
Experience depth changes what is presented, not what authority exists. Customer Home is the default organisation experience; deeper controls remain one level away.
Outcome-first organisation view for setup, launch readiness, next actions and everyday work.
Your identity, access, credentials, transactions, events, evidence and controlled sharing.
Broader configuration, infrastructure, provider, developer and expert controls for authorised operators.
Use the existing product surfaces rather than creating parallel administration paths.
Verify references, inspect current/historical trust state and issue Living Trust Receipts.
Map proof target, verifier, assurance, branding, disclosure and delivery format to reusable CoreX policy configuration.
Identity, access, credentials, transactions, events, evidence and sharing.
Tenant-scoped credential administration for authorised operators.
Authenticated domain workspaces resolve their own role gates after sign-in rather than exposing authority on the public Studio landing.
Explore APIs, standards and side-effect-free policy/offline verification sandbox operations.
Capabilities, standards, profiles, templates and production-readiness state.
Assurance, disclosure, references, service tiers and tenant trust profiles.
Reconciled planes, consoles, product concepts and authentication patterns from the earlier CoreX build, classified against current capability.
Resolve a supported reference and return a minimum-disclosure verification result.
Create an evidence-backed proof for a transaction, event, document, product, configuration or other governed record.
Issue a lifecycle-managed credential, certificate, badge or portable credential representation.
Apply tenant issuer, brand and disclosure profiles without changing canonical authority.
Provide white-label, API, bulk, identity/access and enterprise trust integration capabilities.
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.