OpenChainGraph Suite · OCG v0.8.7 · US State AI Compliance · Cluster ㉕

SB 53 Frontier Scope

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-step obligation router for the California SB 53 Transparency in Frontier Artificial Intelligence Act (effective 2026-01-01). Kept as its own composer rather than folded into the CAIA/TRAIGA/AB2013 chains — SB 53 serves a narrow frontier-lab audience, distinct from the general deployer/developer compliance-owner persona of the other state-AI chains.

OpenChainGraph · 1 Stepcompliance mandateHash-Anchored §4Client-Side · Zero PII
Asserts a scope/obligation finding only, never that those obligations have been fulfilled. Publishing a safety framework or transparency report is a separate act this chain does not perform or verify. Not legal advice.
Chain Topology — SB 53 Frontier Scope Check
§4 Execution Hash · Chain Definition Anchor
execution_hash:computing…
Chain Stages · 1 Step
1 ROOT · TERMINAL node
SB 53 Frontier Scope Checker art-316-sb53-frontier-scope-checker
is_frontier_model, is_large_frontier_developer, and obligation_set complete the scope determination, final stage.
MCP Call · check_sb53_frontier_scope
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "check_sb53_frontier_scope",
    "arguments": {}
  },
  "id": 1
}
https://mcp.ainumbers.co/mcp
Export Chain Artifact
Download the §4 chain definition artifact (hash-anchored 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: A developer trains to 1e27 FLOPs and books 600 million dollars a year. Which SB 53 duties attach before deployment?
Run the AINumbers MCP tool `run_chain` with {"chain":"sb53-frontier-scope"} and read `art-316-sb53-frontier-scope-checker.is_frontier_model`.
Re-run with `inputs` for `art-316-sb53-frontier-scope-checker`, reusing the values that result echoed, with `compute_flops` set to "1e27". 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/sb53-frontier-scope.html