Sample · Module M1
Beneficiary-registry sample
Module M1 example — identity, role, weight, share, successor.
This is an illustrative sample. It is not a populated registry for any real Wrapper Entity, and contains no real-world identity, KYC, wallet, or successor data. Do not rely on it for any operational purpose. Real Beneficiary Registries are maintained by Wrapper Entity Managers per 02-governance-templates/02-modules.md § M1, with off-chain KYC custody by Landseed compliance.
This sample reduces the M1 — Beneficiary Registry specification (02-governance-templates/02-modules.md § M1) to structured-document form. It illustrates:
- The columns of a typical Beneficiary Registry
- Three template scenarios (A, B, C) with different stakeholder shapes
- Privacy and KYC discipline
- Successor mechanics in operation
The samples are placeholders. Names, IDs, KYC references, wallet addresses, and percentages are illustrative and bear no relationship to any real person, property, or deployment.
Schema
A Beneficiary Registry is a table with the following columns:
| Column | Description | On-chain (Tier 2)? |
|---|---|---|
| Beneficiary ID | Internal stable identifier for this seat (e.g., MR-001, WP-002). Persists across successions; survives KYC re-verification. | Yes (Tier 2 only) |
| Real-world identity (KYC-confirmed) | Legal name; KYC vendor; KYC reference number; KYC verification date; next-verification due date. Held off-chain by Landseed compliance. | No (off-chain only) |
| Wallet address (or “paper” + designated custodian) | Ethereum-style address controlled by the Beneficiary or their designated custodian. For Beneficiaries with no wallet, “paper” with named custodian. | Yes (Tier 2 only) |
| Voting weight | Per Voting Class (Article III of operating agreement). Typically expressed as a fraction or percentage by Class. | Yes (Tier 2 only) |
| Distribution share | Percentage of Tier 3 (beneficiary distributions) per § 4.1 of operating agreement. Family or sub-group splits are nested. | Yes (Tier 2 only) |
| Membership class | Role: Owner, Family Member, Steward, Co-Steward, Community Council Member, Elder, Cultural Guardian, Methodology Steward (Landseed), Landseed Steward, Foundation Director, etc. | Yes (Tier 2 only) |
| Effective date | Date of admission to the Registry. | Yes (Tier 2 only) |
| Successor designated | Yes/No. If Yes, designated successor’s Beneficiary ID (a placeholder pointing to a future seat) or named successor reference. | Yes (Tier 2 only) |
| Notes | Operational notes (e.g., “spouse holds general POA”; “custodial wallet via Coinbase Prime”; “data sovereignty restrictions per Template C MOU”). | Selected fields on-chain; sensitive notes off-chain |
The on-chain registry (where used in Tier 2) uses opaque pointers for KYC references and wallet addresses; no personally identifiable information is on-chain. The off-chain Landseed-compliance record is the authoritative source for legal identity. (See 02-governance-templates/02-modules.md § M1 KYC discipline.)
Sample 1 — Template A (Solo Landowner)
Wrapper Entity: Maple Ridge Conservation Stewardship LLC (Vermont LLC) Property: Maple Ridge, Town of [TOWN], County of [COUNTY], Vermont Tier: 1 (no on-chain registry; this table is the operating agreement Exhibit A) Effective date of registry: [DATE]
| Beneficiary ID | Real-world identity (KYC ref) | Wallet / custodian | Voting weight (Class 2/4/5/6) | Voting weight (Class 7/8/9) | Distribution share | Membership class | Effective | Successor designated | Notes |
|---|---|---|---|---|---|---|---|---|---|
MR-001 | J. Doe (Persona ref doe-001; verified 2026-04; due 2031-04) | Paper; custodian: Vermont Counsel Trust Account | 80% | 75% | 65% | Owner (primary Landowner) | 2026-04-15 | Yes — MR-001-SUCC-A (designated heir; spouse) | Sole record owner of Maple Ridge; spouse holds general POA in case of incapacity |
MR-002 | M. Doe (Persona ref doe-002; verified 2026-04; due 2031-04) | Paper; custodian: Vermont Counsel Trust Account | 10% | 10% | 15% | Family Member (spouse) | 2026-04-15 | Yes — children of MR-001 and MR-002 jointly | Spouse of MR-001; designated successor of MR-001 |
MR-003 | A. Doe (Persona ref doe-003; verified 2026-04; due 2031-04) | Paper; custodian: Vermont Counsel Trust Account | 5% | 5% | 7% | Family Member (adult child) | 2026-04-15 | No — succession by per-stirpes inheritance | Adult child of MR-001; advisory-only on stewardship matters until family-internal procedure designates active role |
MR-004 | B. Doe (Persona ref doe-004; verified 2026-04; due 2031-04) | Paper; custodian: Vermont Counsel Trust Account | 5% | 5% | 7% | Family Member (adult child) | 2026-04-15 | No — succession by per-stirpes inheritance | Adult child of MR-001 |
MR-005 | Landseed PBC (entity KYC; Persona ref landseed-pbc; verified 2026-01; due 2031-01) | Multi-sig: Landseed compliance officer | Advisory; methodology authority on Class 3; non-objection rights on Class 4/7/8/9 | Non-objection on Class 7/8/9 | 6% (protocol fee paid via Tier 1 of waterfall, not as Class 3 distribution) | Landseed Steward | 2026-04-15 | Per Landseed succession (corporate) | Landseed PBC entity seat; no individual identity; methodology guardian veto active under § 3.7 |
Total Class-2 voting weight: 100%. Total Tier-3 distribution share: 100%. (Tier 3 sums Owner + Family Members: 65% + 15% + 7% + 7% = 94%. The remaining 6% is the Landseed protocol fee, which flows in Tier 1 not Tier 3 — included here for completeness; a real registry would omit Tier-1 entries from a Tier-3 share column.)
Privacy notes (Template A):
- KYC custody: Landseed compliance, Persona-vendor records
- Wallet: paper with Vermont Counsel Trust Account; signature-based disbursement from multi-sig
- No on-chain registry; this table lives in the LLC’s books and records under Operating Agreement Exhibit A
- Family-internal procedures (per-stirpes inheritance, spouse POA) referenced; not detailed on-chain
Sample 2 — Template B (Land Trust with Co-Stewards)
Wrapper Entity: Whitepine Conservation Stewardship LLC (Vermont LLC) Property: Whitepine Tract, [TOWN], [COUNTY], Vermont Tier: 1 (institutional; no on-chain registry) Effective date of registry: [DATE] Note: the holder of fee is the Whitepine Land Trust (a Vermont 501(c)(3) public charity, separately formed); the LLC is the Wrapper Entity. The Land Trust is the “Member” representing the institutional landholder.
| Beneficiary ID | Real-world identity (KYC ref) | Wallet / custodian | Voting weight (Class 2/4/5/6) | Voting weight (Class 7/8/9) | Distribution share | Membership class | Effective | Successor designated | Notes |
|---|---|---|---|---|---|---|---|---|---|
WP-001 | Whitepine Land Trust (entity KYC; Veriff ref wlt-001; verified 2026-03; due 2031-03) | Paper; custodian: Land Trust Treasurer (multi-sig 2-of-3 with two Trust officers) | 60% | 60% | 70% | Owner (institutional Landholder; 501(c)(3)) | 2026-05-01 | Per institutional procedures; if institution merges, successor inherits | Whitepine Land Trust holds fee; LLC holds VECR. Trust is the dominant Member; board-style governance per Article III |
WP-002 | Northeastern Conservation Co-op (entity KYC; Veriff ref ncc-001; verified 2026-03; due 2031-03) | Multi-sig 2-of-2 with two Co-op officers | 15% | 15% | 12% | Co-Steward (institutional partner; conservation expertise) | 2026-05-01 | Per Co-op procedures | Conservation co-op providing forestry expertise; voting on Class 4 (Management Plan) reflects expertise weight |
WP-003 | Vermont Forest Stewards Association (entity KYC; Veriff ref vfsa-001; verified 2026-03; due 2031-03) | Paper; custodian: VFSA Treasurer | 10% | 10% | 8% | Co-Steward (institutional partner; field operations) | 2026-05-01 | Per VFSA procedures | Provides on-the-ground stewardship coordination |
WP-004 | C. Smith (individual; Veriff ref smith-001; verified 2026-03; due 2031-03) | Paper; custodian: Vermont Counsel Trust Account | 10% | 10% | 7% | Steward (individual ecologist on retainer) | 2026-05-01 | No — vacancy on resignation/death; replacement by Class 7 action | Independent ecologist with long-standing relationship with the Property; non-affiliated |
WP-005 | Landseed PBC (entity KYC; Persona ref landseed-pbc; verified 2026-01; due 2031-01) | Multi-sig: Landseed compliance officer | Advisory; methodology authority on Class 3; non-objection rights on Class 4/7/8/9 | Non-objection on Class 7/8/9 | 3% (protocol fee via Tier 1) | Landseed Steward | 2026-05-01 | Per Landseed succession (corporate) | Same as Sample 1 — entity seat for methodology and guardian veto |
Total Class-2 voting weight: 95% (Members) + Landseed advisory. Total Tier-3 distribution share: 70% + 12% + 8% + 7% = 97%. (3% is Landseed protocol fee in Tier 1.)
Privacy notes (Template B):
- KYC: institutional KYC for entity Members; individual KYC for
WP-004 - Wallet: paper with custodial trust accounts; multi-sig 2-of-2 for
WP-002 - Institutional governance procedures referenced; institutional board minutes preserved as books and records
- 501(c)(3) Land Trust is the qualified holder for any §170(h) deduction sought by an upstream donor of fee to the Trust; the LLC’s role as VECR holder is separate
Sample 3 — Template C (Indigenous Co-Governance with Cultural Guardian)
Wrapper Entity: [Community Name] Stewardship DAO LLC (Vermont DAO LLC)
Property: [Community-Confirmed Designation]
Tier: 2 (smart-contract DAO with on-chain registry)
Effective date of registry: [DATE]
Note: Template C deployments are co-design, not template instantiation (per 02-governance-templates/CLAUDE.md). This sample is illustrative of registry structure; the real registry’s content is determined with the specific community through the co-design process documented in 02-governance-templates/templates/C-indigenous-co-design.md. The sample uses generic role descriptors; a real registry uses the community’s own role designations and language.
| Beneficiary ID | Real-world identity (KYC ref; data sovereignty applies) | Wallet / custodian | Voting weight (FPIC-gated; see notes) | Distribution share | Membership class | Effective | Successor designated | Notes |
|---|---|---|---|---|---|---|---|---|
CC-001 | [Community Council Seat 1] (KYC: community-attested + Sumsub ref cc-001; verified 2026-02; due 2028-02 (shorter cadence per community MOU)) | Custodial wallet via Coinbase Prime; Council-key threshold 5-of-9 | Council majority on Class 2/4/6; supermajority on Class 3/8 | Pro-rata of community fund (Tier 3 routes 60% to community fund) | Community Council Member | 2026-06-01 | Community-determined; DAO ratifies (not a substantive vote) | Council members are designated by community elders’ procedure; Council acts collectively |
CC-002 through CC-009 | [Council Seats 2–9] (analogous structure; off-chain KYC under community-data-sovereignty MOU) | Same Council multi-sig | Council action by 5-of-9 (majority) for Class 2/4/6; 7-of-9 (supermajority) for Class 3/8 | Pro-rata of community fund per Council allocation | Community Council Member | 2026-06-01 | Community-determined per MOU; DAO ratifies | Aggregated Council seat — individual Council members vote within Council; Council outcome is the action that reaches the DAO |
CC-010 | [Cultural Guardian — designated by community elders] (KYC: minimal; community-attested only; no on-chain identity) | Air-gapped hardware wallet; in-person disposition required | Veto rights under FPIC checkpoints (02-modules.md § M2): cultural-line activities including sacred sites, breeding seasons, restricted observation periods | Pro-rata of community fund per Council allocation | Cultural Guardian | 2026-06-01 | Community-determined per protocol; DAO ratifies | Veto exercise requires written notice with rationale; veto preserved in books with restricted-access flag (community-restricted; no public publication) |
CC-011 | [Elder Council representative] (KYC: community-attested) | Air-gapped hardware wallet | Advisory + ratification on Class 3 (methodology); confirmation role on Class 4 amendments | Pro-rata of community fund per Council allocation | Elder | 2026-06-01 | Community-determined per protocol | Elder authority distinct from Council; consulted on major decisions; advisory only on operations |
CC-012 | Landseed PBC (entity KYC; Persona ref landseed-pbc; verified 2026-01; due 2031-01) | Multi-sig: Landseed compliance officer | Methodology authority on Class 3 (proposal only — Council ratifies); guardian veto on actions deliberately destroying ecological condition | 2% (protocol fee — community-negotiated minimum; below the 5% Template-A maximum) | Landseed Steward (Methodology Guardian) | 2026-06-01 | Per Landseed succession | Landseed has no cultural authority and no use-decision authority in Template C. Methodology and ecological-condition-destruction-veto only. (Per 02-modules.md § M2 guardian roles) |
Voting weights for Template C are not numeric percentages; they are gate mechanisms (FPIC checkpoints). The action proceeds when the gate is satisfied (e.g., Council 5-of-9 + Cultural Guardian non-objection for Management Plan amendment); otherwise it does not.
Tier-3 distribution share for Template C is unusual: 60–80% to a community fund (per 02-modules.md § M3; this sample uses 60%). The community fund is administered separately by Council under community-determined procedures, not directly distributed to individual seats. Allocation among Council members (and Cultural Guardian, Elder) is by community procedure, not by registry-specified percentage.
Privacy and data sovereignty notes (Template C):
- Community data sovereignty: KYC details, cultural-restriction flags, and community-internal succession procedures are held under a community-data-sovereignty MOU between the community and Landseed compliance. Landseed maintains the records as custodian, not as owner. The community may inspect, audit, and (subject to MOU procedures) request return or destruction of records.
- Off-chain only for sensitive fields: KYC documents, cultural-restriction details, and identifying information about the Cultural Guardian’s specific cultural expertise are held off-chain only. Even the off-chain custody is with limited access among Landseed-compliance personnel under MOU constraints.
- On-chain for governance state only: the on-chain DAO contract holds non-identifying state (council action records, voting outcomes, attestation references). It does not hold names, KYC references, or any personally-identifying data.
- CARE principles: per NURJ paper §II.B (cited in
02-governance-templates/CLAUDE.md), the registry’s data-handling implements Collective Benefit, Authority to Control, Responsibility, and Ethics. Specific implementations are negotiated per community in the deployment MOU. - No external publication: registry content is not published externally. References to the Wrapper Entity in any public document use the Wrapper Entity’s legal name only; individual seat-holders are not named publicly.
Successor mechanics — illustrated
Successor mechanics implement 02-governance-templates/02-modules.md § M1 successor table. Sample successions:
Scenario 1: Template A — Landowner death
MR-001 (J. Doe) dies. The procedure:
- The Manager confirms the death and notifies all Members.
MR-001’s designated successor isMR-001-SUCC-A(spouse), who is the same individual asMR-002(M. Doe).- The Manager updates the Registry:
| Change | Before | After |
|---|---|---|
MR-001 | J. Doe; 65% Tier-3 share; supermajority voting | Vacant; succeeded by MR-002 |
MR-002 | M. Doe; 15% Tier-3 share; family-member role | M. Doe; 80% Tier-3 share (combined; 65% + 15%); Owner role; supermajority voting |
MR-003, MR-004 | Family Members at 7% each | Unchanged in role; Tier-3 share unchanged; eligible to inherit per per-stirpes on M. Doe’s eventual succession |
-
The Registry is updated as Exhibit A v2 to the operating agreement, signed by the Manager. This is administrative under § 7.2(a) of the operating agreement and does not require Class 7 Member action because the succession was pre-designated.
-
KYC for
MR-002(now Owner) is re-verified earlier than the 5-year cadence to confirm Owner-role identity. -
Multi-sig wallet signers are reviewed; if
MR-001was the Landowner-key signer, M. Doe replacesMR-001as signer (ceremonial action; no on-chain governance because Tier 1).
Scenario 2: Template A — Landowner sells the property
MR-001 sells the fee in the Property to a new owner, P. Roe. The procedure:
- Per Deed § 7.1,
MR-001notifies Grantee at least 60 days before transfer. - The deed of transfer to P. Roe includes the acknowledgment required by Deed § 7.2.
- P. Roe applies for membership in the Wrapper Entity per Class 7 (membership admission).
- Class 7 Member action admits P. Roe as the new Owner seat. (In a Template A solo-landowner deployment, this typically proceeds because the alternative is dissolution under § 2.3(c), which neither party prefers.)
- The Registry is updated:
| Change | Before | After |
|---|---|---|
MR-001 | J. Doe; 65% share; Owner | Vacant; resigned on transfer of fee |
MR-002, MR-003, MR-004 | Family Members | Vacant; resigned on transfer (J. Doe family no longer holds fee) |
(new) MR-006 | P. Roe (KYC ref roe-001; verified [DATE]) | P. Roe; 94% Tier-3 share (combined); Owner |
MR-005 | Landseed Steward | Unchanged |
-
Class 7 amendment is documented as Exhibit A v2 with full Class-7 Member-action record (this is a substantive Class-7 action, not administrative).
-
KYC for P. Roe is performed before admission; multi-sig signer rotation occurs.
-
The Deed itself is not amended. Deed § 7.1–§ 7.3 contemplate this exact scenario and bind P. Roe as successor in title to the same VECR.
Scenario 3: Template C — Council member rotation
A Community Council member (CC-003) ends a term per community procedures. The procedure:
- The community-internal procedure (per MOU) selects a successor.
- The Council communicates the succession to the Manager.
- The DAO ratifies the succession — but this ratification is procedural, not substantive. The DAO does not vote on whether to accept the community’s selection; it records and acknowledges it. (Per
02-modules.md§ M1 Template C successor mechanic: “Community-determined; DAO ratifies the community’s decision; not a substantive vote”.) - The on-chain registry is updated through smart-contract transaction; the off-chain record is updated by Landseed compliance under the community-data-sovereignty MOU.
- KYC for the new Council member is performed under community-attested + light-vendor cadence (per Sample 3 cadence: 2 years).
Important: the architecture’s binding principle — that the community determines its own representation — means Landseed and the DAO are recipients of the community’s decision, not gatekeepers of it.
How this sample maps to the M1 specification
Spec source (02-governance-templates/02-modules.md § M1) | This sample |
|---|---|
| Identity (legal name + off-chain KYC) | “Real-world identity (KYC ref)” column; off-chain custody by Landseed compliance |
| Role (landowner, community council, elder, cultural guardian, etc.) | ”Membership class” column; Sample 1 = Owner/Family/Steward; Sample 2 = institutional Owner/Co-Steward; Sample 3 = Council/Elder/Cultural Guardian |
| Voting weight per decision class | ”Voting weight” columns split by Class; Template C uses gate mechanisms not numeric weights |
| Distribution share | ”Distribution share” column; sums to 94–100% (Tier 3) per template-specific waterfall |
| Successor designation | ”Successor designated” column; Yes/No with reference to designated successor or template-specific succession mechanism |
| Off-chain KYC discipline | All samples; Landseed-compliance custody; KYC re-verification every 5 years (or 2 years in Template C MOU) |
| On-chain pointer (Tier 2 only) | Sample 3 (Template C) only; Samples 1 and 2 are Tier 1, no on-chain registry |
| KYC vendors | Persona / Veriff / Sumsub per 06-risks/04-proposed-resolutions.md Q10; samples illustrate each |
| Successor mechanics (template-specific) | Three illustrated scenarios above (Templates A death, A sale, C rotation) |
| Specific architectural commitments | How this sample reflects them |
|---|---|
Permissioned-only membership (00-foundations/03-binding-principles.md Principle 3) | Class 7 admission required for new Members; non-transferability per § 2.2 of operating agreement skeleton |
| Per-property isolation (Principle 1) | Each registry is per-Wrapper Entity; no cross-Wrapper membership shown |
| Earth Credits ≠ governance positions (Principle 2) | Distribution share column is for cash distributions per Tier 3 of waterfall; no Earth Credits are held by Members directly |
CARE principles for Template C (NURJ §II.B; 02-governance-templates/CLAUDE.md) | Privacy/data-sovereignty notes for Sample 3 implement Collective Benefit, Authority to Control, Responsibility, Ethics |
| Landseed has limited scope per template | Sample 1: methodology authority + guardian veto + 3% protocol fee; Sample 2: same; Sample 3: methodology proposal only (Council ratifies), guardian veto narrow, 2% protocol fee, no cultural authority |
What this sample deliberately does NOT include
- No real names, real KYC IDs, real wallet addresses, or real properties. All entries are placeholders.
- No tradeable token positions. Membership is non-transferable per § 2.2 of the operating agreement skeleton.
- No public-facing data. Registry content lives off-chain (Tier 1) or in opaque on-chain pointers (Tier 2).
- No Template C content treated as instantiable from this template. Sample 3 illustrates structure only; real Template C registries are co-designed with the specific community.
- No specific dollar amounts. Distribution shares are percentages; actual revenue is property-specific and market-dependent.
Final reminder
This is an illustrative schema. It contains no real data. Real Beneficiary Registries are maintained by Wrapper Entity Managers under operating-agreement and architectural-commitment procedures, with KYC custody by Landseed compliance and (in Template C) community-data-sovereignty MOU constraints. Do not use any entry from this sample to populate any real registry.