The Firewall — Earth Credits vs. Benefit Units

This is the architectural firewall against securities characterization. It must be visible at every layer. If a future Landseed staffer cannot tell the difference between a benefit unit and an Earth Credit at a glance, the architecture has failed.

The two things, side by side

Earth Credits	DAO/LLC Benefit Units
Commodity	Governance position
Tradeable	Non-transferable except by succession
Issued by Landseed registry (Layer 3)	Issued by Layer 2 wrapper at formation
Sold to anyone	Held by named real-world stakeholders only
Listed on Exchange (when built)	Never listed
Retired by holder for compliance/claim	Held until succession
Underlying value: methodology score	Underlying right: vote, distribute, ratify
Counterparty: any buyer	Counterparty: only existing members
Regulatory bucket: commodity (CFTC if derivatives)	Regulatory bucket: not a security (perimeter holds)
Pricing: open market	”Pricing”: none — positions don’t have price
Liquidity: market-driven	Liquidity: scheduled distributions only
Holders’ role: passive ownership	Holders’ role: stewardship and governance

Why this distinction is structurally necessary

If benefit units are equivalent to credit positions:

• Benefit units = securities
• Architecture is registered securities offering
• Per-property isolation breaks down because positions are functionally tradeable
• Compliance overhead increases dramatically

The architecture’s regulatory viability depends on this distinction holding visibly at every layer.

The flow — credits and positions on parallel tracks

LAYER 3: MEASUREMENT
EC-M-1.1 attestation generated by methodology
                │
                ▼
        attestation receipt issued
                │
        ┌───────┴───────┐
        │               │
        ▼               ▼

CREDITS TRACK             POSITIONS TRACK
                          
Landseed registry          Wrapper LLC at formation
issues Earth Credits       issues benefit units
        │                  to named stakeholders
        │                          │
        ▼                          │
   Sold to buyers                  │
        │                          │
   ┌────┴─────┐                    │
   │          │                    │
   ▼          ▼                    │
 Direct    Exchange                │
        │   │                      │
        ▼   ▼                      │
  Proceeds flow into                │
       LLC treasury  ◄──────────────┘
                                governs
                                LLC operations

Two parallel tracks. Both originate from the methodology layer. They never cross.

How the firewall is enforced

At the smart contract layer (Tier 2)

• Smart contract has no credit-issuance interface (registry handles credits, not the DAO)
• Smart contract enforces non-transferability of benefit units
• Smart contract treasury receives revenue (proceeds flow IN); does not transact credits

At the operating-agreement layer (Tier 1 and Tier 2)

• Operating agreement specifies that members hold “membership interests,” not “credit positions”
• Operating agreement explicitly states the LLC does not issue Earth Credits
• Operating agreement prohibits transferable membership

At the registry layer

• Registry issues credits to credit accounts (held by Landseed registry, then transferred to buyers)
• Registry does not issue credits to LLC members (members are not buyers)
• Registry’s records distinguish the two clearly

At the operational layer

• Distributions flow as cash (Bright Line 6); LLC does not transfer credits to members
• Members who want credits buy them on the open market (separate transaction, not LLC-mediated)
• Communications consistently distinguish “credit” from “membership”

What if a member wants liquidity

A real concern: if members can’t sell their positions, how do they get liquidity?

Answer: through scheduled distributions, not through position sales.

Scenario	Resolution
Member needs ongoing income	Distributions (annual or quarterly cash)
Member needs lump sum	Wait for accumulated distributions; if still insufficient, position succession (e.g., sale of underlying property triggers succession with cash settlement per operating agreement)
Member exits the property relationship	Operating-agreement succession provisions; cash settlement of accumulated distributions
Member wants exposure to Earth Credit price appreciation	Buy Earth Credits on the open market (separate transaction)

The architecture provides liquidity through ordinary partnership-style distributions, not through speculative-market position sales. This is consistent with the architecture’s framing as stewardship vehicle, not investment vehicle.

Common confusions to avoid

”The DAO holds credits”

Wrong. The DAO does not hold credits. The DAO holds cash from credit sales (treasury). Credits are issued by the registry, sold to buyers, and the proceeds flow into the DAO’s treasury.

”Members own a piece of the credits”

Wrong. Members own governance positions. Through governance, they have rights to receive distributions of revenue (which itself comes from credit sales). They don’t own credits or fractional credit positions.

”The DAO can issue more positions to attract investment”

Wrong. Bright Line 2 prohibits public offering; Bright Line 1 prohibits transferability. New beneficiary admissions require existing-member consent and are tied to property relationship, not investment.

”If the property’s credit revenue increases, members’ positions become more valuable”

This is partially correct but misleading. Distributions become larger when revenue is larger. Positions themselves are non-transferable so don’t have market value. A member’s economic interest is the future stream of distributions, which is governed by their share, not by position-level pricing.

This distinction matters for Howey analysis (Element 3 — expectation of profit). The “profit” expectation is for distributions, framed as condition-derived revenue, not for capital appreciation of the position itself.

”Earth Credits and benefit units are conceptually similar — both relate to ecological condition”

True at the highest level — both relate to the property’s ecological condition. But operationally and legally they are different categories:

• Credits = certified attestations of measured condition (commodity)
• Positions = governance roles in the entity holding the VECR (governance)

Conflating them collapses the architecture.

Operational discipline checklist

For any communication, deployment, or operational action, verify:

• Is the communication about credits or positions? Don’t mix.
• If about positions, are we framing them as governance, not investment?
• If about credits, are we acknowledging they’re commodities sold to buyers?
• Does the LLC’s books and records distinguish “treasury revenue from credit sales” from any “credit holdings”?
• Does the smart contract (Tier 2) have any interface that could be misread as credit issuance?
• Does the operating agreement use consistent language?

If any answer is unclear, fix it. Sloppy language at this layer compromises the architecture.

Why the firewall matters for first-pilot communications

For the first pilot deployment, every external communication is an opportunity to either reinforce or weaken the firewall. Recommended discipline:

• All marketing copy reviewed by Landseed compliance
• Captain Landseed content reviewed for the firewall
• Landowner-facing materials use plain-English distinctions
• Investor-facing materials (for the Institutional Fund, when built) explicitly clarify that the Fund buys credits, not positions

A stack of well-framed early communications builds the firewall as a public norm. A stack of sloppy early communications creates ambiguity that’s hard to retract.

Maintenance

The firewall is the single most important architectural feature for regulatory viability. It is reviewed:

• Per pre-deployment self-check (07-pre-deployment-self-check.md)
• Annually in compliance review
• Whenever a new template, coalition entity, or operational practice is introduced
• Whenever Landseed PBC’s communications strategy is updated

If the firewall ever appears to weaken, halt-and-escalate.