OpenChainGraph Suite · CONTRACT A3 · IP Rights

Tokenization Prep

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.

Generate an ISCC content fingerprint, declare AI-training rights via TDMRep, validate any on-chain royalty split, produce a TASL attribution string, and certify the result as a tokenization-ready license VC. The royalty-split step is optional: pass empty input if no on-chain split applies and the workflow continues to certification.

OpenChainGraph · 5 Steps IP rights mandate Hash-Anchored §4 chain_depth:5 Client-Side · Zero PII
Not legal advice. This workflow maps inputs to pre-existing published license families and standards only. No legal counsel is provided. Consult a licensed attorney in your jurisdiction before relying on any output for commercial or legal purposes.
Chain Topology — ISCC Content Code Generator → TDMRep Reservation Builder → Royalty Split Validator → Attribution String Generator → License Election Certifier
§4 Execution Hash · Chain Definition Anchor
execution_hash:computing…
Chain Stages · 5 Steps
1 ROOT node
ISCC Content Code Generator art-201-iscc-content-code-generator
ISCC content fingerprint and datahash feed Stage 2 AI-training rights reservation
MCP Call · generate_iscc_code
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "generate_iscc_code",
    "arguments": {}
  },
  "id": 1
}
https://mcp.ainumbers.co/mcp
↓
2 D2 node
TDMRep AI Training Reservation Builder art-202-tdmrep-reservation-builder
TDMRep JSON and Content-Usage header feed Stage 3 royalty split validation
MCP Call · build_tdm_reservation
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "build_tdm_reservation",
    "arguments": {}
  },
  "id": 1
}
https://mcp.ainumbers.co/mcp
↓
3 D3 · OPTIONAL node
Royalty Split Validator art-208-royalty-split-validator
Validated split config and config_hash feed Stage 4 attribution string generation (step is optional — proceed with empty input if no split applies)
MCP Call · validate_royalty_split
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "validate_royalty_split",
    "arguments": {}
  },
  "id": 1
}
https://mcp.ainumbers.co/mcp
↓
4 D4 node
Attribution String Generator art-207-attribution-string-generator
TASL attribution string, ccREL JSON-LD, and RDFa block feed Stage 5 license election certification
MCP Call · generate_attribution_string
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "generate_attribution_string",
    "arguments": {}
  },
  "id": 1
}
https://mcp.ainumbers.co/mcp
↓
5 TERMINAL node
License Election Certifier art-199-license-election-certifier
Exports certified tokenization-ready license VC with ISCC binding and execution_hash — final stage
MCP Call · certify_license_election
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "certify_license_election",
    "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: We are preparing the catalog asset for tokenization. Which royalty split finding blocks a clean prep pack?
Run the AINumbers MCP tool `run_chain` with {"chain":"tokenization-prep"} and read `art-208-royalty-split-validator.valid`.
Re-run with `inputs` for `art-208-royalty-split-validator`, reusing the values that result echoed, with `cap_bps` changed so cap_bps set to 4000, keeping the two 5000 bps entries. 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/tokenization-prep.html