> For the complete documentation index, see [llms.txt](https://www.bioregionalsystemslab.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.bioregionalsystemslab.org/dev/evolution/building-in-the-open.md).

# Building in the Open

<mark style="color:$info;">**May 12, 2026 · General**</mark>

<figure><img src="/files/O4iNedZEcflb7yLlLCIq" alt=""><figcaption></figcaption></figure>

#### **The site has been live for over a month. Today is the day it begins to carry the substance it was designed to carry.**

The Season 2 page is published in working form. The Bioregional Mapping Toolkit project page is up, with the Concept Document published as a public artifact. The first Evolution entries land here. The frameworks page reflects current state. The Program section names the lab's working rhythm honestly.

None of this is finished. That is the point.

## **What is now visible**

What you see today is the lab in its living state. Frameworks taking shape. Projects mid-build. A cooperative finding its rhythm.

<mark style="color:$primary;">**BioOS is at Alpha.**</mark> The architecture has been worked through three passes of structural review. Twenty Domains across three layers. Twelve Core Concepts. A Bioregional Vision as a named architectural feature. The framework documentation is being produced through the spring.

<mark style="color:$primary;">**Bioregional Mapping Toolkit is in active development.**</mark> The Concept Document is at v2. The Alpha prototype is in field testing with a selected group of practitioners. Six components are scoped. Three are in production this season.

The cooperative has opened. Membership is small and deliberate at this stage. Year Zero is about getting the foundation right rather than scaling.

Season 2 is the season where these strands meet real terrain.

## **Why we work this way**

We launch this way on purpose, so those most able to shape the work can do so while it forms. Polished surfaces look complete. Complete-looking work invites passive reception. Working surfaces invite contribution.

The lab is small. The field BSL is contributing to is much larger than the lab itself. Most of what will eventually matter about this work will not come from inside BSL. It will come from practitioners, partners, and bioregions who engage early enough that their feedback shapes what gets built.

Building in the open is how that engagement becomes possible.

## **What this means practically**

Drafts are visible before they are final. Frameworks are documented at the maturity they actually hold, not the maturity that would be most impressive. Project pages surface working artifacts alongside polished ones. Evolution entries land at the pace work actually happens, not at a publishing cadence designed to perform activity.

The site will continue to develop through Season 2 and beyond. Some things will be revised. Some directions will change. The version markers across the site let returning visitors track what is current.

What is committed: the work is real, the state is what we say it is, and contribution pathways are genuine.

## **How to engage**

Read the [Season 2 page](/dev/program/season-2-first-light.md) for the current working surface. Read the [Bioregional Mapping Toolkit project page](/dev/projects/bioregional-mapping-toolkit.md) for the most active build. Read the [frameworks page](/dev/frameworks.md) for the architectural ground.

If you want to contribute, the cooperative is open. Membership pathways are on the Engage page.

If you want to stay in touch without joining, the newsletter publishes selected Evolution entries and major milestones. Quiet cadence. Worth the inbox.


---

# 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://www.bioregionalsystemslab.org/dev/evolution/building-in-the-open.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.