Every proposed change from Membership Agreement v.1 (original attorney draft) to Membership Agreement v.2 (revised draft)
MA v.1 (original) ↗ MA v.2 (revised) ↗ Legal analysis ↗
← Membership Agreement Analysis  ·  RegenHub, LCA  ·  Proposed Changes Index

Membership Agreement — Proposed Changes Index

Serialized reference list of every proposed change from Membership Agreement v.1 (original attorney draft) to Membership Agreement v.2 (revised draft), drawn from initial counsel analysis (Issues 01–06) and the May 2026 independent research addendum (Items A01–A04). Each item carries a stable identifier for use in discussion, amendment motions, and version tracking.

ID Title Section Nature
Counsel Analysis — Issues 01–06
MA-01 IP Assignment — Scope Misaligned with Cooperative Model § 3.3 Blocking
MA-02 Voluntary Withdrawal and Membership Interest Redemption Missing § 5.6 (new) Blocking
MA-03 Patronage Accounting and Federal Tax Alignment §§ 2.3–2.4, 3.3 Blocking
MA-04 Recital — Foundational Framing Mischaracterizes Entity Preamble / Recital Advisable
MA-05 Termination — No Cure Period or Procedural Protection § 5 Advisable
MA-06 Membership Class Architecture — Scope, Dues Notice §§ 1–1.1, 1.5 Clarifying
MA-07 Status of Parties — Positive Owner-Member Characterization § 9.4 Clarifying
Research Addendum — Items A01–A04
MA-A01 Schedule A Is Empty and Share Price Lives in Two Places § 1.4, Schedule A Extends BL-04
MA-A02 Agreement Speaks Subchapter T Inside a Subchapter K Entity §§ 2.3, 2.4, 3.3 Blocking
MA-A03 Withdrawal Returns Unclear Amount on Inconsistent Clock § 5.4 · Bylaws §§ 1.7.3–1.7.4, 1.9 Extends MA-02
MA-A04 IP Section Largely Resolved in v.2 — Two Residuals Remain §§ 3.4.1–3.4.4 Diverges
Cross-document conflicts with Bylaws
Counsel Analysis · Issues 01–06
MA-01

IP Assignment — Scope Misaligned with Cooperative Model

§ 3.3 · § 3.3.3 Blocking
Problem

"Scope of their service" is undefined and overbroad — it could capture a member's independent professional practice, prior work, and open-source contributions that have no connection to Cooperative-commissioned deliverables. This assignment scope is not required by C.R.S. § 7-58-602 and is inconsistent with the Cooperative-of-practice model where members are practitioners, not employees.

§ 3.3.3's portfolio license requires prior written permission "on each occasion" before a member may display their own work — more restrictive than most employment agreements and contrary to the member's interest in marketing their practice.

Proposed — Define "Cooperative-Commissioned Work"
Add definition before § 3.3:
"Cooperative-Commissioned Work" means Intellectual Property developed by Applicant pursuant to a written task assignment, statement of work, or engagement letter executed by an authorized officer of the Cooperative, expressly identifying the deliverable as a work-made-for-hire for the Cooperative, and for which Applicant has received or is entitled to receive compensation from the Cooperative beyond the standard member share and any patronage allocation.
Proposed — Replace § 3.3 Works-Made-for-Hire Scope
Replace § 3.3 assignment scope:
The Cooperative shall have title to, ownership of, and all proprietary rights in and to any Intellectual Property constituting Cooperative-Commissioned Work. All such work shall be considered "works made for hire" as defined by 17 U.S.C. §§ 101 and 201(b). To the extent any Cooperative-Commissioned Work is not deemed a work made for hire, Applicant hereby assigns all right, title, and interest therein to the Cooperative. Intellectual Property developed by Applicant outside the scope of Cooperative-Commissioned Work — including Applicant's independent professional practice, open-source contributions, and prior work — remains Applicant's property and is not affected by this Agreement.
Proposed — Replace § 3.3.3 Portfolio License
Replace § 3.3.3 with notice-and-objection model:
The Cooperative grants Applicant a perpetual, royalty-free, non-exclusive license to display Cooperative-Commissioned Work in Applicant's professional portfolio and in the marketing of Applicant's services. Before any such display, Applicant shall provide the Cooperative written notice identifying the specific work and proposed use. The Cooperative may, within ten (10) business days of such notice, provide written objection based solely on a specific client confidentiality obligation binding on the Cooperative. Absent a timely objection, Applicant may proceed.
See also MA-A04 (addendum): IP provisions are materially improved in v.2. Residual items: (1) confirm assignment (not work-made-for-hire label) is the operative mechanism for non-qualifying works; (2) confirm venture IP developed through the Cooperative's commercial activities is explicitly excluded from § 3.3 unless subject to a separate written agreement.
MA-02

Voluntary Withdrawal and Membership Interest Redemption Missing

§ 5.6 (new section) Blocking
Problem

The Agreement addresses termination by the Cooperative but is silent on voluntary resignation. C.R.S. § 7-58-1101(1) gives members an unconditional right to dissociate from the Cooperative at any time. The Agreement must implement that right. § 9.1 prohibits transfer without consent but provides no exit mechanism — a member wishing to leave has no documented path and no clarity on what happens to their equity.

Proposed — Add New Section 5.6: Voluntary Withdrawal
New § 5.6:
Applicant may voluntarily withdraw from membership at any time by providing written notice to the Cooperative. Withdrawal is effective upon the date the Cooperative receives such notice, unless Applicant specifies a later effective date. Upon the effective withdrawal date: (a) Applicant's right to access Cooperative services, participate in governance, and receive future profit allocations shall terminate; and (b) the Cooperative shall redeem Applicant's Class A stock at its original purchase price ($100.00 per share) within ninety (90) days of the effective date, subject to (i) the limitations on distributions under C.R.S. § 7-58-1007, (ii) any outstanding financial obligations of Applicant to the Cooperative as of the withdrawal date, and (iii) Board authorization as required by C.R.S. § 7-58-1006. Any patronage credits formally noticed and allocated to Applicant's capital account but not yet distributed shall be redeemed in accordance with the Cooperative's then-current patronage redemption schedule. Applicant's obligations under Sections 3.3, 4, 6, 7, and 9 survive withdrawal.
Open question for the board: should redemption return par value ($100) or the member's positive capital-account balance? Under Subchapter K, the member has paid income tax on retained allocations — returning only par value may create a tax phantom. See MA-A03 for the full capital-account problem.
MA-03

Patronage Accounting and Federal Tax Alignment

§§ 2.3–2.4 · § 3.3 Blocking
Problem

§ 2.3 gives the Board full discretion to set and change the profit-share formula. This level of discretion undermines (1) IRC § 704(b)'s substantial economic effect safe harbor, which requires documented capital-account machinery that moves deterministically with allocations, and (2) C.R.S. § 7-58-1004's proportional-to-patronage default. A Board that can change the formula at will cannot demonstrate the stable allocation mechanism § 704(b) requires.

Proposed — Add § 2.4: Patronage Plan
New § 2.4:
The Board shall adopt a written Patronage Plan within ninety (90) days of admitting the first patron member. The Patronage Plan shall specify: (a) the method for calculating each patron member's patronage for each fiscal year; (b) the basis for allocating net margins among patron members in proportion to their patronage, consistent with C.R.S. § 7-58-1004; (c) the form and timing of patronage dividends, including the minimum percentage to be paid in cash; (d) the procedures for issuing written notices of allocation to each patron member; and (e) the procedures for maintaining and adjusting patron capital accounts. The Board may amend the Patronage Plan, provided that any amendment reducing the cash component of patronage dividends or changing the patronage basis shall require approval by a majority of patron members at a duly noticed meeting.
Proposed — Add IRC § 704(b) Consent to § 3.3
Add to § 3.3:
Applicant further acknowledges that: (a) the Cooperative intends to maintain capital accounts for patron members in accordance with Treasury Regulation § 1.704-1(b)(2)(iv); (b) the Cooperative will provide Applicant with annual written notices of allocation reflecting Applicant's distributive share of net income or loss for each fiscal year; and (c) such allocations are intended to have substantial economic effect within the meaning of IRC § 704(b).
See also MA-A02 (addendum): the agreement uses Subchapter T vocabulary ("patronage dividends," "net margins," "year received") inside a Subchapter K entity. These are blocking issues that need vocabulary conformance before execution.
MA-04

Recital — Foundational Framing Mischaracterizes the Entity

Preamble / Recital Advisable
Problem

The current recital describes RegenHub as "a coworking space and community venue in Boulder, Colorado, providing affordable workspace and event infrastructure." This is a facilities description that omits the entity's Public Benefit LCA status, its scenius purpose, its cooperative-of-practice character, and the hybrid (physical + distributed) nature of its membership base. Recital language affects interpretation of ambiguous provisions throughout the Agreement.

Proposed — Replace Recital
Replace current recital with:
RegenHub, LCA ("Cooperative") is a Colorado Public Benefit Limited Cooperative Association organized to cultivate scenius — the collective intelligence that arises from communities of practice — through right relationship between tools and the people who use them. The Cooperative serves patron members who are practitioners, builders, and thinkers operating across Boulder, Colorado and aligned virtual and regional communities. The Cooperative may operate physical gathering space, digital infrastructure, programs, and services in furtherance of this public benefit purpose.
MA-05

Termination — No Cure Period or Procedural Protection

§ 5 Advisable
Problem

§ 5 authorizes termination on grounds including "conduct detrimental to operations or reputation," "good faith belief" of inaccurate reporting, and conduct "inhibiting other members." Only non-payment includes a 30-day cure period. Patron members are owner-members with equity — termination without notice and opportunity to respond is procedurally thin even if legally within the Board's authority, and may conflict with Bylaws § 1.10.1's notice requirements for suspension.

Proposed — Tighten Termination Grounds (d) and (e)
Replace § 5.1(d):
From: "RegenHub, in its reasonable business judgment, determines that Applicant's conduct is detrimental to the operations and/or reputation of RegenHub"

To: "the Cooperative, in its reasonable business judgment based on specific, articulable facts, determines that Applicant's conduct is materially detrimental to the operations and/or reputation of the Cooperative"

Replace § 5.1(e):
From: "RegenHub determines, based on a good faith belief, that Applicant has inaccurately reported information"

To: "the Cooperative determines, based on a good faith belief supported by specific facts, that Applicant has inaccurately reported information material to Applicant's membership or patronage"

Why: The v1 standards for (d) and (e) were vague enough to be applied pretextually. Adding "specific, articulable facts" to (d) and "supported by specific facts / material to membership or patronage" to (e) reduces the risk of arbitrary termination and makes the Board's determination subject to meaningful review. Minor errors or conduct that is not materially harmful cannot be a termination ground.
Proposed — Add Notice and Cure Provision After § 5 Grounds
Add after termination grounds list:
Notice and Cure. Before exercising any termination right under this Section 5 (other than under Section 5(b) [non-payment] or Section 5(c) [false statement]), the Cooperative shall provide Applicant with: (a) written notice specifying the ground(s) for the proposed termination and identifying the conduct or omission at issue; and (b) a thirty (30)-day period to cure, where the breach is reasonably capable of cure. Termination shall be carried out in accordance with the dispute resolution procedures in the Bylaws. Prior to any final termination determination, Applicant shall have the right to submit a written response to the Board or its designated committee.
MA-06

Membership Class Architecture — No Explicit Scope Statement

§§ 1–1.1 Clarifying
Problem

The Agreement does not identify itself as the Class A Patron Member agreement. With the Techne co-op agreement anticipated and additional membership classes possible, scope clarity is needed so members and future agreements know which class each document governs.

Proposed — Add Scope Statement to § 1
Add opening sentence to § 1:
This Agreement governs Class A patron membership in RegenHub, LCA. It does not govern investor membership or any other membership class established by the Board after the date of this Agreement.
Proposed — Add Class Architecture Note to § 1.1
Add after stock price mechanics in § 1.1:
The Board may establish additional membership classes with different financial rights, governance rights, and stock prices. Membership in any such additional class shall be governed by a separate membership agreement or addendum specific to that class.
Proposed — Add Dues Increase Notice Requirement to § 1.5
Add to § 1.5 (Membership Dues):
The Board may, in its discretion, establish membership dues payable by patron members. The Board may change the amount, frequency, or structure of membership dues; provided that any increase in dues shall take effect no sooner than thirty (30) days after written notice to all affected patron members.

Why: v1 gave the Board unconstrained discretion to change dues without any notice period. A sudden dues increase could effectively force members out by making membership unaffordable. The 30-day advance notice requirement is a baseline fairness protection and is consistent with the Board's duty of good faith to members under the ULCAA. Decreases and structural changes (e.g., from annual to monthly billing) are not subject to the notice requirement — only increases.
MA-07

Status of Parties — Positive Owner-Member Characterization

§ 9.4 Clarifying
Problem

Section 9.4 in v1 defines the parties' relationship exclusively through negative disclaimers — Applicant is not an employee, not an independent contractor, not a partner. While accurate, the provision says nothing about what Applicant actually is. This creates an interpretive gap: if a dispute arises and a court or third party looks to the agreement to characterize the relationship, they find only a list of what it is not.

In the cooperative context, this omission is particularly consequential. LCA members are owner-members — they hold equity interests and governance rights, not merely service access. Courts interpreting ambiguous relationship language look for the most analogous established category. Without a positive characterization, the agreement implicitly invites classification as something other than what was intended.

Proposed — Add Positive Characterization to § 9.4
Add opening sentence to § 9.4 before the existing disclaimers:
From (v1): "9.4 Status of Parties. Applicant is not an employee, agent, independent contractor, or partner of the Cooperative."

To (v2): "9.4 Status of Parties. Applicant is an owner-member of the Cooperative with the rights and obligations set forth in this Agreement and the Governing Documents. Applicant is not an employee, agent, independent contractor, or partner of the Cooperative."

Why: The term "owner-member" is legally significant under ULCAA. It signals equity ownership (membership stock under § 1.1) and democratic participation (voting rights under Bylaws Art. V), distinguishing the relationship from all of the categories the disclaimers negate. A court reading § 9.4 now has a positive anchor — "owner-member" — before reaching the list of what the relationship is not.
Note

This change is already reflected in the published v2 document. The proposed language above is the as-drafted text. No further revision is required unless the Board wishes to add a cross-reference to Bylaws Art. V (Member Rights) or the ULCAA's member equity provisions.

Research Addendum · Items A01–A04 · May 2026
MA-A01

Schedule A Is Empty and Share Price Lives in Two Places

§ 1.4 · Bylaws Schedule A Extends BL-04
Problem

MA § 1.4 hard-codes the share price at $100.00. Bylaws Schedule A is currently a placeholder. If Schedule A is ever populated with a different figure, or if the share price changes, both documents must be amended in parallel — creating a coordination burden and a drift risk. The single-source-of-truth principle requires one authoritative location.

Proposed Path
  1. Populate Bylaws Schedule A with definitive per-class share prices before execution.
  2. Revise MA § 1.4 to read: "The share price per Class A share is the amount set forth in Schedule A to the Bylaws, as amended from time to time by the Board." Remove the hard-coded $100.00 reference.
MA-A02

Agreement Speaks Subchapter T Inside a Subchapter K Entity

§§ 2.3, 2.4, 3.3 Blocking
Problem

The Cooperative has elected partnership tax treatment (Subchapter K). Under Subchapter K, a member includes their distributive share of income or loss in their taxable income for the year in which the Cooperative's taxable year ends — not the year they receive a distribution. The Agreement uses Subchapter T vocabulary: "net margins," "patronage dividends," "written notices of allocation," and "in year received." These are concepts from cooperative tax law (IRC §§ 1381–1388), which applies to cooperatives taxed as corporations, not partnerships. The vocabulary mismatch will confuse members about when their tax obligation arises.

Proposed Vocabulary Conformance
Replace throughout §§ 2.3, 2.4, 3.3:
  • "Net margins" → "net income" or "taxable income"
  • "Patronage dividends" → "distributive share"
  • "Written notices of allocation" → "capital account allocation" or "Schedule K-1"
  • "In year received" → "in taxable year of Cooperative in which allocated, as reported on Schedule K-1"
  • State-law patronage hook (C.R.S. § 7-58-1004 proportional distribution) may remain as a cooperative-purpose provision governing the calculation basis, distinct from the federal tax vocabulary.
MA-A03

Withdrawal Returns Unclear Amount on Inconsistent Clock

§ 5.4 · Bylaws §§ 1.7.3–1.7.4, 1.9 Extends MA-02
Problem

Three provisions give three different answers to "what does a withdrawing member receive?"

Bylaws § 1.7.4 settles the capital account at book value. MA § 5.4 redeems the share at $100 par plus separate patronage credits under a schedule that does not exist. Bylaws §§ 1.7.3 and 1.9 give the Board up to 12 months to process redemption.

The deeper problem under Subchapter K: a member pays income tax each year on their allocated share of Cooperative income, whether or not distributed. If withdrawal returns only $100 par value and not the accumulated capital-account balance (which contains retained allocations the member has already taxed), the member has paid tax on value they never received — a tax phantom. MA § 5.4's separate patronage-credit schedule is the right instinct but does not equal the capital account as drafted.

Proposed — Single Withdrawal Rule
Recommended resolution:
Adopt a single rule across both documents: a withdrawing member is paid their positive capital-account balance (which already contains the $100 original contribution plus all retained allocations) on a single stated timeline, subject to C.R.S. § 7-58-1007 distribution limits. Remove or reconcile the separate par-value and patronage-credit redemption provisions. Identify which document controls timing — recommend the Bylaws as governing, with the MA cross-referencing.
This item should be resolved together with BL-06 (Bylaws redemption window). The timeline and the amount must come from the same document to avoid future conflict.
MA-A04

IP Section Largely Resolved in v.2 — Two Residuals Remain

§§ 3.4.1–3.4.4 Diverges from MA-01
Affirmed
The independent research read finds that the IP provisions in v.2 (§§ 3.4.1–3.4.4) materially improve on v.1. The member-overreach concern raised in MA-01 is largely resolved. The portfolio license mechanism is more workable. This item diverges from MA-01's blocking assessment: the v.2 IP section is not a blocking issue on its own.
Two Residuals Require Attention

Residual 1 — Assignment mechanism: Confirm that the operative IP transfer mechanism is assignment (not the work-made-for-hire label) for deliverables that do not meet the statutory definition of works made for hire under 17 U.S.C. § 101. If the label fails, assignment is the fallback; both should be expressed in the agreement to avoid the gap.

Residual 2 — Venture IP: Confirm that IP developed through the Cooperative's commercial or investment activities (venture IP, portfolio company IP) is explicitly excluded from § 3.4's member assignment unless subject to a separate written agreement covering that specific engagement. As drafted, § 3.4 is ambiguous about whether venture IP developed by a member who is also an advisor or director of a portfolio company is captured.