OpenChainGraph Suite · CONTRACT A3 · IP Rights

License Compatibility 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.

Map parent and child licenses into canonical rights vectors, compare them across frameworks, and produce a compatibility verdict with reason codes and the required child license. Use as a standalone entry point when you only need to know whether a derivative work can legally adopt a given license, or embed it as steps 2 and 3 of the full IP License Election and Attestation workflow.

OpenChainGraph · 2 Steps IP rights mandate Hash-Anchored §4 chain_depth:2 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 — Cross-License Rights Comparator → License Compatibility Checker
§4 Execution Hash · Chain Definition Anchor
execution_hash:computing…
Chain Stages · 2 Steps
1 ROOT node
Cross-License Rights Comparator art-198-cross-license-rights-comparator
Canonical rights vectors and diff feed Stage 2 compatibility analysis
MCP Call · compare_rights_matrix
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "compare_rights_matrix",
    "arguments": {}
  },
  "id": 1
}
↓
2 TERMINAL node
License Compatibility Checker art-204-license-compatibility-checker
Exports compatibility verdict, reason codes, and required child license — final stage
MCP Call · check_license_compatibility
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "check_license_compatibility",
    "arguments": {}
  },
  "id": 1
}
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: Our library ships under a share-alike license. May a proprietary module build on it?
Run the AINumbers MCP tool `run_chain` with {"chain":"license-compatibility-check"} and read `art-204-license-compatibility-checker.compatible`.
Re-run with `inputs` for `art-204-license-compatibility-checker`, reusing the values that result echoed, with `child_license` changed so the child is CC-BY-NC-4.0 while parent_license is CC-BY-SA-4.0. 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/license-compatibility-check.html