7ac74f432b
- Institutional / JVMTM / reserve-provenance / GRU transport + standards JSON - Validation and verify scripts (Blockscout labels, x402, GRU preflight, P1 local path) - Wormhole wiring in AGENTS, MCP_SETUP, MASTER_INDEX, 04-configuration README - Meta docs, integration gaps, live verification log, architecture updates - CI validate-config workflow updates Operator/LAN items, submodule working trees, and public token-aggregation edge routes remain follow-up (see TODOS_CONSOLIDATED P1). Made-with: Cursor
Reserve provenance and settlement attestation (staged package)
Purpose: Structured artifacts that connect legal / funding narrative to operational reconciliation (ledger, bank export, chain) without claiming bank or KYT completion where evidence is still pending.
Not legal advice. Entity names, amounts, and references mirror the 3FR / Titan / FIDES funding narrative you supplied; counsel must review before any regulatory submission. Replace or redact for other deals.
Truthfulness rules (supervisory posture)
| Artifact | Declares complete? |
|---|---|
| Attorney receipt attestation | Legal form only — does not replace bank confirmation |
| Settlement finality declaration | Declared finality per your workflow — not universal legal finality |
| Funding origin chain | Structured narrative from documentation review |
| Bank balance certification | AWAITING_BANK_EXPORT until MT940 / camt.053 / API |
| KYT execution record | PENDING until vendor integration |
| Reconciliation trigger | INITIATED — run generate-3way-reconciliation-evidence.sh for machine output |
| Reserve recognition | PROVISIONAL_RESERVE — bank + KYT still pending |
| Reserve monetary linkage | PROVISIONAL_LINKAGE_NARRATIVE — ties MT103, composition, SIS refs, custody cite; EO/DCID = investigative standard reference, not government endorsement; reconcile magnitudes to originals |
| Regulatory stack (HYBX / OMNL / DBIS) | DECLARED_ARCHITECTURE — OMNL LEI (GLEIF); OMNL charter EO + DCID standard references (12829/12968/10450 + DCID 6/4, parallel) in docs — not U.S. endorsement; DBIS SMOM–OSJ; populate regulatoryEvidence for HYBX registration and executed charters |
| Reserve hosting map | PROVISIONALLY_STRUCTURED — links reserve composition to declared entity layers; verify AUSTRAC registration before AML/CTF claims |
Keystone (you must still obtain): Bank-issued MT940, camt.053, or API export. The repo MT940 .txt is a structural specimen — not a substitute for custodian certification, signatures, or seals.
Operator attachment (out of band): Place the real MT103 hard-copy scan as MT103_HARDCOPY.pdf (or your naming standard) in secure storage; do not commit privileged PDFs to git unless policy allows.
Original signatures: When physical hard copies (or PDF scans that faithfully reproduce them) bear original authorized signatures, those artifacts are normally the primary supervisory evidence for execution and intent. The JSON and MT940 specimens in this repo remain format and workflow aids; they do not duplicate or replace custodied originals. Record custody (where originals live, who certified scans, optional file hashes) per your evidence policy.
Layout (package root relative)
| Path | Role |
|---|---|
legal/ATTORNEY_RECEIPT_ATTESTATION_3FR.json |
Counsel receipt anchor |
settlement/SETTLEMENT_FINALITY_DECLARATION.json |
Instruction / receipt / credit flow declaration |
provenance/FUNDING_ORIGIN_CHAIN_3FR.json |
Bond → sale → transfer → allocation chain |
bank/JVMTM_BANK_BALANCE_JSON.json |
Certification container pending bank-issued MT940/camt.053 |
bank/MT940_STATEMENT_3FR_TITAN_RECEIVING_ACCOUNT.txt |
Specimen only — MT940 layout for bank request & archival; not certified |
bank/MT940_STATEMENT_3FR_TITAN_RESERVE_LINKED.txt |
Specimen only — same as above plus reserve / SIS / custody narrative blocks (not bank SWIFT text); use for traceability, not as issued statement |
bank/README_BANK_REQUEST_MT940_CAMT053.md |
Wording to request official MT940 or camt.053 |
bank/JVMTM_BANK_BALANCE_PARSED_EXAMPLE_AFTER_MT940.example.json |
Example parse for JVMTM_BANK_BALANCE_JSON env (3-way generator); not bank-issued |
kyt/KYT_EXECUTION_RECORD.json |
KYT container pending vendor |
reconciliation/3WAY_RECONCILIATION_TRIGGER.json |
Links to ledger / bank file / chain records |
reserve/RESERVE_RECOGNITION_DECLARATION.json |
Provisional reserve classification |
reserve/RESERVE_MONETARY_LINKAGE_DECLARATION.json |
Machine-readable linkage: funding event + composition + SIS standard refs + custody cite (provisional) |
reserve/RESERVE_HOSTING_AND_JURISDICTION_MAP.json |
Reserve composition + Titan custody cite mapped to HYBX / OMNL / DBIS declared roles |
governance/REGULATORY_STACK_DECLARATION.json |
Three-entity stack: commercial vs monetary vs sovereign risk domains; hosting relationship |
governance/REGULATORY_STACK_NARRATIVE.txt |
Human-readable mirror of the stack for auditors (verify against primary evidence) |
Validation
bash scripts/validation/validate-reserve-provenance-package.sh
Archive integration
scripts/omnl/build-omnl-e2e-settlement-audit-archive.sh copies this tree into the zip under reserve-provenance-package/ (alongside settlement-events/, audit-proof/, etc.).
Related repo tooling
- Operational 3-way:
scripts/omnl/generate-3way-reconciliation-evidence.sh— pointJVMTM_BANK_BALANCE_JSONat a filled bank JSON when MT940/API is available. - KYT:
scripts/omnl/fetch-kyt-vendor-report.sh— refuses to fabricate PASS. - JVMTM templates:
config/jvmtm-regulatory-closure/.