Documents & Collaboration · Playbooks
The firm's judgment, versioned — preferred positions, fallbacks, and red lines that AI applies but can never rewrite.
Included with EdgeLex · Available in EdgeDocs, Microsoft Word, and Lex
Legal Playbook Review⟳ Run again
Applies the exact active firm, practice, client, and Matter policy layers to this saved version.
Complete coverage receipte42b7f91ac…
1 active layer · 6 terminal outcomes
▼ Why this Playbook applies
Firm Mutual NDA Playbook · firm layer · version 3
📄 Mutual NDA — Northstar vendor onboarding
Exact saved DMS version — the review binds to this version’s hash, not “the latest.”
▾ Confidentiality Survival🗎 Missingmedium risk · firm policy
A required provision was not located in the reviewed text.
Approved language
The confidentiality and use restrictions survive for five years after disclosure; trade secrets remain protected for so long as they qualify as trade secrets under applicable law.
Propose policy changeDismiss with reason
▾ Permitted Use and Disclosure🗎 MissingRED LINEhigh risk
Approved language
The receiving party may use Confidential Information solely for the Purpose and may disclose it only to representatives who need to know it for the Purpose and are bound by confidentiality obligations at least as protective as this Agreement.
EscalatePropose policy changeDismiss with reason
Limits and non-applicable rules · 3
nda.confidential_information.definition? Needs factsinformational risk
Finalize immutable review receipt
The problem
Every firm has positions it always takes, language it always rejects, and thresholds that demand a partner — but that judgment lives in senior lawyers' heads and old redlines, applied from memory, and lost when people leave.
The firm’s judgment, operationalized
Reviewed. Codified. Mapped. Governed. Proposed. Scoped.
Follow the firm’s positions from a document review back to the control plane that governs them — every screen below is the real product.
01 · Reviewed
The playbook reads the document — and shows its receipts.
Inside EdgeDocs, one click applies the exact active firm, practice, client, and matter policy layers to the saved version. Every rule lands as a terminal outcome: a missing required provision arrives with the approved language ready to apply, a red line arrives with an escalation path, and the whole review finalizes into an immutable receipt naming the playbook version that governed.
The document surface it lives in →Legal Playbook Review⟳ Run again
Applies the exact active firm, practice, client, and Matter policy layers to this saved version.
Complete coverage receipte42b7f91ac…
1 active layer · 6 terminal outcomes
▼ Why this Playbook applies
Firm Mutual NDA Playbook · firm layer · version 3
📄 Mutual NDA — Northstar vendor onboarding
Exact saved DMS version — the review binds to this version’s hash, not “the latest.”
▾ Confidentiality Survival🗎 Missingmedium risk · firm policy
A required provision was not located in the reviewed text.
Approved language
The confidentiality and use restrictions survive for five years after disclosure; trade secrets remain protected for so long as they qualify as trade secrets under applicable law.
Propose policy changeDismiss with reason
▾ Permitted Use and Disclosure🗎 MissingRED LINEhigh risk
Approved language
The receiving party may use Confidential Information solely for the Purpose and may disclose it only to representatives who need to know it for the Purpose and are bound by confidentiality obligations at least as protective as this Agreement.
EscalatePropose policy changeDismiss with reason
Limits and non-applicable rules · 3
nda.confidential_information.definition? Needs factsinformational risk
Finalize immutable review receipt
02 · Codified
A rule is judgment with structure.
Each rule carries a preferred position, the approved language verbatim, a risk classification, required and red-line flags, deterministic applicability facts, and match phrases that locate the governed subject without deciding the outcome. Institutional judgment, written once, applied everywhere.
‹ Legal Playbook library
Firm Mutual NDA PlaybookActiveSuspend⧉ Create successor⬇ JSON⬇ CSV
Starter positions for recurring bilateral confidentiality agreements. ContractFirmcontracts.mutual.nda
Rule title
Definition of Confidential InformationRule key
nda.confidential_information.definitionRisk
Medium ▾Source status
Attested ▾☑ Required ☐ Red linePreferred position
Protect non-public information disclosed in any form, subject to customary exclusions.
Approved preferred language
“Confidential Information” means non-public information disclosed by or on behalf of a party in any form that is marked confidential or reasonably should be understood to be confidential, excluding information that the receiving party can demonstrate is public without breach, previously known without restriction, independently developed, or rightfully received from a third party.
Applicability
Add deterministic facts that must be true before this rule applies.
Clause or issue match phrases
confidential information
definition of confidential information
One deterministic phrase per line. These locate the governed subject; they do not decide the outcome by themselves.
03 · Mapped
The whole playbook on one screen.
The matrix shows every rule with its risk, preferred position, ranked fallbacks, red-line status, and attested sources — the view a practice group argues over in a conference room, now the view the system actually enforces.
‹ Legal Playbook library
Firm Mutual NDA PlaybookActiveSuspend⧉ Create successor⬇ JSON⬇ CSV
Starter positions for recurring bilateral confidentiality agreements. ContractFirmcontracts.mutual.nda
nda.confidential_information.definitionMediumProtect non-public information disclosed in any form, subject to customary exclusions.Approved fallbackNo1 · Attested
nda.use.disclosureHighLimit use to the stated purpose and disclosure to need-to-know representatives under equivalent duties.NoneYes1 · Attested
nda.term.survivalMediumUse a five-year survival period, with trade secrets protected while legally qualifying.Approved fallbackNo1 · Attested
The whole playbook, one screen: every rule with its risk, its preferred position, its ranked fallbacks, and whether it is a red line — each backed by an attested source record.
04 · Governed
Maker-checker, hashed, immutable.
Author, review, approve, publish, and activate are separate capabilities. A published version is immutable — content-hashed and rule-set-hashed — and change happens through successor versions with effective dates. The approval record shows who attested to what, when. The version that governed any past review is reconstructible forever.
‹ Legal Playbook library
Firm Mutual NDA PlaybookActiveSuspend⧉ Create successor⬇ JSON⬇ CSV
Starter positions for recurring bilateral confidentiality agreements. ContractFirmcontracts.mutual.nda
Version
3Rules
3Content hash
7a91c24de8…44b2Rule-set hash
2fd08a31bc…91e7Published
8/3/2026, 11:03 PMEffective from
On activationPublished versions never change. Amendments become successor versions with their own review — the version that governed any past review is reconstructible forever.
Adopted EdgeLex NDA starter positions; conformance test passed. — M. Chen
Rules unchanged from the adopted pack; risk classifications confirmed. — T. Okafor
Activation of the firm NDA baseline. — T. Okafor
05 · Proposed
AI proposes. It can never approve.
Describe a policy change in ordinary legal language and Lex structures one bounded proposal from the current version — with the governance boundary in writing: version hashes bound to the proposal, no tools available, and a lawyer must accept it into a draft and complete normal review. The firm's judgment stays the firm's.
The authority layer underneath →‹ Legal Playbook library
Firm Mutual NDA PlaybookActiveSuspend⧉ Create successor⬇ JSON⬇ CSV
Starter positions for recurring bilateral confidentiality agreements. ContractFirmcontracts.mutual.nda
Use ordinary legal language. Lex will structure one bounded change proposal from this version. It cannot edit, approve, publish, or activate the Playbook.
For SaaS agreements, our normal position is a mutual liability cap at fees paid in the prior 12 months. Add a fallback at 2x fees and treat uncapped indirect damages as a red line.
✦ Create proposal
- Current-version hashes are bound to the proposal.
- No DMS, email, calendar, task, or web tools are available.
- A lawyer must accept the proposal into a draft and complete normal review.
06 · Scoped
Firm, practice, client, matter — resolved deterministically.
Playbooks are owned at every level of the practice, and overlay resolution picks the exact rules that govern each piece of work — a client's special instructions ride on top of the firm baseline. The library states the boundary in its own chrome: AI may propose drafts and changes; it cannot approve or activate policy.
The evidence that improves it →⚖ Governance Control Plane
Legal Playbooks+ New Legal Playbook
Turn firm judgment into scoped, versioned, testable policy. Active versions are resolved deterministically in EdgeDocs, Word, and governed Legal Graph workflows.
Visible lineages
14Your authority
Activate · Apply Document Change · Approve · Audit · Author · Consume · Propose Change · Publish · Review · Suspend
✦ AI boundary
AI may propose drafts and changes. It cannot approve or activate policy.
Firm Mutual NDA PlaybookContractFirmUpdated 8/3/2026
Starter positions for recurring bilateral confidentiality agreements.
contracts.mutual.nda
SaaS MSA PlaybookContractFirmUpdated 8/3/2026
Liability caps, indemnity posture, and data-protection positions for vendor SaaS paper.
contracts.saas.msa
Litigation Case AssessmentLitigationPracticeUpdated 8/3/2026
Guidance standards for early case assessment and settlement-authority framing.
litigation.case-assessment
Delgado Foods — NDA overlayContractClientUpdated 8/3/2026
Client-specific instructions layered over the firm NDA baseline.
client.delgado.nda-overlay
The difference
Judgment you can cite.
Other tools call a prompt a playbook. Here a playbook is governed institutional knowledge — versioned, hashed, maker-checker approved — and every application of it is receipt-bound to the exact version and rules that governed. When a client asks why the firm took a position, the answer is a record, not a recollection.
How firm knowledge compounds →Immutable versions
Published playbooks are content-hashed and never change — amendments are successors with their own review.
Receipt-bound
Every review finalizes into an immutable receipt naming the version, layers, and outcomes that governed.
AI proposes only
Lex drafts bounded change proposals; approval, publication, and activation stay human, always.
Capabilities
What it does
Institutional judgment, structured
Preferred clauses and positions, ranked fallback language, red lines and prohibited positions, risk classifications, escalation and approval conditions, applicability and exception rules — authored as structured rules, not prose in a memo.
Maker-checker lifecycle
Author, review, approve, publish, and activate are separate capabilities held by separate people. Published versions are immutable; change happens through successor versions with effective dates, suspension, and retirement — never silent edits.
Firm to matter, resolved
Playbooks are owned at firm, practice-group, client-team, or matter level, and overlay resolution picks the exact rules that govern each piece of work — a client's special instructions ride on top of the firm baseline.
Review with receipts
Exact-version document review in EdgeDocs (DOCX and PDF) and Microsoft Word: every rule lands as a terminal outcome on an exact span, with approved language ready to apply, lawyer decisions, escalation — and an immutable application receipt naming the playbook version that governed.
AI applies — never amends
Lex and the execution graphs draft proposals, apply approved playbooks, test coverage, and recommend changes. They can never approve, publish, activate, waive, or silently amend a rule. The firm's judgment stays the firm's.
Starter packs and the evidence loop
Six draft-only starter packs — Mutual NDA, SaaS MSA, Vendor Services, Litigation Case Assessment, Intake Conflicts, Compliance Investigation — and Clause Benchmark evidence feeding reviewed change proposals, so the playbook improves on proof, not vibes.
In your control
Playbooks are the firm's normative knowledge: published versions are immutable, every application is receipt-bound to the exact version and rules that governed it, and no AI pathway can approve or alter a rule.
Related
Works with
EdgeDocs
Native document drafting and a full DMS: versioning, redlines, clause library, e-signature with an evidence trail, and freeze-on-signature.
Clause Benchmark
Source-grounded clause observations, lawyer-approved standards, and benchmarks built from your own negotiation history — not a vendor's market data.
Lex AI & Agents
Lex isn't one application among many. It's the horizontal layer connecting matters, documents, email, messages, meetings, deadlines, and billing — grounded in your data, gated by your approvals.
See EdgeLex on your own terms.
We'll walk through self-hosting, model control, and your firm's workflows.