Architecture · Methodology Foundation
The Methodology Foundation
Separate legal entity holding the methodology IP under irrevocable open-source license — continuity-safe if Landseed PBC fails.
What this is
A separate legal entity (proposed: Landseed Methodology Foundation, or equivalent name) that holds the methodology IP under irrevocable open-source license. It is the architectural mechanism that makes the methodology — and therefore Earth Credits as a commodity — independent of any specific corporate entity, including Landseed PBC.
This document specifies what the Foundation is, why it’s necessary, and how it’s formed and governed.
Why this is necessary
Currently:
- Methodology (EC-M-1.1) is developed by Landseed PBC
- Registry function (Earth Credit issuance) is operated by Landseed PBC
- Brand and intellectual property are owned by Landseed PBC
If Landseed PBC fails as a corporation (Test 16 in 06-risks/):
- Methodology stewardship is interrupted
- Registry function may stop issuing credits
- Existing deployed DAOs/LLCs hold valid NRD-lites and continue, but cannot issue new credits
- The architecture becomes an orphan
The architecture’s mitigation has been “form a Methodology Foundation that holds the IP irrevocably.” But until this document, that was 2 sentences. This document specifies what it actually is.
What the Foundation does
| Function | Specification |
|---|---|
| Holds methodology IP | Open-source license to EC-M-1.1 and successor versions; perpetual, irrevocable, no royalties |
| Holds registry function authority | The registry function (per 05-interfaces/04-registry-function-specification.md) operates under Foundation authority once formed |
| Holds brand IP | ”Earth Credits” mark, “EC-M” designation, “Landseed methodology” framing; licensed to Landseed PBC and successor entities |
| Maintains methodology archives | The three-archive commitment (Landseed systems + institutional + decentralized) is fulfilled by the Foundation |
| Governs methodology evolution | New methodology versions (EC-M-2.0, EC-M-3.0) are developed and approved by Foundation governance |
| Provides continuity | If Landseed PBC fails or transitions, Foundation continues; methodology and registry continue |
Foundation legal structure
| Aspect | Specification |
|---|---|
| Form | Vermont nonprofit corporation OR 501(c)(3) public charity OR Vermont DAO LLC (depending on which best fits) |
| Founders | Landseed PBC + initial methodology stewards + 2–3 independent directors |
| Tax status | Aim for 501(c)(3) public charity (tax-exempt; donations deductible; aligns with conservation purpose) |
| Domicile | Vermont (continuity with conservation-easement ecosystem); could be Delaware if tax/structural advantages |
| Existence | Perpetual; not subject to Landseed PBC’s corporate continuity |
Why Vermont (or Delaware) and not Marshall Islands
The Foundation must have institutional credibility. Marshall Islands’ DAO LLC structure is operationally functional but lacks the institutional credibility that conservation foundations command. Vermont (or Delaware) nonprofit corporation:
- Recognized institutional structure
- IRS 501(c)(3) eligibility
- Banking access
- Boards of directors are familiar to outside reviewers
This is one of the few places the architecture deviates from “default Marshall Islands for non-US.” The Foundation is US-based for institutional credibility.
Foundation governance
Board composition (initial)
7 members:
| Seat | Role | Term | Successor |
|---|---|---|---|
| Methodology Steward 1 (Alex) | Methodology authority; primary architect | 5 years | Per Foundation bylaws |
| Methodology Steward 2 (TBD; co-author of EC-M) | Methodology authority | 5 years | Per Foundation bylaws |
| Methodology Steward 3 (TBD) | Methodology authority | 5 years | Per Foundation bylaws |
| Independent Ecologist 1 | Scientific validation | 4 years | Foundation board appoints |
| Independent Ecologist 2 | Scientific validation | 4 years | Foundation board appoints |
| Independent Finance/Audit | Fiduciary oversight | 3 years | Foundation board appoints |
| Landseed PBC Representative | Corporate continuity | 3 years | Landseed PBC appoints |
7 seats balances methodology expertise (3) with independent oversight (3) with PBC continuity (1). PBC representative does not have controlling vote.
Governance procedures
| Decision class | Threshold |
|---|---|
| Methodology version adoption | Methodology stewards majority + audit committee non-objection |
| Foundation amendment | Board supermajority (5 of 7) |
| Officer appointments | Board majority |
| Methodology IP licensing changes | Board supermajority |
| Registry function authority delegation | Board majority |
| Annual budget | Board majority |
| Any change affecting Earth Credit holders | Public notice + 60-day comment period |
These are designed so:
- Methodology can evolve through stewardship
- Independent oversight prevents capture
- Landseed PBC has voice but not control
- Public has visibility into governance
Methodology IP licensing
The license terms:
| Term | Specification |
|---|---|
| Scope | EC-M-1.1 and all successor versions; methodology documents; calculator code; reference data |
| License | Open-source (CC-BY-4.0 or equivalent); perpetual; irrevocable |
| Royalty | None |
| Successor restrictions | Foundation can update methodology; cannot restrict open-source nature; cannot revoke license |
| Use | Anyone (including Landseed PBC’s competitors or successor entities) can use the methodology under license |
| Attribution | Required (“EC-M-1.1 by Landseed Methodology Foundation; original architecture by Landseed PBC”) |
Why open-source: a closed-source methodology dies with its corporate owner. Open-source methodology survives any specific entity. This is the mechanism for continuity.
Why irrevocable: even if Foundation board wishes to change license, they cannot remove what’s already published. This protects against future board capture.
Why no royalty: royalty-bearing IP is harder to license to successors and competitors. The Foundation’s revenue comes from registry service fees and (potentially) methodology consulting, not from IP royalties.
Foundation revenue and operations
Revenue sources
| Source | Description |
|---|---|
| Donations and grants | Conservation foundations; methodology research grants; mission-aligned philanthropy |
| Registry service fees | Per-issuance and per-sale fees (per 05-interfaces/04-registry-function-specification.md); split with Landseed PBC for first 3 years; Foundation alone thereafter |
| Methodology consulting | If sovereign programs adopt EC-M, Foundation can consult for fees |
| Endowment income | Long-term: an endowment funded by initial donations + accumulated registry fees |
Operating budget (proposed)
| Year | Operating cost |
|---|---|
| Year 1 (formation) | $200k–$400k |
| Year 2 (operational) | $400k–$700k |
| Year 3 (growth) | $600k–$1M |
| Year 5+ (mature) | $1M–$2M |
These are total Foundation costs, not Landseed PBC’s costs. The Foundation funds itself; it is not a Landseed PBC cost center.
Formation timeline
| Phase | Time | Notes |
|---|---|---|
| Phase 1 — Initial Articles + Bylaws | 2–4 months | Outside counsel drafts; Landseed PBC + initial directors review |
| Phase 2 — IRS 501(c)(3) application | 8–18 months | IRS Form 1023; can take 6–12+ months |
| Phase 3 — Initial board formation | 1–2 months parallel | Identify and engage directors; first board meeting |
| Phase 4 — Methodology IP transfer | 2–3 months | License agreement; assignment of registered marks; methodology documents repositoried |
| Phase 5 — Registry function delegation | 3–6 months | Operational handoff from Landseed PBC’s internal function to Foundation; multi-key signoff established |
| Phase 6 — Independent operations | Ongoing | Foundation operates independently; quarterly reports to public |
Total formation time: 12–18 months from decision to fully independent operations.
This means: starting Foundation formation in parallel with first-pilot deployment (Year 1 of architecture execution) targets full Foundation independence by Year 2.
What Foundation independence achieves
The Foundation is fully independent when:
- Methodology IP is licensed (irrevocably)
- Registry function operates under Foundation authority
- Board is operational and has held governance meetings
- Foundation has its own banking, treasury, operational systems
- Foundation has independent audit and compliance
- Independent directors are non-Landseed-PBC affiliates
At that point: even if Landseed PBC failed tomorrow, the Foundation continues, methodology continues, registry continues, Earth Credits continue to be valid commodities.
What this does not do
For clarity:
- Does not provide continuity if Foundation also fails. A double-failure scenario (Landseed PBC + Foundation both fail) is not architecturally addressed. Mitigation: Foundation is structured for institutional durability (board diversity, endowment, etc.).
- Does not eliminate Landseed PBC’s role. Landseed PBC remains the BD function, the public-facing brand, the Captain Landseed operator, the developer of templates and frameworks. The Foundation just owns the methodology IP and registry function.
- Does not make methodology immutable. Methodology can evolve through Foundation governance; it just cannot be revoked from the public.
- Does not affect existing deployed DAOs/LLCs. Their NRD-lites continue to reference whatever methodology version was current at execution; the Foundation just maintains the methodology infrastructure.
Critical architectural property
The Foundation is the architecture’s continuity mechanism. Without it:
- Landseed PBC failure = methodology orphan
- Methodology orphan = Earth Credits become uncertain commodities
- Uncertain commodities = trust collapses
- Trust collapse = architecture fails
With it:
- Landseed PBC failure = methodology continues under Foundation
- Earth Credits remain valid commodities
- Existing deployments remain operational
- New deployments continue under Foundation/registry
The Methodology Foundation is the architecture’s most important continuity mechanism, and it is currently unbuilt. Forming it is a precondition for scaled deployment.
Decision points
| Decision | Owner | Status | When |
|---|---|---|---|
| Form Foundation | Alex + the co-architect + Landseed PBC board | Recommended | Year 1 of architecture execution (parallel with first pilot) |
| Foundation jurisdiction | Counsel | Vermont (recommended) or Delaware | Foundation formation |
| Foundation structure (501c3 vs nonprofit corp vs DAO LLC) | Counsel + tax counsel | 501(c)(3) (recommended) | Foundation formation |
| Initial board composition | Alex + the co-architect + Methodology stewards | Per board specification above | Foundation formation |
| Methodology IP transfer terms | Counsel + Methodology stewards | Per license terms above | After Foundation formed |
| Registry function delegation | Landseed PBC + Foundation | Per registry spec | Year 2 |
co-architect review of Foundation
For the co-architect's pressure-testing:
- The Foundation is the answer to “what happens if Landseed PBC fails?” — a real question for any 99-year architecture
- Foundation is institutionally credible (Vermont nonprofit; well-recognized structure)
- Foundation governance balances methodology expertise with independent oversight
- Foundation is well-funded through registry fees + donations
- Foundation independence is achieved through irrevocable open-source licensing
- Methodology IP is open-source (anti-rentier; methodology spreads, not capture)
These should be reassuring to the co-architect (his institutional instincts respect this kind of structure). The unknowns the co-architect may surface:
- Specific Foundation jurisdiction (Vermont vs. Delaware vs. other)
- Specific board composition for stewards (who, exactly?)
- Specific tax structure (501(c)(3) vs. other)
- Funding plan for Foundation Year 1 operations
- Timeline of Foundation independence (Year 2 might be ambitious)
These are details that emerge during Foundation formation, not architecture-level questions.
Cross-references
- Registry function:
05-interfaces/04-registry-function-specification.md - Test 16 (Landseed PBC fails):
06-risks/02-pressure-tests.md - Methodology incorporation:
01-nrd-lite/05-methodology-incorporation.md - Methodology archival commitment:
01-nrd-lite/05-methodology-incorporation.md(3-archive commitment + paper backup)