Skip to content
Landseed NRD-DAO Atlas
← NRD-Lite (Layer 1)

NRD-Lite · Drafting strategy

Drafting Strategy

The order of clauses, the language to avoid, and what counsel must sign on.

How to actually produce per-jurisdiction NRD-lite templates. This document is the workflow.

The skeleton

Every per-jurisdiction template hews to the same skeleton, in this order:

1.  Recitals (parties, purposes, prior agreements)
2.  Granting Clause
3.  Definition of the Verified Ecological Condition Right (VECR)
4.  Term
5.  Identification of the Holder (the wrapper entity)
6.  Measurement Standing
7.  Transfer Covenants (including Partial Conveyances)
8.  Reversion
9.  Enforcement Floor
10. Coordination Clause (where applicable)
11. Choice of Law and Forum
12. General Provisions (severability, integration, notices, definitions)
13. Signatures (parties, notarization, witness as required)
14. Exhibits:
    - Exhibit A: Legal description of the property
    - Exhibit B: Methodology reference (with version pin and hash)
    - Exhibit C: Methodology summary (paper backup, 5–10 pages)
    - Exhibit D: Wrapper entity formation documents (informational, not incorporated)

Each per-jurisdiction template is its own document. Each section is drafted to satisfy the local jurisdiction’s category, recording, and enforcement requirements.

The skeleton is uniform; the expression of each section varies per jurisdiction.

The drafting sequence

For each jurisdiction:

Step 1 — Counsel selection

Engage qualified property counsel with:

  • Conservation-instrument experience (in-gross easements, environmental servitudes)
  • Familiarity with the jurisdiction’s recording and registration mechanics
  • Comfort with novel structures (the VECR is novel even when mapped to existing categories)
  • Capacity for ongoing advisory (questions will arise during deployment)

For jurisdictions where indigenous co-governance is in scope (Template C deployments), additionally engage indigenous-rights counsel.

Step 2 — Property-category mapping

Counsel identifies which existing category in the jurisdiction the VECR maps to:

  • USA: in-gross conservation easement under state act
  • Argentina: provincial servidumbre ecológica or afectación administrativa
  • Ecuador: servidumbre ecológica under Ley Forestal
  • Bangladesh: 99-year registered lease with environmental covenants
  • Madagascar: bail emphytéotique (private) or convention de gestion (community)

Counsel produces a written category-mapping memorandum documenting:

  • The chosen category
  • The statutory basis
  • Any constraints the category imposes
  • Any drafting language idiosyncratic to the category

The memorandum is a Landseed-internal document. Future per-jurisdiction template revisions reference it.

Step 3 — Skeleton instantiation

Counsel drafts each section to the local category’s requirements:

  • Element 1 (granting clause): in the local category’s voice
  • Element 2 (definition): the VECR’s substance, expressed in local terminology
  • Element 3 (term): with the local statutory cap if any
  • Element 4 (holder): formatted to satisfy local “qualified holder” requirements (or with affiliated 501(c)(3) workaround)
  • Etc.

The methodology incorporation, transfer covenants, partial-conveyance handling, and enforcement floor language stay substantively uniform across jurisdictions, just expressed in local form.

Step 4 — Annotated commentary

Counsel produces an internal annotated commentary alongside the deed template. The commentary explains, section by section:

  • What the section is doing
  • Why this language was chosen over alternatives
  • What was considered and rejected
  • Any local-jurisdiction caveats

The commentary is a Landseed-internal asset. Future Landseed staff can read the commentary to understand the deed’s logic without reverse-engineering the drafting decisions.

Step 5 — Internal review

the co-architect + Landseed counsel review the draft template against:

  • The 11 load-bearing elements (02-load-bearing-elements.md)
  • The 5 legal-floor tests (04-legal-floor.md)
  • The methodology incorporation requirements (05-methodology-incorporation.md)
  • The architecture’s binding principles (00-foundations/03-binding-principles.md)

Internal review approves the template for test-recording.

Step 6 — Test recording

Where possible, file a test instrument with the recording office to confirm acceptance before live use:

  • Paper formality (page size, font, signature pages)
  • Substantive acceptability (the office accepts the document type)
  • Recording fee verified
  • Estimated turnaround time

Some recording offices accept “test deed” filings; others do not. Where they don’t, work directly with office staff to verify acceptability.

Step 7 — Live use

After test recording succeeds, the template is ready for live use. First live deployment in any jurisdiction is treated as a pilot, monitored closely.

What the per-jurisdiction template includes

Each template package includes:

DocumentPurpose
The deed templateThe actual draft with placeholders for property-specific information
The annotated commentaryInternal explanation of drafting decisions
The category-mapping memorandumStatutory basis for the property-right characterization
A landowner-facing explanationPlain-language summary for the kitchen-table conversation
Methodology summary exhibit (paper backup)The 5–10 page printed methodology synopsis
Recording-office requirements checklistLocal filing formalities

What stays uniform across jurisdictions

These remain substantively the same regardless of jurisdiction (only language varies):

These remain customized per jurisdiction:

  • The category designation and granting language
  • Recording mechanics and signatures/notarization
  • Local-court forum selection
  • Wrapper-entity choice (driven by jurisdiction; see 03-jurisdictions/)
  • Reservation for ancestral rights or sovereign considerations (Template C / Template E deployments)

Cost and time per jurisdiction

PhaseTimeCost
Counsel selection2–4 weeks$5k–$15k retainer
Property-category mapping memorandum4–6 weeks$15k–$25k
Skeleton instantiation6–8 weeks$25k–$40k
Annotated commentary2–4 weeks (parallel with skeleton)included in skeleton work
Internal review2–4 weeksminimal additional cost
Test recording2–6 weeks (depends on jurisdiction)$1k–$3k
Total12–16 weeks per jurisdiction$45k–$80k per jurisdiction

These are first-jurisdiction costs. Subsequent properties in the same jurisdiction reuse the template with property-specific information at much lower marginal cost (likely $5k–$15k per property).

Counsel coordination across jurisdictions

When working in multiple jurisdictions in parallel, counsel coordination matters:

  • The category-mapping memoranda are independent per jurisdiction
  • The skeleton structure is uniform (counsel adapts; doesn’t redesign)
  • Cross-jurisdiction issues (e.g., wrapper-entity holding deeds in multiple jurisdictions) require coordinated counsel review

Recommendation: a small Landseed-internal “deed coordination” group reviews each jurisdiction’s drafts against the others to ensure substantive uniformity. This is a 0.25 FTE function.

Drafting discipline

The temptation will be strong, in any given jurisdiction, to add “just in case” clauses that re-create v1.2’s bulk. Counsel’s instinct is to be thorough, which often means over-specifying.

Discipline: every addition beyond the skeleton requires affirmative justification documented in the annotated commentary. “Counsel suggested it” is not justification; “the local recording office requires it” is.

This discipline is what keeps the NRD-lite at 8–15 pages over time. Without it, drafts grow toward 50, 100, 200 pages, and we are back to v1.2.

What success looks like

A successful per-jurisdiction template:

  • Is 8–15 pages
  • Maps clearly to a recognized property category
  • Passes test recording
  • Is comprehensible to a landowner with the kitchen-table summary
  • Is enforceable in local courts
  • Is reusable across multiple properties in the jurisdiction with property-specific information only

If a jurisdiction’s template doesn’t satisfy these, the work isn’t done. The architecture cannot be deployed in that jurisdiction until it does.