OpenChainGraph Suite · SOX 404 / ICFR

ICFR Control-Test 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.

SOX 404 control-test evidence cycle: population, sample, and per-item test results reconcile into ONE test-conclusion artifact (coverage, exception count vs tolerable deviation, test conclusion). gate_status and any deficiency candidate are recorded per the §27 Human Accountability vocabulary: the tester is the §27.1 preparer, every conclusion requires a reviewer sign-off, and deficiency severity classification is a separate reviewer approval record; both recorded now, enforced once HA-RETRO-1's runtime gating is wired to this chain. Never a filed submission.

OpenChainGraph · 1 Step compliance control Hash-Anchored §4 chain_depth:1 Client-Side · Zero PII
Chain Topology: ICFR Control-Test Cycle
§4 Execution Hash · Chain Definition Anchor
execution_hash:computing…
Chain Stages · 1 Step
1 ROOT · TERMINAL node
Control-Test Evidence Composer art-461-control-test-evidence-composer
Reconciles the declared sample against per-item test results into sample coverage, exception count, and test_conclusion, final stage. Fixed review_required gate routes every conclusion to a §27.4 reviewer sign-off (recorded, not yet runtime-gated); an exception_count above the tolerable-deviation threshold flags a deficiency CANDIDATE for the reviewer's severity classification, never computed here.
MCP Call · compose_control_test_evidence
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "compose_control_test_evidence",
    "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 SOX test round just closed. Did the key control hold within the tolerable exceptions we declared?
Run the AINumbers MCP tool `run_chain` with {"chain":"icfr-control-test-cycle"} and read `art-461-control-test-evidence-composer.within_tolerance`.
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/icfr-control-test-cycle.html