# Changelog

### **Flexflow is built in the open. This changelog is a transparent record of how the framework evolves: what changed, where, and why.** 

Every structural update, refinement, and addition is documented here so that practitioners can track the system's development and understand the reasoning behind each decision.

Have a suggestion or feedback? Reach out at <create@flexflow.cc> or use the chat widget.

## **Core Concepts, Architecture Restructuring, and Framework Introduction**

<mark style="color:$info;">**March 9, 2026**</mark>

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

#### **This is the most substantial framework update since Flexflow's initial publication. Seven new Core Concepts complete the intellectual foundation.**

The Architecture has been restructured across all three layers. A new Introduction section establishes the narrative on-ramp for practitioners encountering Flexflow for the first time. And the Unified Taxonomy has been refined to resolve structural inconsistencies and strengthen the system's formal logic.

These changes reflect several months of intensive development focused on bringing the framework to alpha-ready depth: rigorous enough to build with, honest about what is still growing.

<details>

<summary><strong>Added</strong></summary>

#### **Seven Core Concepts (Concepts 4-10)**

The Core Concepts section now contains the complete intellectual arc from worldview through architecture through dynamics. The seven new concepts, each developed with the full three-part structure (Overview, In Depth, Expand Your Understanding):

* <mark style="color:$primary;">**Concept 4: A-B-C Cybernetic Loop**</mark> <sup>(Architecture tier)</sup>\
  The continuous feedback circuit connecting the three layers. Introduces multiple loop speeds (fast, medium, slow) and the Speed vs. Fidelity tension.
* <mark style="color:$primary;">**Concept 5: Fractal Organization**</mark> <sup>(Architecture tier)</sup>\
  The self-similar operating pattern that repeats at every organizational scale. Includes the seven-image "Nature's Operating Manual" gallery.
* <mark style="color:$primary;">**Concept 6: Four Dimensions of Infrastructure**</mark> <sup>(Architecture tier)</sup>\
  Infrastructure as four integrated dimensions: Physical, Digital, Biological, Cultural. Reframes burnout and cultural dysfunction as infrastructure failures.
* <mark style="color:$primary;">**Concept 7: Holistic Modularity**</mark> <sup>(Architecture tier)</sup>\
  Modules that are simultaneously self-contained and deeply connected through standardized interfaces. Includes the six-image Hex Gallery.
* <mark style="color:$primary;">**Concept 8: Living Charter**</mark> <sup>(Architecture tier)</sup>\
  The version-controlled organizational identity document with 24 components in six clusters. Introduces the Seed Charter and connective intelligence framework.
* <mark style="color:$primary;">**Concept 9: Multi-Flow Value Model**</mark> <sup>(Dynamics tier)</sup>\
  Ten forms of organizational value and the Value Spectrum diagnostic. Introduces the Enriched Game (positive-sum dynamics).
* <mark style="color:$primary;">**Concept 10: Resonance: The Amplification Principle**</mark> <sup>(Dynamics tier)</sup>\
  Mutual amplification between coherent systems under four substrate conditions (P.BND, P.REL, P.VAL, P.PRC). Operates at micro, meso, and macro scales.

#### **Framework Introduction**

A new seven-section narrative introduction serving as the entry point for practitioners discovering Flexflow for the first time. Establishes the case for the living-systems lens, names the cost of the mechanistic paradigm, and orients readers with audience-specific reading paths. Includes a gateway block for progressive disclosure: readers can absorb the core argument in 60 seconds or read the full 12-minute essay.

#### **Architecture Section Structure**

The Architecture section has been restructured as a multi-page section with a landing page and five sub-pages: Overview, Domain Reference, Unified Taxonomy, Architecture in Practice, and Design Principles. The Architecture Overview introduces three designed diagrams (three-layer topology, cybernetic loop flow, and fractal scale) to make abstract structural concepts visually navigable.

#### **Domain Reference**

A comprehensive reference page documenting all 25 domains across all three layers with sub-domain tables, descriptions, and cross-references to Core Concepts. Includes the "Adaptive by Design" section establishing that domains are a flexible scaffold, not a rigid specification.

#### **Taxonomy Overview in Domain Reference**

The Domain Reference now includes an integrated taxonomy overview with the full level table (L0-L5) and an expanded treatment of the Log as a temporal event layer for organizational sensing and intelligence.

#### **Core Concepts Landing Page**

A card-based landing page with tier groupings (Worldview, Architecture, Dynamics) and descriptions for all eleven concepts plus the closing meta-reflection.

#### **Framework Landing Page Thumbnails**

Descriptive text for all framework section thumbnails: Introduction, Core Concepts, Architecture, Ontology, Library, and Changelog.

#### **OrgKit Waitlist Page**

A new page communicating the OrgKit's five core components, development status, planned Summer 2026 release, and waitlist signup.

</details>

<details>

<summary><strong>Improved</strong></summary>

#### **A-Layer Architecture: Charter Relocation**

A1 Charter has been moved from the B-Layer (where it previously sat as a strategic domain) to the A-Layer as the anchor of Infrastructure. This reflects a fundamental design decision: the Charter is not an operational instrument but the foundational identity layer that everything else in the architecture references. The Charter is now A1, the first domain in the first layer, and all other domains trace their authority back to it.

#### **A1 Charter Sub-Domain Structure**

The Charter's internal organization has been restructured to align with the Unified Taxonomy. The six functional clusters (Identity, Strategic, Operational, Relational, Accountability, Evolution) are now formally designated as L2 Sub-Domains (A1.1 through A1.6), with the 24 Charter elements properly positioned at L4 (Component) within L3 Capabilities. This resolves a structural inconsistency where the Charter used a non-standard internal numbering system.

#### **B-Layer Architecture: Complete Redesign**

The entire Operation layer has been redesigned with five new domains replacing the previous structure: B1 Compass, B2 Programs, B3 Projects, B4 Formations, B5 Impact. The new B-Layer provides clearer separation of concerns: strategic translation (B1), operational rhythm (B2), delivery (B3), human organization (B4), and learning feedback (B5). B5 Impact is particularly significant as the domain that closes the cybernetic loop.

#### **C-Layer Architecture: Cluster Organization and Domain Refinement**

The twelve Ecosystem domains are now organized in four named clusters following a progressive sensing logic: Foundations (C1-C4), Diagnosis (C5-C7), Dynamics (C8-C10), Meta-Sensing (C11-C12). C11 has been renamed from "Sensing Systems" to "Sensors." C12 Resonance has been added as the capstone sensing domain, measuring mutual amplification between the organization and its ecosystem.

#### **A-Layer Domain Naming**

Several A-Layer domains have been renamed for clarity and precision. "Systems & Integrations" replaced by A7 Services. Service sub-domains renamed from Microservices/Mesoservices/Macroservices to Small-Scale/Mid-Scale/Enterprise-Scale Services to avoid collision with software engineering terminology. A5.1 renamed from "Foundation Models" to "Core AI Capabilities" for durability as technology evolves. A6 sub-domains renamed from "Resources" terminology to "Capital" terminology (Financial Capital, Human Capital, etc.) for distinctiveness.

#### **Unified Taxonomy: L3 Terminology**

L3 has been confirmed as "Capability" (what the organization does in a sub-domain) rather than "Module." This aligns the taxonomy with the living-systems lens: the hierarchy describes functional capacity, not just structural components.

#### **Brand Positioning**

Flexflow is now positioned as a "system" rather than a "framework" in public-facing copy. The word "framework" is reserved for the documentation section where it accurately describes that specific body of content. Home page and marketing copy uses "system" (for the whole), "architecture" (structural design), "practice" (learning dimension), and "community" (social dimension).

</details>

<details>

<summary><strong>Removed</strong></summary>

#### **B-Layer: Previous Domain Structure**

The previous B-Layer domain structure has been fully replaced. The prior domains (which included Charter at B1) have been retired in favor of the new five-domain architecture that more clearly separates strategic translation, operational rhythm, delivery, human systems, and learning feedback.

#### **Non-Standard Charter Numbering**

The original Charter numbering system (A1.0 through A1.24 with letter-coded clusters like A1.I, A1.S) has been retired in favor of standard taxonomy notation (A1.1 through A1.6 at L2, with components at L4). This brings the Charter into full alignment with the Unified Taxonomy.

#### **"Module" as L3 Terminology**

The term "Module" at L3 has been replaced with "Capability." Module remains valid as general vocabulary within the framework (particularly in the context of Holistic Modularity) but no longer holds a specific taxonomic position.

</details>

## **The New A-INFRASTRUCTURE Architecture**

<mark style="color:$info;">**October 7, 2025**</mark>

<div align="left" data-with-frame="true"><figure><img src="/files/XDNM5MJHXLZDhul9oFTM" alt=""><figcaption></figcaption></figure></div>

> #### This architectural update introduces a simpler, more powerful, and intuitive structure for the entire Infrastructure layer, including the new Protocols and Platforms domains.

This evolution streamlines the A-Infrastructure layer to be more logical and user-friendly. We've replaced the abstract and limited "CIP" with a universal Protocols domain and clarified the purpose of every standard domain.&#x20;

This change makes the framework's foundation more robust, scalable, and easier to understand in practice.

<details>

<summary><strong>Added</strong></summary>

* <mark style="color:$primary;">**A1 - Protocols**</mark> <sup>**(New L1 Domain)**</sup>\
  This new L1 Standard Domain replaces the old "CIP." It is designed to be the central, version-controlled registry for all significant protocols across the entire organization, including those for Infrastructure, Operation, and Ecosystem.
* <mark style="color:$primary;">**A6 - Platforms**</mark> <sup>**(New L1 Domain)**</sup>\
  A new L1 Standard Domain that replaces the ambiguous "Systems & Integrations." Platforms is the dedicated registry for the major, multi-function software and hardware platforms that the organization builds upon (e.g., your cloud provider, communication suite, CRM).

</details>

<details>

<summary><strong>Improved</strong></summary>

* **A-Infrastructure Domain Order**\
  The entire A-Infrastructure stack has been re-sequenced for a more logical and intuitive narrative flow: Protocols → Security → Data → AI Engine → Resources → Platforms → Services → Workflows.
* <mark style="color:$primary;">**Language Simplification**</mark>\
  Domain names have been simplified for clarity. For example, "Service Fabric" has been shortened to the more direct **A7 - Services**.
* <mark style="color:$primary;">**Conceptual Clarity**</mark>\
  The distinction between A7 - Services (external, consumed services) and A6 - Platforms (foundational, operational environments) creates a much clearer and more powerful model for managing a modern tech stack.

</details>

<details>

<summary><strong>Removed</strong></summary>

* <mark style="color:$primary;">**"Core Infrastructure Protocol (CIP)"**</mark> <sup>**(Old A1 Domain)**</sup>\
  This limited, infrastructure-only concept has been removed and replaced by the more universal and powerful **A1 - Protocols** domain.
* <mark style="color:$primary;">**"Systems & Integrations"**</mark> <sup>**(Old A8 Domain)**</sup>\
  This ambiguous domain has been removed and replaced by the more precise and useful **A6 - Platforms** domain.

</details>

## **The Multi-Flow Value Model: A New Logic for a New Era**

<mark style="color:$info;">**September 27, 2025**</mark>

<div align="left" data-with-frame="true"><figure><img src="/files/z1gvGu4kEvnfuiSbXS2J" alt=""><figcaption></figcaption></figure></div>

> #### <mark style="color:$primary;">This update introduces a powerful new framework for moving beyond the narrow "business model" to a holistic, multi-dimensional understanding of value.</mark>

We are excited to introduce a core innovation at the heart of the Flexflow Framework: [**The Multi-Flow Value Model**](broken://pages/HWSvwsjC1lJTEXee0uxb#the-multi-flow-value-model). This new model provides a richer language and a more powerful lens for seeing, cultivating, and circulating the full spectrum of value that a healthy organization generates.&#x20;

It is our answer to the extractive, mono-focused logic of the old paradigm.

<details>

<summary><strong>Added</strong></summary>

* <mark style="color:$primary;">**"The Multi-Flow Value Model"**</mark> <sup>**(New Core Concept)**</sup>\
  A new Core Concept has been added to the framework's Introduction. It defines the strategic and philosophical shift from focusing solely on financial capital to stewarding ten distinct "Flows of Value," from Social and Human to Regenerative and Symbolic.

* <mark style="color:$primary;">**"The Value Spectrum"**</mark> <sup>**(New Diagnostic Tool)**</sup>\
  We have introduced the concept of the **Value Spectrum**, a powerful visual tool inspired by the "Wheel of Life." It allows organizations to map and measure their health and balance across all ten Value Flows, turning this new model into a practical, actionable diagnostic.

* <mark style="color:$primary;">**B1.10 - Value Models**</mark>**&#x20;**<sup>**(New Charter Component)**</sup>\
  A new standard component has been added to the B1 - Charter library. This is the formal home where an organization can document its unique strategy for creating and circulating multiple forms of value.

</details>

<details>

<summary><strong>Improved</strong></summary>

* <mark style="color:$primary;">**System-Wide Integration**</mark>\
  This new value logic has been woven into the entire framework. The C5 - Value Flows domain is now explicitly about mapping these ten flows. The A5 - Resources domain is about managing the assets that constitute them. This creates a more coherent and powerfully integrated system.

</details>

<details>

<summary><strong>Removed</strong></summary>

* No core components were removed in this update. This release is focused on adding a powerful new layer of strategic depth and practical tooling to the Flexflow Framework.

</details>

## **The Living Charter: A Deep Dive into B1**

<mark style="color:$info;">**September 26, 2025**</mark>

<div align="left" data-with-frame="true"><figure><img src="/files/HQbpCOi44LX4dIeBAdrV" alt=""><figcaption></figcaption></figure></div>

> #### <mark style="color:$primary;">This major update provides the complete, component-by-component blueprint for the Living Charter, transforming it from a high-level concept into a practical, actionable tool for organizational design.</mark>

We've moved from the "what" to the "how." The B1 - Charter is the heart of any Flexflow-powered organization, and this update provides the deep, granular detail that builders need to craft their own.

We've defined the full library of standard components and established the templates for documenting them with clarity and rigor.

<details>

<summary><strong>Added</strong></summary>

* <mark style="color:$primary;">**Complete Library of 22 Standard Charter Components**</mark>\
  We have formally defined and structured the full library of [22 standard components](broken://pages/tGUGY1pqBb5wFxVhwAQB#sub-domains) that make up a comprehensive Charter. Each component, from B1.1 - Vision to B1.22 - Evolution, now has a clear purpose and a dedicated home in the framework, providing a complete and modular blueprint.<br>
* <mark style="color:$primary;">**The Organizational Alignment Protocol (OAP)**</mark>\
  A powerful new concept has been formalized within the B1.14 - Governance component. The OAP is a set of rules that ensures the organization's strategy (B - Operation) remains in a coherent, dynamic alignment with its capabilities (A - Infrastructure) and its understanding of the world (C - Ecosystem).

</details>

<details>

<summary><strong>Improved</strong></summary>

* <mark style="color:$primary;">**Charter Navigability & Structure**</mark>\
  The B1 - Charter is no longer a single page. It is now a complete section with its own landing page and dedicated sub-pages for each of the 22 components. This creates a much clearer, more manageable, and professional documentation experience.<br>
* <mark style="color:$primary;">**Practical Guidance for Builders**</mark>\
  We have introduced the "Minimum Viable Charter" concept to provide a clear starting point for new organizations. Furthermore, the Builder's Hub on every component page now directly connects the theory to the practical guides and templates in our Open Library.

</details>

<details>

<summary><strong>Removed</strong></summary>

* No core components were removed in this update. This release is focused on adding depth, clarity, and structure to the existing B1 - Charter domain.

</details>

## **The New B-OPERATION Stack**

<mark style="color:$info;">**September 6, 2025**</mark>

<div align="left" data-with-frame="true"><figure><img src="/files/VmyCBHhkBP9XUURRv9OU" alt=""><figcaption></figcaption></figure></div>

> #### <mark style="color:$primary;">This update refactors the operational heart of the framework, introducing a simpler, more powerful, and action-oriented five-part model.</mark>

This evolution streamlines the B-Operation layer to more closely mirror the natural language of building.&#x20;

We've replaced abstract concepts with the tangible, universal units of work that every organization understands instinctively: **Teams** and **Projects**. This change makes the entire framework more intuitive and powerful in practice.

<details>

<summary><strong>Added</strong></summary>

* <mark style="color:$primary;">**B2 - Teams (New L1 Domain)**</mark>\
  A new L1 Standard Domain in the **Operation** layer, designed to be the central home for your team structures, roles, and interaction protocols. This elevates the "who" of your organization to a first-class citizen in the framework.<br>
* <mark style="color:$primary;">**B3 - Projects (New L1 Domain)**</mark>\
  A new L1 Standard Domain that replaces the abstract "Core Elements." It serves as the central registry for all value-creating work, categorized into **Products & Services** (long-term), **Initiatives & Campaigns** (medium-term), and **Tasks & Bounties** (short-term).

</details>

<details>

<summary><strong>Improved</strong></summary>

* <mark style="color:$primary;">**B-Operation Stack Coherence**</mark>\
  The entire B-Operation stack has been re-sequenced for a more logical and intuitive narrative flow: Charter → Teams → Projects → Program → Impact. This creates a perfectly clear story from the "why" to "how we learn."<br>
* <mark style="color:$primary;">**Integration of "Communication"**</mark>\
  The components of the former "Communication" domain have been woven into their more natural homes. The **Communication Strategy** is now a core part of the B1 - Charter, and the **Communication Tools** are part of the A - Infrastructure layer. This makes the framework more systemic and less siloed.

</details>

<details>

<summary><strong>Removed</strong></summary>

* <mark style="color:$primary;">**"Core Elements" (Old B2 Domain)**</mark>\
  This abstract domain has been removed and replaced by the more tangible and actionable **B3 - Projects** domain.<br>
* <mark style="color:$primary;">**"Communication" (Old B4 Domain)**</mark>\
  This standalone domain has been removed, with its core functions integrated more systemically across the entire framework.

</details>

## **The Service Fabric & The Four Dimensions**

<mark style="color:$info;">**August 24, 2025**</mark>

<div align="left" data-with-frame="true"><figure><img src="/files/2lm8CPb7ycgqltMzGWef" alt=""><figcaption></figcaption></figure></div>

> #### <mark style="color:$primary;">**Introducing a new domain for taming the "Franken-stack" and a more intuitive, dimensional approach to infrastructure.**</mark>

This update introduces a powerful new way to manage your organization's service dependencies and a more human-centric structure for the entire Infrastructure layer.&#x20;

We've introduced the **Service Fabric** to bring radical clarity to your external services, and elevated the **Four Dimensions** to be the primary lens for understanding your foundational capabilities.

<details>

<summary><strong>Added</strong></summary>

* <mark style="color:$primary;">**A7 - Service Fabric**</mark>\
  A new L1 Standard Domain in the [<mark style="color:$info;">Infrastructure</mark>](broken://pages/Gx94pkLH83QktCHviuDO) layer, designed to be the central registry for all external services.
* <mark style="color:$primary;">**Micro/Meso/Macro Service Taxonomy**</mark>\
  A new classification system within the Service Fabric to strategically manage service dependencies.
* <mark style="color:$primary;">**"The Framework as a Scaffold" Core Concept**</mark>\
  A new [<mark style="color:$info;">Core Concept</mark>](broken://pages/HWSvwsjC1lJTEXee0uxb) that explicitly details the adaptive, non-rigid nature of the Flexflow Framework.

</details>

<details>

<summary><strong>Improved</strong></summary>

* <mark style="color:$primary;">**A - Infrastructure Architecture**</mark>\
  The Infrastructure layer is now organized around the four thematic dimensions (Digital, Physical, Biological, Cultural) as a meta-layer of classification, with eight functional Standard Domains. This is a more intuitive and powerful structure.
* <mark style="color:$primary;">**Language Consistency**</mark>\
  We have standardized on the term "Standard Domains" throughout the documentation for better clarity.

</details>

## **A More Scalable Taxonomy**

<mark style="color:$info;">**August 22, 2025**</mark>

<div align="left" data-with-frame="true"><figure><img src="/files/CP8rQZKwkufJ9r73FTdj" alt=""><figcaption></figcaption></figure></div>

> #### <mark style="color:$primary;">**Refining our architectural language to add a new layer of precision and a powerful new logging capability.**</mark>

To make the Flexflow Framework even more robust and scalable, we've introduced a new level to our core taxonomy and formalized how events are tracked.

<div align="left"><figure><picture><source srcset="/files/0ac4DKoOZWEOpPc3OH0U" media="(prefers-color-scheme: dark)"><img src="/files/k1alKKh50FqDntuuar4d" alt="" width="375"></picture><figcaption></figcaption></figure></div>

This update adds more granularity to the architectural hierarchy, making it easier to map complex domains while introducing a powerful temporal dimension to the entire system.

<details>

<summary><strong>Added</strong></summary>

* <mark style="color:$primary;">**L2 - Sub-Domain**</mark>\
  A new level in the [<mark style="color:$info;">Unified Taxonomy</mark>](broken://pages/4bQ1AeMhBtqwbnt4sTVt#the-unified-taxonomy-a-common-language-for-every-component)<mark style="color:$info;">,</mark> creating a more logical hierarchy between L1 Domains and L3 Capabilities.
* <mark style="color:$primary;">**The "Event Log"**</mark>\
  A new special class of object for time-stamped records, allowing for a complete audit trail and organizational memory.

</details>

<details>

<summary><strong>Improved</strong></summary>

* <mark style="color:$primary;">**Taxonomy Table**</mark>\
  The main taxonomy table has been updated to a six-level structure (L0-L5 + Log), providing a more precise and scalable model.
* <mark style="color:$primary;">**Navigational Examples**</mark>\
  All examples throughout the documentation have been updated to reflect the new, more granular taxonomy.

</details>

## **Introducing the Concept Generator**

<mark style="color:$info;">**August 14, 2025**</mark>

<div align="left" data-with-frame="true"><figure><img src="/files/vMHWqj67TdZYq2aV96r5" alt=""><figcaption></figcaption></figure></div>

> #### <mark style="color:$primary;">**A new strategic partner for your ideas and a dedicated home for all Flexflow tools.**</mark>

This is an exciting update that introduces a powerful new capability to our ecosystem. We are officially launching the [**Concept Generator**](broken://pages/UB1OaPe4ZMJIA4ypzw2D), our first major tool designed to act as your co-founder in shaping raw ideas into professional, decision-ready documents.&#x20;

To house this and future tools, we have also added a new top-level [**Tools**](broken://pages/w0YtcefhnkXvAjDPWb1d) section.

<details>

<summary><strong>Added</strong></summary>

* <mark style="color:$primary;">**The Concept Generator Tool**</mark>\
  A new, standalone tool that combines a Master Prompt, an input template, and a reference example to help you transform fragmented notes into a clear, compelling Concept Overview. It's a strategic partner designed to bring your ideas to life.
* <mark style="color:$primary;">**New "Tools" Section**</mark>\
  A new primary section has been added to the main navigation of flexflow\.cc. The Concept Generator is the first tool to be featured here, with more to come.
* <mark style="color:$primary;">**Concept Generator Guide**</mark>\
  A comprehensive, step-by-step guide on how to use the Concept Generator effectively, from understanding the Master Prompt to refining your final output.

</details>

<details>

<summary><strong>Improved</strong></summary>

* <mark style="color:$primary;">**Site Navigation**</mark>\
  The main navigation has been updated to include the new **Tools** section, providing a clear and scalable home for all current and future practical applications built by the Flexflow team.

</details>


---

# Agent Instructions: 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:

```
GET https://labs.lumeon.dev/frameworks/flexflow/changelog.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.