SAFIEvidence Map

Proof specimen / public-safe level

Evidence that can be inspected, not merely admired.

SAFI’s credibility is the path from source event to policy context, signed decision, proof package, and independent review. This page stays at specimen level and avoids confidential bytes, source mechanics, and patent-claim detail.

Proof path

Five artifacts an institutional reviewer should ask to see.

01

Event packet

Eligibility, sanctions, custody approval, Sharia review, payment event, transfer rule, servicing event, or denial.

02

Rule context

Jurisdiction, product, partner role, rulebook version, threshold, reviewer, and exception policy.

03

Signed decision

Approved, denied, escalated, or remediated state tied to a reviewable decision payload.

04

Proof bundle

Inclusion-style evidence, export manifest, policy references, and archive path.

05

Verifier readout

Offline inspection result for a selected specimen, without implying regulator approval.

Specimen matrix

What a proof package can demonstrate, and what it cannot.

SpecimenReviewer questionSAFI artifactBoundary
Compliance decisionWas the workflow approved or denied under a known rule context?Signed decision, policy version, reviewer state, exception logDoes not imply regulator approval.
Custody approvalWas a vault or signer action authorized under dual control?Vault state, quorum record, signer posture, key-ceremony referenceDoes not imply live-value custody authorization.
Islamic reviewWas transaction-specific Sharia review evidence preserved?Asset eligibility, review materials, approval conditions, purification registerDoes not certify Sharia compliance.
PAYAGENT mandateWas an automated workflow inside its authority?Mandate record, proof-of-intent, allow/deny receipt, human thresholdDoes not claim autonomous financial execution.
Diligence Atlas