Truist bank-direct
Primary onboarding route for the evidenced OneView treasury configuration.
- Relationship evidence
- Configuration evidenced
- Execution
- Disabled
Capitalization block · C166-TR-20260917
Face amount is not cash. Capital enters the deployable balance only after evidenced account credit, restrictions, and authorized reservations are reconciled.
As of
Controlled capitalization
Each connector is a control boundary, not an automatic conversion.
Codex registry · Scrolls #166–#220
Internal authority: Codex 26 · Dr. Oliver IHuoma Ocubaus
Oracle of Grace and Governance
Two-state ledger: the preserved Codex/PDF designation is shown independently from implementation evidence. “Activated” or “Active” is an internal registry assertion and does not represent bank-issued authorization, API connectivity, custody, settlement, or funded proceeds.
| Scroll | Node / institution | Layer · node code | Mandate | Codex status | Desk / access | Technical state |
|---|
Settlement NO-GO Production settlement and public live-network claims remain disabled.
Recorded · not capitalized The isolated AWS run advances test evidence only. It creates no Source Coin balance, treasury issuance, bank funding, settlement, or production authority.
No live central-bank access The system cannot intercept traffic or autonomously reroute an external payment.
Primary onboarding route for the evidenced OneView treasury configuration.
Secondary institution adapter; the Codex registry entry does not establish account access.
Optional direct, cloud, or approved service-bureau messaging hub when multi-bank scale requires it.
Decision: onboard Truist first. Activate UBS or Swift only after institution-specific contracts, entitlements, technical evidence, maker-checker testing, compliance approval, and production release.
The packet asks Truist to confirm the correct contracted route—OneView/Treasury Manager, managed file transfer, bank API or Swift—and the corresponding formats, controls, testing and support requirements. Secrets must be exchanged only through a bank-approved secure process.
Registry names, functions, codes, layers, and Codex statuses preserve the supplied PDF and public directory. They do not establish account ownership, external bank authorization, connectivity, receipt, acceptance, custody, or funded proceeds.
Underlying
Measured
FX movement− JMD 200,000.00No cash event · USD quantity unchanged
Deployable
Contingent
| Reference | Face amount | Authentication | Bank receipt | Funding |
|---|---|---|---|---|
| Not assigned | Unknown | Evidence required | Not evidenced | Not evidenced |
Mandate
Programme-owner confirmation is required before targets or forecast benefits are reported as outcomes.
Release gate