| Capability | Status | Notes |
|---|---|---|
| Cardinal web experience | Live controlled pilot | The public product site, product gateway, wallet connection, product routes, customer sign-in, demonstration journeys, and enterprise Admin Dashboard are published at cardinalweb3.com. This does not make testnet or pilot capabilities generally available for production funds. |
| Protection API | Controlled pilot | Authentication, validation, scoring, findings and usage foundations are implemented. |
| SafeSend | Testnet pilot | Connected frontend and Protection API flow; production verification remains. |
| SafeReceive | Controlled pilot | Direction-aware source screening, explainable policy output, evidence provenance, deterministic investor-demo scenarios, and separately metered comprehensive reports are implemented. Licensed production coverage remains unconfirmed. |
| Programmable Escrow | Contract implementation | Core lifecycle and dispute controls exist; production integration and audit remain. |
| Cardinal Intelligence | Controlled pilot | Normalized evidence and replaceable adapters are connected. The reserved investor BLOCK scenario uses labelled synthetic evidence; licensed provider coverage is not yet confirmed. |
| Enterprise Policy Engine | Controlled pilot | Versioned ALLOW, REVIEW, and BLOCK decisions and matched-rule explanations are connected; persisted tenant policies and approval workflows remain 30-day work. |
| Transaction simulation | Adapter contract defined | Fixture and heuristic modes must remain distinct from an approved live simulation provider. |
| Protected Settlement Engine | Architecture roadmap | The existing SafeSend, SafeReceive, Policy, Escrow, and reporting foundations support the direction. Dynamic routing, continuous monitoring, advanced conditions, and Transaction Passports are not production capabilities today. |
| Enterprise Admin Dashboard | Live operational pilot | Protection API metrics, incoming and outgoing protection checks, generated-report metadata, partners, masked API-key records, usage, billing and SafeSend fee views are connected. Customer-portal records, Escrow events and support tickets are not yet centrally ingested. |
| Business Customer Portal | Live controlled demonstration | Separate client sign-in, white-labelled property workflow, payment requests, SafeReceive decision records, and demo data are published. Production-grade multi-tenant identity, roles, billing, retention, and security validation remain required. |
| Branded comprehensive reports | Live controlled pilot | Cardinal-branded report generation, evidence provenance, exposure summaries, and structured institution fields are published for controlled scenarios. Licensed production data coverage and customer charging remain unconfirmed. |
| External threat intelligence | Planned integration | Production provider adapters and owned intelligence datasets remain roadmap work. |
| Support operations | Published contact only | contact@cardinalweb3.com is the verified public contact in Cardinal documentation. A dedicated support mailbox, tenant-scoped ticket queue and response SLA are not yet confirmed. |
| Mainnet deployment | Not yet verified | Requires final configuration, monitoring and security review. |
Documentation records reviewed implementation status. A feature branch or controlled demonstration is not automatically a production release.
View delivery horizons
Review the investor-demo, 30-day, and longer-term scope.
Operate the Admin Dashboard
Review connected data, metric boundaries, operational gaps, and production controls.