Standardized Agreements & Legal Templates · Cluster 20 · OpenChainGraph v0.4

Standardized Agreements & Legal Templates

Every mature open-legal standard splits into a negotiable cover page and a fixed, review-once body incorporated by reference. This cluster assembles that split as OCG nodes: cover-page variables become kernel inputs, the fixed body ships as a vendored, hash-pinned artifact. The Mutual NDA Composer fills a Common Paper MNDA (Version 1.0, CC BY 4.0) from your Key Terms, then the Acceptance Binder lets a party countersign the exact assembled terms by hash, never by re-embedding the text. We ship the assembler, not the signed contract.

Common Paper MNDA v1.0 · CC BY 4.0 Fixed Body Verbatim · §3.3 Immutable-Body Model Agent-Countersignable via §16 contract-api.json Twin Zero PII

Agent-native differentiator: each vendored template is published as an MCP Resource (stable URI, body hash in metadata); the assembler is a Tool; the packet is a Prompt. An agent can discover a standard, read its variable contract, fill it, and countersign at a specific body hash, handing a verifiable "I accepted THESE exact terms" receipt to another agent.

EDUCATIONAL: All outputs are assembled drafts and acceptance receipts, not executed contracts or legal conformity certificates. Real party identity, signatures, and legal effect stay off-platform. Consult a licensed attorney for your jurisdiction.

Assemble & bind

Two nodes: assemble the agreement from your Key Terms, then bind a party's acceptance to the exact assembled artifact.

ART-276 · assemble_mutual_nda

Mutual NDA Composer

Assembles a Common Paper Mutual NDA (Version 1.0, CC BY 4.0) from your Cover Page Key Terms: purpose, effective date, MNDA term, term of confidentiality, and governing law and jurisdiction. The Standard Terms body is vendored verbatim and never modified. Emits a contract-api.json variable map twin.

assemble_mutual_nda Fixed Body Verbatim

ART-277 · bind_agreement_acceptance

Agreement Acceptance Binder

Binds a party's acceptance to a specific assembled agreement artifact by execution_hash, template_id, and vendored body_sha256, never by re-embedding the text. Carries no party identity. An optional §16 signature turns this into a countersignable receipt.

bind_agreement_acceptance Zero-PII Receipt

Chains: mutual-nda-composer (1 chain)

Assemble then bind, hash-chained via parent_hashes.

mutual-nda-composer · 2 nodes · Linear

Mutual NDA Composer

Assembles the MNDA from Cover Page Key Terms (ART-276), then binds a party's acceptance to the assembled artifact by its execution_hash and body_sha256 (ART-277).

→ ART-276 → ART-277

Chain topology

mutual-nda-composer ART-276 (assemble_mutual_nda) → ART-277 (bind_agreement_acceptance)

Reference: the full standards landscape

A curated, license-tagged catalog of every open and proprietary agreement standard surveyed for this category — computable (Strand A) and reference-only (Strand B).

Reference directory · both strands

Agreement Standards Directory

Common Paper, Bonterms, oneNDA/oneDPA/oneSaaS, YC SAFE, Accord Project, FINOS CDM, OpenAgreements, CommonAccord, plus the AI-vendor axis (Common Paper AI Addendum, EU MCC-AI, GSA AI clause). License-tagged, linked to canonical sources.

Reference tier

Common Paper Mutual NDA v1.0: commonpaper.com/standards/mutual-nda/1.0. Vendored verbatim, CC BY 4.0. Verify current version before relying on the assembled text for a real transaction.

Immutable-body model (§3.3): the vendored Standard Terms body is never edited, regardless of license. All customization lives in the Cover Page Key Terms and an Additional Terms attachment layer, never spliced into the body.

Zero-PII (§0): party identity, signatures, and notice addresses stay as literal placeholder tokens. Real filling and signing happen off-platform, at your own e-sign flow.