Gated §21.4 chain for TMS account lifecycle straight-through processing. Step 1 validates the CGI-MP eBAM state machine across acmt.007 (account opening request), acmt.010 (opening confirmation), acmt.011 (closing request), acmt.017 (modification request), and acmt.019 (modification confirmation) message types. Detects orphan messages and determines the final account state. A §21.4 compliance gate on /acmt_state routes only OPENING_CONFIRMED accounts to Step 2 for immediate in-house-bank pool interest allocation; all other states (closure, modification, pending, invalid) exit at Step 1. No personal data is processed.
/acmt_statevalidate_ebam_acmt_flow{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "validate_ebam_acmt_flow",
"arguments": {
"account_reference_id": "ACCT-REF-20240115-001",
"messages": [
{
"msg_type": "acmt.007",
"msg_id": "MSG-007-001",
"creation_date": "2024-01-15",
"is_confirmation": false
},
{
"msg_type": "acmt.010",
"msg_id": "MSG-010-001",
"creation_date": "2024-01-16",
"is_confirmation": true,
"related_msg_id": "MSG-007-001"
}
]
}
},
"id": 1
}
allocate_ihb_interest{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "allocate_ihb_interest",
"arguments": {
"pool_type": "notional",
"pool_rate_annual_pct": 5.0,
"day_count_convention": "ACT/360",
"period_days": 1,
"currency": "USD",
"members": [
{"member_id": "ACCT-REF-20240115-001", "balance": 500000, "withholding_rate_pct": 0,
"notes": "newly opened account entering pool"},
{"member_id": "EXISTING-POOL-ANCHOR", "balance": 2000000, "withholding_rate_pct": 0}
]
}
},
"id": 2
}
Copy this paragraph into Claude, OpenClaw, or any MCP-aware agent to run this whole workflow on the server and check one field that answers a real question.
Question: Our correspondent account maintenance messages went out overnight. Did any report arrive without the request that authorised it?
Run the AINumbers MCP tool `run_chain` with {"chain":"treasury-account-lifecycle-ebam"} and read `art-262-validate-ebam-acmt-flow.is_valid`.
Re-run with `inputs` for `art-262-validate-ebam-acmt-flow`, reusing the values that result echoed, with `acmt_messages` changed so one report arrives with no matching request. Compare the same field.
Verify: call `verify_execution_hash` (https://mcp.ainumbers.co/mcp) with `claimed_hash` set to `composite_execution_hash` and the full `composite_artifact`.
Ledger, for a human re-check: https://ledger.ainumbers.co/
PII rule: send synthetic or anonymised inputs only. The MCP server runs these kernels and logs no payloads.
Chain page: https://ainumbers.co/chaingraph/chains/treasury-account-lifecycle-ebam.html