> For the complete documentation index, see [llms.txt](https://lumeon.gitbook.io/lumeon-archive/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lumeon.gitbook.io/lumeon-archive/unsorted/bioregional-systems-lab/fund.md).

# Fund

#### **The BSL Fund is the financial backbone of Bioregional Systems Lab. It pools all revenue generated by the cooperative and allocates it according to principles established in the Bioregional Systems Lab Charter.**

As a multi-stakeholder cooperative, BSL does not have external shareholders or profit extraction mechanisms. Every resource that enters the fund is stewarded on behalf of the cooperative's mission: building integrative infrastructure for bioregional coordination. Members of all three classes (Core Team, Field Collective, Bioregional Representatives) have full visibility into the fund's status, flows, and allocation decisions.

Detailed governance provisions, voting thresholds for allocation changes, and the Exit-to-Commons timeline are documented in the [**BSL Charter**](broken://pages/oQ8IiY3DgD3gy0N7DnyJ).

<details>

<summary><mark style="color:$primary;"><strong>Fund Principles</strong></mark></summary>

*Full transparency. Shared stewardship. Every member sees where resources come from, where they go, and why.*

<mark style="color:$primary;">**1. Mission-First Allocation**</mark>\
The fund exists to serve the mission, not the other way around. Allocation decisions are evaluated against the cooperative's stated purpose and the priorities established in the Charter. Revenue growth is a means, not an end.

<mark style="color:$primary;">**2. Radical Transparency**</mark>\
Every member can see the full fund status at any time. Revenue sources, allocation categories, individual transactions above €1,000, and quarterly reconciliation reports are all accessible. There are no hidden accounts, off-book arrangements, or opaque discretionary pools.

<mark style="color:$primary;">**3. Multi-Flow Stewardship**</mark>\
Consistent with the Multi-Flow Value Model, the fund tracks and reports on resource allocation across multiple value dimensions, not just financial. Quarterly reports include an assessment of how fund activity has contributed to knowledge value (open-source contributions, publications), social value (community capacity built), and ecological value (bioregional outcomes supported). Financial accounting is necessary but not sufficient.

<mark style="color:$primary;">**4. Commons Commitment**</mark>\
A fixed percentage of all revenue is allocated to the Commons Pool, ensuring that BioOS and BioXD remain accessible as shared infrastructure regardless of the cooperative's commercial performance. This allocation is protected in the Charter and cannot be reduced by ordinary member vote.

<mark style="color:$primary;">**5. Fair Compensation**</mark>\
The cooperative pays fairly for the work its members do. Compensation bands are transparent, published internally, and benchmarked annually. The ratio between the highest and lowest compensation within the cooperative is capped and reported.

</details>

## **Revenue Streams**

All cooperative revenue flows into the BSL Fund from three primary sources, corresponding to the three tiers of the business model.

<table><thead><tr><th valign="top">Stream</th><th valign="top">Source</th><th valign="top">Description</th></tr></thead><tbody><tr><td valign="top"><mark style="color:$primary;"><strong>BioOS</strong></mark></td><td valign="top">Self-Deploy licenses + Partnership engagements</td><td valign="top">Annual license fees from self-deploying bioregions. Project-based revenue from collaborative partnership implementations with Field Collective practitioners.</td></tr><tr><td valign="top"><mark style="color:$primary;"><strong>Commons Marketplace</strong></mark></td><td valign="top">Transaction facilitation fees</td><td valign="top">A percentage fee on paid transactions (premium templates, specialized services, proprietary datasets, advanced integrations) exchanged through the marketplace. Free content generates no fee.</td></tr><tr><td valign="top"><mark style="color:$primary;"><strong>Education</strong></mark></td><td valign="top">Certification + Workshops + Institutional licensing</td><td valign="top">Revenue from BioOS Operator Certification programs, intensive workshop delivery, and volume licensing for institutional teams. Open Learning Commons is free and generates no direct revenue.</td></tr></tbody></table>

Additional sources (grants, philanthropic contributions, research funding) are reported separately as **Mission Capital** and are subject to the same allocation framework with any donor-restricted conditions noted transparently.

## **Allocation Framework**

The fund is allocated across six categories. Target percentages are set annually by member vote and reviewed quarterly. The ranges below represent the Charter-established boundaries within which annual targets must fall.

<table><thead><tr><th valign="top">Category</th><th valign="top">Target</th><th valign="top">Range</th><th valign="top">Purpose</th></tr></thead><tbody><tr><td valign="top"><mark style="color:$primary;"><strong>Operations</strong></mark></td><td valign="top">35%</td><td valign="top">30-40%</td><td valign="top">Core team compensation, infrastructure, legal, administration, and the operational costs of running the cooperative. Keeps the lab functional and its people fairly paid.</td></tr><tr><td valign="top"><mark style="color:$primary;"><strong>Development</strong></mark></td><td valign="top">25%</td><td valign="top">20-30%</td><td valign="top">Product and framework development. BioOS platform, BioXD methodology, AI capabilities, Self-Deploy tooling, and Commons Marketplace infrastructure. The investment in what we build.</td></tr><tr><td valign="top"><mark style="color:$primary;"><strong>Commons Pool</strong></mark></td><td valign="top">15%</td><td valign="top">15-20%</td><td valign="top">Protected allocation for open-source development, free educational content, open research, and the maintenance of BioXD and BioOS as shared public infrastructure. Cannot be reduced below 15% by ordinary vote.</td></tr><tr><td valign="top"><mark style="color:$primary;"><strong>Field Collective</strong></mark></td><td valign="top">10%</td><td valign="top">8-15%</td><td valign="top">Practitioner development, certification infrastructure, practice circle support, community of practice facilitation, and Field Collective coordination. The investment in the people who deploy the work.</td></tr><tr><td valign="top"><mark style="color:$primary;"><strong>Reserves</strong></mark></td><td valign="top">10%</td><td valign="top">8-12%</td><td valign="top">Operating reserve (target: 6 months of core operations) and contingency fund. Provides stability and ensures the cooperative can weather funding gaps without compromising mission commitments.</td></tr><tr><td valign="top"><mark style="color:$primary;"><strong>Regenerative Fund</strong></mark></td><td valign="top">5%</td><td valign="top">3-8%</td><td valign="top">Direct allocation to bioregional regeneration initiatives that fall outside the scope of paid engagements. Enables the cooperative to support early-stage bioregions, indigenous-led initiatives, and Global South deployments that cannot yet afford commercial terms.</td></tr></tbody></table>

**Notes:**

* Allocation targets are proposed by the Core Team, reviewed by the Field Collective, and approved by full member vote annually.
* Quarterly reconciliation reports compare actual allocation against targets and explain any variance above 3%.
* The Exit-to-Commons timeline (Charter-mandated transition to Perpetual Purpose Trust within 10 years) will progressively shift governance of the Commons Pool allocation to the Trust as the transition proceeds.

## **Current Fund Status**

**Reporting period:** Q1 2026 (January - March) **Fund stage:** Pre-revenue / Formation

<table><thead><tr><th valign="top">Metric</th><th valign="top">Status</th></tr></thead><tbody><tr><td valign="top"><mark style="color:$primary;"><strong>Total Fund Balance</strong></mark></td><td valign="top">€2,500</td></tr><tr><td valign="top"><mark style="color:$primary;"><strong>Revenue (Q1)</strong></mark></td><td valign="top">€0 (pre-revenue)</td></tr><tr><td valign="top"><mark style="color:$primary;"><strong>Mission Capital Received</strong></mark></td><td valign="top">€2,500 (founding contribution + initial grant)</td></tr><tr><td valign="top"><mark style="color:$primary;"><strong>Operating Runway</strong></mark></td><td valign="top">~3 months at current burn rate</td></tr><tr><td valign="top"><mark style="color:$primary;"><strong>Committed Partnerships</strong></mark></td><td valign="top"><ul><li><mark style="color:$primary;"><strong>Lumeon Labs</strong></mark> (Catalyst Grant + Foundational Infrastructure)</li><li><mark style="color:$primary;"><strong>Collective Canopy</strong></mark> (Infrastructure + Coordination)</li><li><mark style="color:$primary;"><strong>Flexflow</strong></mark> (Substrate framework for BioOS )</li></ul></td></tr><tr><td valign="top"><mark style="color:$primary;"><strong>Self-Deploy Licenses</strong></mark></td><td valign="top">0 (product in development)</td></tr><tr><td valign="top"><mark style="color:$primary;"><strong>Field Collective Members</strong></mark></td><td valign="top">2 (founding practitioners)</td></tr></tbody></table>

**Q1 Allocation (Actual):**

<table><thead><tr><th valign="top">Category</th><th valign="top">Allocated</th><th valign="top">% of Total</th><th valign="top">Notes</th></tr></thead><tbody><tr><td valign="top"><mark style="color:$primary;"><strong>Operations</strong></mark></td><td valign="top">€0</td><td valign="top">00%</td><td valign="top">Above target range. Expected during formation phase with zero revenue. Core team compensation and legal setup.</td></tr><tr><td valign="top"><mark style="color:$primary;"><strong>Development</strong></mark></td><td valign="top">€0</td><td valign="top">00%</td><td valign="top">Above target range. Heavy front-loading of BioXD and BioOS protocol development.</td></tr><tr><td valign="top"><mark style="color:$primary;"><strong>Commons Pool</strong></mark></td><td valign="top">€0</td><td valign="top">15%</td><td valign="top">At minimum. Open-source framework documentation and GitBook infrastructure.</td></tr><tr><td valign="top"><mark style="color:$primary;"><strong>Field Collective</strong></mark></td><td valign="top">€0</td><td valign="top">0%</td><td valign="top">Below target range. Minimal activity pre-launch. Founding practitioner onboarding costs only.</td></tr><tr><td valign="top"><mark style="color:$primary;"><strong>Reserves</strong></mark></td><td valign="top">€0</td><td valign="top">4%</td><td valign="top">Below target range. Building toward 6-month reserve as revenue begins.</td></tr><tr><td valign="top"><mark style="color:$primary;"><strong>Regenerative Fund</strong></mark></td><td valign="top">€0</td><td valign="top">0%</td><td valign="top">Not activated during pre-revenue phase.</td></tr></tbody></table>

**Variance notes:** Operations and Development are over-allocated relative to long-term targets. This is expected and appropriate during the formation phase, where the cooperative is building the foundational infrastructure before revenue begins. The trajectory toward target allocation ranges is projected for Q3 2026, contingent on the pilot partnership closing and the first Self-Deploy licenses being sold.

## **Upcoming Milestones**

<table><thead><tr><th valign="top">Target</th><th valign="top">Milestone</th><th valign="top">Fund Impact</th></tr></thead><tbody><tr><td valign="top"><mark style="color:$primary;"><strong>Q2 2026</strong></mark></td><td valign="top">Pilot partnership signed</td><td valign="top">First BioOS Partnership revenue. Operations allocation normalizes toward target range.</td></tr><tr><td valign="top"><mark style="color:$primary;"><strong>Q3 2026</strong></mark></td><td valign="top">BioOS Self-Deploy MVP launched</td><td valign="top">First license revenue. Development allocation begins normalizing.</td></tr><tr><td valign="top"><mark style="color:$primary;"><strong>Q4 2026</strong></mark></td><td valign="top">First Education cohort enrolled</td><td valign="top">Education revenue stream activated. Field Collective allocation increases toward target.</td></tr><tr><td valign="top"><mark style="color:$primary;"><strong>Q1 2027</strong></mark></td><td valign="top">Commons Marketplace beta</td><td valign="top">Marketplace facilitation fees begin. Regenerative Fund activated.</td></tr><tr><td valign="top"><mark style="color:$primary;"><strong>2027</strong></mark></td><td valign="top">Cooperative formalized with all three membership classes</td><td valign="top">Full allocation governance operational. All members voting on annual targets.</td></tr></tbody></table>

*This page is updated quarterly. Last update: March 2026. Full quarterly reports are accessible in the **Fund Archive**. Questions about the fund can be raised in the **Stewardship Circle** on the community platform or directed to the Core Team at* [*fund@bioregionalsystemslab.org*](mailto:fund@bioregionalsystemslab.org)*.*


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://lumeon.gitbook.io/lumeon-archive/unsorted/bioregional-systems-lab/fund.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
