OpenChainGraph Suite · CONTRACT A3 · arch #5

Small Business 1071 Readiness Check

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.

Check small business lending coverage readiness in two independent stages: first compute whether a financial institution meets the CFPB Section 1071 origination threshold from caller-supplied origination counts and validate SBLAR records against caller-declared required fields (ART-475); then a session receipt aggregating the run's execution hashes (CRY-05). All origination counts, field lists, and SBLAR records are caller-supplied; findings are arithmetic findings, never coverage determinations. Federal only, not legal advice.

Note: all origination counts, field lists, and SBLAR records are caller-supplied inputs, never inferred by the kernel. The coverage computation applies the caller-supplied origination counts against the Section 1071 threshold; readiness is a computation from caller-declared facts, not a CFPB coverage determination. Findings are arithmetic findings, never legal conclusions.

OpenChainGraph · 2 Steps compliance mandate · CFPB 1071 Hash-Anchored §4 chain_depth:2 Client-Side · Zero PII
Chain Topology (linear): Small Business 1071 Readiness Check → Session Receipt
§4 Execution Hash · Chain Definition Anchor
execution_hash:computing…
Chain Stages · 2 Steps
1 ROOT node
CFPB 1071 Coverage Check & SBLAR Record Validator art-475-cfpb-1071-coverage-check
Computes Section 1071 coverage from caller-supplied origination counts and validates SBLAR records against a caller-declared required-field list
MCP Call · compute_cfpb_1071_coverage
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "compute_cfpb_1071_coverage",
    "arguments": {}
  },
  "id": 1
}
https://mcp.ainumbers.co/mcp
↓
2 TERMINAL · D2 node
Agent-Action Audit-Trail Aggregator cry-05-agent-action-audit-trail-aggregator
Produces session_receipt_root, the Merkle root over the run's execution_hashes (final stage)
MCP Call · aggregate_execution_receipts
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "aggregate_execution_receipts",
    "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: Do my small business origination counts trigger Section 1071 reporting requirements?
Run the AINumbers MCP tool `run_chain` with {"chain":"small-business-1071-readiness-check"} and read `art-475-cfpb-1071-coverage-check.originations_year1_count`.
Re-run with `inputs` for `art-475-cfpb-1071-coverage-check`, reusing the values that result echoed, with `originations_year1_count` set to 999. 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/small-business-1071-readiness-check.html