OpenChainGraph Suite · Standardized Agreements & Legal Templates

Mutual NDA Composer

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.

Assembles a Common Paper Mutual NDA (Version 1.0, CC BY 4.0) from Cover Page Key Terms, then binds a party's acceptance to the assembled artifact by its execution_hash, template_id, and vendored body_sha256. The Standard Terms body is vendored verbatim and never modified. Not legal advice.

OpenChainGraph · 2 Steps compliance mandate Hash-Anchored §4 chain_depth:2 Client-Side · Zero PII
Chain Topology: Mutual NDA Composer
§4 Execution Hash · Chain Definition Anchor
execution_hash:computing…
Chain Stages · 2 Steps
1 ROOT node
Mutual NDA Composer art-276-mutual-nda-composer
assembled_markdown and contract_api (template_id, body_sha256, variable_map) feed the acceptance binder as the referenced artifact
MCP Call · assemble_mutual_nda
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "assemble_mutual_nda",
    "arguments": {}
  },
  "id": 1
}
https://mcp.ainumbers.co/mcp
↓
2 TERMINAL node
Agreement Acceptance Binder art-277-agreement-acceptance-binder
accepted_template_id, accepted_body_sha256, and referenced_execution_hash form the countersignable acceptance record
MCP Call · bind_agreement_acceptance
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "bind_agreement_acceptance",
    "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: Legal wants a draft out today but the purpose clause is still blank. Does the composer still accept the cover page?
Run the AINumbers MCP tool `run_chain` with {"chain":"mutual-nda-composer"} and read `art-276-mutual-nda-composer.checks.0.pass`.
Re-run with `inputs` for `art-276-mutual-nda-composer`, reusing the values that result echoed, with `purpose` set to "". 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/mutual-nda-composer.html