Perimeter
Eight bright lines
Eight rules the architecture cannot cross without becoming a security. Each is a constraint, a justification, and a test for whether a proposed change preserves the perimeter.
Every bright line below is an architectural commitment. Crossing one moves the architecture into US securities territory or its rough analog elsewhere. Several of the lines are tested independently in Pressure tests.
The Eight Bright Lines
These rules govern every template, every wrapper entity, every coalition entity, every operational procedure. They are non-negotiable. Crossing any one creates regulatory exposure. They are enforced at three layers: smart contract code (Tier 2 templates), wrapper-entity operating documents, and Landseed operational procedures.
The lines
| # | Bright line | What this prevents | Enforcement |
|---|---|---|---|
| 1 | No transferable benefit units. Benefit units cannot be sold, gifted to non-stakeholders, or pledged as collateral. They transfer only via DAO-approved succession (death, sale of underlying property, replacement of an institutional seat-holder). | Secondary-market characteristic that regulators treat as evidence of a security | Smart contract enforces non-transferability technically (Tier 2); operating agreement enforces legally (Tier 1 and Tier 2); member onboarding includes explicit acknowledgment |
| 2 | No public offering. No public marketing of benefit units. No solicitation. No “join the property.” DAO membership is closed at template deployment; subsequent additions require existing-beneficiary consent. | Public-offering element under multiple regulatory regimes | Membership protocols restrict admission; marketing protocols prohibit position-related public communications |
| 3 | No pooled treasury. Each property’s DAO has its own treasury, isolated from every other DAO. Treasury cannot be lent to another DAO. Treasury cannot pool with another DAO for any purpose. | Horizontal common-enterprise prong of Howey | Per-property isolation at legal-entity level; smart contracts (Tier 2) have no cross-DAO function surfaces |
| 4 | No fund-of-DAOs. Landseed does not create a vehicle that holds multiple DAOs’ benefit units. The Institutional Fund buys Earth Credits (a commodity); it does not buy DAO positions or have governance rights in any DAO. | Fund structure that pools investor exposure across properties | Coalition entity charters; Fund offering documents specify credit-only acquisition |
| 5 | Earth Credits are issued by the registry, not the DAO. The DAO does not issue Earth Credits. Landseed’s registry function issues credits; buyers purchase from the registry; proceeds flow to DAOs as revenue. | Conflation of governance positions with commodity issuance | Registry operational separation; smart contract (Tier 2) does not have credit-issuance interfaces |
| 6 | Distributions are cash by default. Until securities counsel confirms in-kind credit distribution does not create a securities-transaction characterization (Q1 in 06-risks/), distributions are cash only. If a member wishes to convert their cash distribution to Earth Credits, that is a separate, post-distribution transaction the member executes themselves. Benefit unit count is fixed at deployment for the duration of each member’s tenure. | Token-issuance characteristic that regulators treat as evidence of a security | Economics module’s distribution mechanics; treasury operations route only cash |
| 7 | Landseed never holds a controlling benefit unit position. Landseed has a seat in every DAO with limited scope (methodology decisions and guardian veto). Landseed does not hold a controlling stake. | Appearance of Landseed controlling the entity that holds the property right | Beneficiary registry composition; voting weight rules in Governance module |
| 8 | No automated trading or yield products on benefit units. Benefit units are not “DeFi-able.” No staking, no lending, no liquidity pools, no automated market making. The smart contract does not expose interfaces that DeFi protocols could connect to. | Speculative-financial-product characterization | Smart contract design (no DeFi-compatible interfaces); operating agreement prohibits yield products |
How each line is tested
Each bright line maps to a specific question in 07-pre-deployment-self-check.md. Before any deployment goes live, every question must be answered “no” (i.e., the deployment does not violate any line).
Why eight, not more or fewer
Eight is empirical, not principled. They are the lines that, if crossed, create the most likely regulatory failure modes:
- 1, 2 → defeat secondary-market and public-offering elements
- 3, 4 → defeat horizontal common enterprise
- 5, 6 → keep credits and positions distinct
- 7 → prevent Landseed-control characterization
- 8 → prevent speculative-financial-product characterization
Adding more would create overlap. Removing any opens a specific failure mode.
What the bright lines collectively defend
Together, the eight bright lines defend the architecture against:
| Threat | Defense |
|---|---|
| US securities (SEC) classification of benefit units | All eight lines collectively |
| US commodity (CFTC) classification of benefit units | Lines 1, 6, 8 |
| Foreign securities classification (Argentina CNV, etc.) | All eight lines collectively |
| Public-offering characterization in any jurisdiction | Lines 1, 2 |
| Fund characterization | Lines 3, 4 |
| Investment-contract characterization | All eight lines collectively |
What the bright lines do NOT defend against
For clarity:
- They do not defend against a regulator who simply decides to characterize the architecture differently regardless of the structure. Regulators have discretion.
- They do not defend against an architectural change that violates one of them — i.e., they require ongoing operational discipline.
- They do not defend against speculative landowner litigation, which is a different category of risk.
- They do not defend against criminal prosecution for fraud (not a perimeter concern; the methodology and registry must operate honestly).
Maintenance
The bright lines are amended only:
- In response to regulatory guidance affecting any line
- In response to court decisions changing the underlying analysis
- In response to a target jurisdiction’s regulatory regime materially changing
- In response to a coalition entity proposal that requires new perimeter analysis
The principle does not move: governance positions and commodities are different things, and the architecture must keep them visibly different at every layer.