Cardinal Intelligence is the evidence layer beneath SafeSend, SafeReceive, policy, simulation, and protected settlement.
Normalized evidence and replaceable provider adapters are connected in the controlled pilot. The reserved investor BLOCK scenario uses clearly labelled synthetic evidence. External coverage depends on approved licences, credentials, networks, and provider availability. Cardinal does not claim universal tracing or complete compliance coverage.
Evidence model
Each evidence item identifies the screened subject, chain, category, severity, confidence, source, observation time, optional expiry, and supporting tags.
Public responses expose sanitized evidence. They must not expose provider secrets, raw licensed payloads, or internal investigation notes.
Provider modes
Demonstration evidence
The controlled investor scenario uses a reserved wallet address and synthetic evidence for stolen-funds exposure, sanctions-list exposure, and illicit-service association. The interface and comprehensive report identify these records as demonstration fixtures and retain their source references and timestamps.
This proves evidence normalization, policy enforcement, and report generation without making an unsupported allegation about a real wallet. In production, a sanctions claim must come from an authorised current source and should be described as evidence linking a wallet or entity to a sanctions list—not as a sanctioned bank account unless a separate banking-data source supports that statement.
Source and freshness rules
- Identify the source and observation time for every externally derived claim.
- Do not display expired or unavailable evidence as current.
- Route conflicting or incomplete evidence to
REVIEW unless an approved policy requires BLOCK.
- Use provider data as evidence. Keep the final decision in Cardinal policy.
- Record licensing, retention, deletion, attribution, and redistribution restrictions before enabling a provider.
Proprietary intelligence
Cardinal may build an internal graph from permitted scan outcomes, verified reports, address relationships, contract observations, and settlement results.
Keep raw licensed data separate when provider terms prohibit reuse. Protect stored evidence with tenant isolation, access controls, retention rules, and an audit trail.
Attribution and source-of-funds rules
- Distinguish a direct match from indirect exposure and record the number of hops when known.
- Identify whether an entity attribution is verified, provider-attributed, customer-supplied, inferred, or synthetic demonstration data.
- Do not turn a wallet or exchange attribution into a bank-account claim without a separate authorised source.
- Preserve the source reference and observation time needed to reproduce the decision.
- Keep licensed provider facts separate from Cardinal-owned observations, policy outcomes, and derived graph relationships.
- Route ambiguous, conflicting, stale, or incomplete provenance to
REVIEW unless an approved policy requires another action.
Cardinal’s proprietary advantage should come from permitted observations, normalized evidence, graph relationships, decision outcomes, and settlement feedback. It should not depend on copying or redistributing restricted provider datasets. 
