Financial Ops Pack v1.0constitution presetmeasure, never moneyApache-2.0

EcoCloud Trust — Financial Ops Pack

A control preset for bank operational-risk, fintech ops, and payments-operations teams. It is a deterministic EcoCloud Agent Constitution (the eight schema-valid action-gate keys) plus a map of the operational-risk controls to the governance kernels that already enforce them, today. A preset wiring shipped primitives — not a new product, a certification program, or a money rail.

EcoCloud clears governed work; your bank settles money.

The control map

OpRisk controls → the kernels that enforce them

Every row is a deterministic control that runs in the execution path — not a policy PDF. Each links to its live kernel demo.

#ControlOpRisk pillarEnforced by
1Risk & control register (RCSA): each control is a constitution rule; a control-test is a dry-run.Identify & assess3 kernels
2Four-eyes (maker–checker) + signing-limit escrow before high-impact writes execute.Mitigate & enforce2 kernels
3Authority subsetting — an agent's powers are a strict subset of its sponsoring human's.Mitigate & enforce1 kernel
4Counterparty gate — KYA passport status + LEI / IBAN / BIC validation + revocation hotlist before any action touches a counterparty.Third-party & fraud2 kernels
5Egress allowlist — no governed action to a destination outside the approved set.Third-party & fraud1 kernel
6Message preflight — ISO-8583 envelope shape, mandatory fields, currency & limit checks before a payload leaves the boundary.Execution & process1 kernel
7Dispute arbitration — reason-code taxonomy, SLA clocks, and an N-role review quorum.Monitor & report2 kernels
8Reconciliation — invoice / obligation vs contract → exceptions queue + signed dispute evidence.Monitor & report1 kernel
9Regulator mode — read·check·approve·mutate lineage + causal trajectory replay for investigations.Monitor & report2 kernels
10Compliance evidence — the tamper-evident audit graph exported as a SOC 2 / regulatory evidence pack.Monitor & report1 kernel
11Signed Outcome Receipt — offline-verifiable, zero-trust proof that a controlled action actually closed.Monitor & reportlive
12Fleet integrity — behavioral-drift canary + flash-crash breaker on the agent fleet.Monitor & report2 kernels
The preset

A schema-valid constitution you can adopt today

The action-gate half of the pack. It validates against the canonical constitution.schema.json (v0.1.0) and runs unchanged in the browser, edge, and Node kernel. Paste it into your workspace constitution or extend it.

"max_priority": "high",
"forbidden_terms": ["wire transfer", "move funds", "disburse", "payout", "release escrow", "issue credit", "custody transfer", "settle funds", "drop table", "delete production", "rotate prod secret"],
"forbidden_assignees": ["external-counterparty", "unverified-agent"],
"forbidden_tags": ["funds-movement", "settlement", "kyc-exempt", "prod-secret"],
"objective_tags": ["reconciliation", "control-test", "attestation", "preflight", "dispute-evidence", "counterparty-screening"],
"quiet_hours_utc": { "start": 22, "end": 6 },
"max_creates_per_day": 200,
"require_approval_below_confidence": 0.8
The hard boundary

What this is — and what it deliberately is not

EcoCloud does
  • govern
  • validate
  • authorize
  • attest
  • dispute
  • reconcile
  • net
  • prove (signed, offline-verifiable)
EcoCloud does NOT
  • hold balances
  • move or settle money
  • issue credit
  • act as an escrow bank or custodian
  • execute payments
  • replace a core banking / payment switch

Where the money goes. The missing partner is a licensed settlement bank / PSP that reads EcoCloud's attestations and netting statements and moves the funds off-network. That boundary is the moat: EcoCloud stays a neutral controls-and-proof layer, which is what lets bank OpRisk and ops teams adopt it without license drag.

Honest scope. This pack packages what is live: twelve deterministic kernels you can run right now, wired into one coherent control set. It does not ship a certification / "EcoCloud Governed" badge program, settlement-bank partner integrations, a network fee schedule, or multi-region active-active — those are scheme-operator concerns, not capabilities claimed here. See Operating Regulations (or-1) for the network rulebook and What's live for the full shipped/planned split.