Readiness status is evidence-driven and can only advance through documented institutional review.
The ten readiness categories below are the standing dimensions against which any institutional pilot must be evaluated. Each category carries a status that can only advance through documented institutional evidence — never through self-attestation.
Do not calculate fake percentages. Do not manufacture evidence.
Named institutional sponsor, signatories and formal pilot authorization.
Jurisdictional legal review, regulatory classification and licensing perimeter assessment.
API, ISO 20022, host-to-host, SFTP and treasury system compatibility.
KYC/KYB, AML/CFT, sanctions screening and regulatory reporting interfaces.
mTLS, HSM/MPC, network security, access controls and key management.
Settlement finality model, payment/finality reference mechanism and reconciliation.
Protected Backing Cell verification, backing attribution and evidence packages.
Five-way reconciliation model, break detection and resolution procedures.
Business continuity, disaster recovery, failure-injection testing and incident response.
Independent security, finality, reconciliation and resilience verification.
The initial institutional pilot follows a strictly bounded, one-institution / one-jurisdiction / one-corridor scope. Each stage below is a gate — no stage may be skipped, and no stage implies approval of the next.Broader treasury holding is outside the initial pilot scope.
The MITHQAL review package is the standing set of artifacts and templates that institutional counterparts may request during a formal engagement. Each item carries the PROPOSED status until an institutional review formally activates it.
These are MITHQAL review artifacts/templates. Not approved by any institution.
Every institutional engagement element should visually distinguish its current evidence state. The five canonical statuses below are the only permitted display values on this surface.
PROPOSED
UNDER_REVIEW
EVIDENCE_REQUIRED
SANDBOX_CANDIDATE
VALIDATED
Never display: APPROVED, LICENSED, SUPPORTED, LIVE, PRODUCTION READY unless backed by real verified evidence.
Two parallel ladders govern institutional readiness: the evidence-state ladder (does institutional evidence exist?) and the technical status ladder (does the implementation satisfy a verification gate?). Both must advance together — neither may be inferred from the other.
Only authorized institutional evidence should move an element forward.
The jurisdiction workflow defines how a jurisdiction evaluation request advances — from initial submission through to institutional validation. None of these states constitutes a license, an approval, or a supported jurisdiction status.
Jurisdiction evaluation request received. This is an evaluation state, not an approval.
MITHQAL has begun reviewing the submission. No institutional commitment implied.
Assessing jurisdictional regulatory environment, infrastructure and corridor feasibility.
Legal classification and regulatory perimeter under evaluation. No license implied.
Technical integration, API and rail compatibility under assessment.
Identified as a potential sandbox testing candidate. Not yet validated.
Identified as a potential pilot candidate. Subject to formal authorization.
Validated through documented institutional review. Requires authorized institutional evidence.
Institutional counterparts, regulators, and reviewers may request the review package or initiate a formal evaluation through the channels below. Initial contact should contain only institutional, non-sensitive information.
meltonsy@icloud.com
Use this channel to request the institutional review package, propose a sandbox evaluation, or initiate a formal architecture review. Replies are not instantaneous and do not constitute an institutional commitment.
Do not submit passwords, private keys, seed phrases, customer credentials, confidential customer information, production banking credentials, or other secrets. Initial contact should contain only institutional and non-sensitive information.