OpenChainGraph Suite · Audit & Assurance

QFC Part 371 Recordkeeping Cycle

Note (dated 2026-08-04): a chain composes independent computations performed in an analytical order. No step's output is carried into the next step by the execution model; each step computes from its own declared inputs. This is true of every chain on this site, including chains whose per-step copy below reads as a data handoff.

Single-stage cycle over an institution's own 12 CFR part 371 qualified-financial-contract position, counterparty, and collateral file. The validator checks the file's shape against the appendix's published record layout and ties the file's declared totals to a supplied control-total summary, reporting a shape defect and a totals mismatch as two separate, never-merged findings. The rollup emits the closed decision: auto_pass, review_required, or escalate (did_not_run when no control-total summary is supplied). A file nonconformance routes the finding to internal audit as reviewer; the daily-capability recordkeeping check closes with a preparer/reviewer pair rather than a named external approver, since this is an internal standing test rather than a supervisor-facing filing, though an approver role binding stays available where the institution runs this co-sourced. The bundle evidences the institution's own basis for asserting part 371 recordkeeping conformance; it is not a filing and offers no advice on whether a contract is in fact a covered QFC.

OpenChainGraph · 1 Step compliance control Hash-Anchored §4 chain_depth:1 Client-Side · Zero PII
Chain Topology: QFC Recordkeeping File Validator
§4 Execution Hash · Chain Definition Anchor
execution_hash:computing…
Chain Stages · 1 Step
1 ROOT / TERMINAL node review_required(reviewer)
QFC Part 371 Recordkeeping File Validator art-537-qfc-recordkeeping-file-validator
File-shape validation against the part 371 appendix record layout plus a control-total tie-out, and the rollup closed decision enum, close the recordkeeping-conformance evidence pack. Single stage.
§27 Human Accountability gate: a file nonconformance (review_required) routes the finding to internal audit as reviewer, and a totals mismatch (escalate) is reported as a first-class finding, never silently reconciled. The daily-capability recordkeeping check closes with a preparer/reviewer pair, not necessarily a named external approver, because this is an internal standing test, distinct from a supervisor-facing filing; an approver role binding stays available where the institution runs this co-sourced (§27.1, OPTIONAL by role).
MCP Call · validate_qfc_recordkeeping_file
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "validate_qfc_recordkeeping_file",
    "arguments": {}
  },
  "id": 1
}
https://mcp.ainumbers.co/mcp
Export Artifacts
Download the §4 chain definition artifact (hash-anchored composite JSON) or the §13.11 W3C Verifiable Credentials view. Both derive from the chain definition; no new hash is minted. Available after hash computation.

Ask your agent

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: The QFC recordkeeping file is ready to file. Do its declared totals tie to the control summary behind it?
Run the AINumbers MCP tool `run_chain` with {"chain":"qfc-recordkeeping-cycle"} and read `art-537-qfc-recordkeeping-file-validator.decision.gate_policy`.
Re-run with `inputs` for `art-537-qfc-recordkeeping-file-validator`, reusing the values that result echoed, with `control_totals` changed so its position_count is 3 while the file declares 2. 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/qfc-recordkeeping-cycle.html