> For the complete documentation index, see [llms.txt](https://lumeon.gitbook.io/docs/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/docs/unsorted/bioregional-systems-lab/bslos/b-operation.md).

# B - Operation

<details>

<summary><mark style="color:$primary;"><strong>About this layer</strong></mark></summary>

#### **Operation is how work is governed and run in BSL.**

Where Infrastructure is what the lab runs on, Operation is how it moves: how attention is focused, how people are organized, how work is held and carried out, and how the lab navigates over time.

The layer runs as a sequence, not a set of parts. Beacons elevates what most needs attention into shared focus. Programs design the response and hold the continuous and recurring work, including the seasonal rhythm. Projects deliver the bounded work that runs to completion. Formations hold the people and teams who carry it. Waypoints reads what was produced and steers where the lab heads next, feeding back into how it senses itself for the next cycle.

This sequence is one turn of BSL's larger loop: the lab senses itself and its field, orchestrates a response here in Operation, acts through its Infrastructure, and senses again. The domains below take you into each part.

</details>

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h4><mark style="color:$primary;"><strong>Beacons</strong></mark></h4></td><td>How signal becomes shared focus, elevating what most needs attention.</td><td><mark style="color:$primary;"><strong>B1</strong></mark></td><td><a href="broken://pages/P1v79aFdvsWOzZ5OmW99">Broken link</a></td></tr><tr><td><h4><mark style="color:$primary;"><strong>Programs</strong></mark></h4></td><td>The seasons, cadences, and continuous work that run on an ongoing rhythm.</td><td><mark style="color:$primary;"><strong>B2</strong></mark></td><td><a href="broken://pages/WzNJbNnYcBi8CBjgCObS">Broken link</a></td></tr><tr><td><h4><mark style="color:$primary;"><strong>Projects</strong></mark></h4></td><td>The bounded work, each governed by a Compass toward a clear completion.</td><td><mark style="color:$primary;"><strong>B3</strong></mark></td><td><a href="broken://pages/SY3opVnXmP6DohoEWgTr">Broken link</a></td></tr><tr><td><h4><mark style="color:$primary;"><strong>Formations</strong></mark></h4></td><td>How people and teams are organized, from roles to teams to networks.</td><td><mark style="color:$primary;"><strong>B4</strong></mark></td><td><a href="broken://pages/wFukPichxyCtj2OJqnqq">Broken link</a></td></tr><tr><td><h4><mark style="color:$primary;"><strong>Waypoints</strong></mark></h4></td><td>How the ecosystem navigates: tracking where it has been and steering where it heads next.</td><td><mark style="color:$primary;"><strong>B5</strong></mark></td><td><a href="broken://pages/mogZ42jbG3SmDCMFE0BT">Broken link</a></td></tr></tbody></table>

d


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://lumeon.gitbook.io/docs/unsorted/bioregional-systems-lab/bslos/b-operation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

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.