The Baseflow Operating System is based on self-governance; self-governance is still governance—but it’s built, owned, and evolved by the people who live it. Right now, trust fuels the organization, with few formal processes. Growth demands more structure, but instead of top-down control, self-governance will let teams shape their own rules. This isn’t just about scaling—it’s about unlocking agility, ownership, and continuous evolution.

It will be a long journey to get there—shifting from implicit trust to explicit, shared governance takes time, learning, and iteration. But every system starts with a first step, and this document is ours. Here, we lay the foundation for a governance model that grows with us, shaped by the people who make it work.

Hold on, what does self-governance look like?

It’s a system where governance isn’t set in stone—it’s dynamic, decentralized, and shaped by those doing the work. Instead of fixed hierarchies, it runs on roles and circles.

Roles give clarity on responsibilities, while circles are self-organizing teams that evolve as needs change. Decisions happen where the knowledge is, not just at the top. It’s not chaos, and it’s not corporate red tape—it’s a framework for agility, ownership, and continuous improvement.

I know, committee sounds bad as well, but it beats management by compliance and the world is not perfect. (Image stolen from Scott Millet)

Circles are self-organizing teams that manage a specific domain within the organization. Instead of traditional departments, each circle has autonomy to define roles, make decisions, and evolve its governance. Circles are…

• Purpose-driven – Every circle exists to fulfill a specific function in the organization.
• Linked roles – Each circle has roles that contribute to its purpose, including a Lead Link to connect with the broader structure.
• Nested structure – Circles can contain sub-circles, allowing governance to scale organically.
• Self-governance – Circles define their own roles, policies, and processes within their scope.

Are we done? not quite. There is some additional scaffolding to make self-governance work. Much like the kernel in an Operating System, there are events (recurring meetings for governance and work) and artifacts (documentation and transparency tools) to keep everything running smoothly.