# Domain Reference

#### **Flexflow's architecture contains twenty-five domains organized across three Core Layers. Each domain represents a distinct functional area of organizational life. Together, they provide a complete map of what an organization is and does.**

Every domain entry on this page follows a consistent format: a positioning statement, a description of what the domain covers and why it exists, a table of sub-domains, and connections to relevant Core Concepts and related domains. Individual domain deep-dives will be developed over time and linked from each entry as they become available.

## **How the Domain Map is Organized**

The architecture follows a unified hierarchy. Each level nests inside the one above it, from the broadest structural grouping down to the smallest managed element. This page covers Levels 0 through 2 (Layers, Domains, and Sub-Domains). Deeper levels are developed in individual domain deep-dives as they become available.

<table><thead><tr><th width="84">Level</th><th width="126">Name</th><th width="112">Outline ID</th><th width="141">Stable ID</th><th width="148">What It Represents</th><th>Example</th></tr></thead><tbody><tr><td><strong>L0</strong></td><td>Core Layer</td><td><strong>A, B, C</strong></td><td>INF, OPR, ECO</td><td>Highest grouping of the architecture</td><td>A - Infrastructure</td></tr><tr><td><strong>L1</strong></td><td>Domain</td><td><strong>A1, B1, C1</strong></td><td>INF.01, OPR.01</td><td>Primary functional area inside a layer</td><td>A7 - Services</td></tr><tr><td><strong>L2</strong></td><td>Sub-Domain</td><td><strong>A1.1, B1.1</strong></td><td>INF.01.01</td><td>Sub-area inside a domain</td><td>A7.3 - Enterprise-Scale Services</td></tr><tr><td><strong>L3</strong></td><td>Capability</td><td><strong>A1.1.1</strong></td><td>INF.01.01.01</td><td>What the organization does in that sub-domain</td><td>A7.3.1 - Manage Logistics</td></tr><tr><td><strong>L4</strong></td><td>Component</td><td><strong>A1.1.1.1</strong></td><td>INF.01.01.01.01</td><td>A specific system, artifact, or process</td><td>A7.3.1.1 - Shipping Partner</td></tr><tr><td><strong>L5</strong></td><td>Element</td><td><strong>A1.1.1.1.1</strong></td><td>INF.01.01.01.01.01</td><td>The smallest managed item, single owner</td><td>A7.3.1.1.1 - DHL Contract</td></tr></tbody></table>

Every element in the architecture carries two IDs. The <mark style="color:$primary;">**Outline ID**</mark> (A7.3.1.1) is designed for human navigation: intuitive, hierarchical, easy to reference in conversation.&#x20;

The <mark style="color:$primary;">**Stable ID**</mark> (INF.01.01.01.01) is designed for machine readability: consistent format, unambiguous, queryable by AI systems. Both refer to the same element. The dual system makes the architecture simultaneously human-navigable and machine-readable.

#### **The Log: Events in Context**

The taxonomy levels above describe what exists in the organization: its structure, capabilities, and components. The Log captures what happens.

A Log entry is a time-stamped event attached to any level in the hierarchy. It records that something occurred, when it occurred, and where in the architecture it occurred.

**Format:** `ID.YYYYMMDD.HHMM` **Example:** `A7.3.1.1.1.20251115.1030` — Contract signed with DHL, logged against the specific Element where it happened.

The Log is not a hierarchical level. It is a temporal layer that runs alongside the structure. Levels describe the organization as it is. The Log describes the organization as it moves through time. Together, they make the architecture both structural and temporal.

This matters for sensing and organizational intelligence. When events are logged against specific architectural locations, the system accumulates a structured history that can be queried, analyzed, and learned from. "What happened in the B-layer this quarter?" is a question the Log can answer. "What C-layer observations preceded this B5 Impact review?" is a pattern the Log can reveal. The cybernetic loop (Core Concept 4) depends on the organization's ability to sense what is happening. The Log is the mechanism that makes that sensing architecturally concrete.

The Log is a foundational concept with room to evolve. Future development may include event type classification (Decision, Observation, Milestone, Incident, Change, Learning), significance indicators, and linkage between related events across layers to enable causal chain analysis.

For the full treatment of the taxonomy including the dual ID system, navigational examples, and the Log specification, see the Unified Taxonomy page.

## **Adaptive by Design**

The twenty-five domains listed on this page are the Flexflow standard set, built to address the universal needs of organizations operating as living systems. They are not a rigid specification. They are a scaffold.

You can tailor this scaffold to match your organization's context. Rename domains to fit your language. Combine domains that overlap in your operating reality. Split domains that carry too much scope for your needs. Add entirely new domains that address functions unique to your situation. The same applies at every level of the hierarchy: sub-domains, capabilities, and components are all starting structures, not final configurations.

The only constraint is architectural coherence. The three-layer logic (Infrastructure, Operation, Ecosystem) and the cybernetic relationship between them should hold. Within that logic, the domain structure is yours to shape. A three-person startup and a thousand-person enterprise will activate different domains at different depths. Both are valid expressions of the same architecture.

As your organization evolves, so should your domain map. Domains can be added, retired, or restructured as conditions change. The architecture is designed for this. A living system does not maintain a fixed set of organs. It develops the capabilities its environment demands.

## **A - Infrastructure**

<mark style="color:$primary;">**Foundation for Capability**</mark>

The organization's body. Everything it has, everything it can do, and the conditions that sustain its capacity to function. Infrastructure is viewed through four integrated dimensions: Physical, Digital, Biological, and Cultural (Core Concept 6). This lens shapes how every domain in this layer should be read. A domain like Security is not only digital. A domain like Resources is not only financial. Each domain below has expressions across all four dimensions, and designing for only one or two leaves the infrastructure incomplete. Eight domains.

### **A1. Charter**

**Organizational Identity and Strategy**

The version-controlled source of truth encoding the organization's identity, values, strategy, and operating logic. The [Charter](broken://pages/wbHN1Br7U9U2NqOVb5bW) is not a document that describes the organization. It is the operating system that runs it. Contains six sub-domains representing distinct functional clusters, each containing the capabilities and components that define that aspect of organizational identity. Every other domain in the architecture traces its authority back to the Charter.

Organizations begin with the Seed Charter: a minimum viable identity that activates a focused subset of components across clusters. As the organization matures, the Charter deepens. Components are added, refined, and versioned. The Charter is never complete. It is always current.

<table><thead><tr><th valign="top">Sub-Domain</th><th valign="top">Description</th></tr></thead><tbody><tr><td valign="top"><mark style="color:$primary;"><strong>A1.1</strong></mark><strong> Identity</strong></td><td valign="top">Purpose, values, principles, narrative identity, naming conventions</td></tr><tr><td valign="top"><mark style="color:$primary;"><strong>A1.2</strong></mark><strong> Strategic</strong></td><td valign="top">Vision, mission, strategic objectives, value model, competitive positioning</td></tr><tr><td valign="top"><mark style="color:$primary;"><strong>A1.3</strong></mark><strong> Operational</strong></td><td valign="top">Governance model, decision architecture, operational parameters, communication protocols</td></tr><tr><td valign="top"><mark style="color:$primary;"><strong>A1.4</strong></mark><strong> Relational</strong></td><td valign="top">Stakeholder commitments, partnership principles, community agreements, boundary definitions</td></tr><tr><td valign="top"><mark style="color:$primary;"><strong>A1.5</strong></mark><strong> Accountability</strong></td><td valign="top">Success metrics, review cadences, accountability structures, transparency commitments</td></tr><tr><td valign="top"><mark style="color:$primary;"><strong>A1.6</strong></mark><strong> Evolution</strong></td><td valign="top">Amendment protocols, version control, sunset provisions, learning integration</td></tr></tbody></table>

Within each sub-domain, L3 Capabilities describe what the organization does (e.g., "Define organizational purpose," "Establish value commitments") and L4 Components are the specific artifacts that fulfill those capabilities (e.g., the Purpose Statement, the Values Declaration). The full 24-component structure across all six sub-domains is detailed in Core Concept 8.

{% hint style="info" %}
**Connections:** Core Concept 8 (Living Charter). B1 Compass reads the Charter to set operational direction. B5 Impact feeds strategic learning back into Charter evolution.
{% endhint %}

### **A2. Protocols**

**Rules and Standards for Coordination**

The governance infrastructure that defines how the organization operates, interacts, and maintains coherence. Protocols are encoded agreements that enable coordination without constant negotiation. They establish the rules of engagement so that people and teams can act autonomously while remaining aligned.

| Sub-Domain                     | Description                                                                         |
| ------------------------------ | ----------------------------------------------------------------------------------- |
| **A2.1 Governance Protocols**  | Decision-making rules, authority structures, escalation paths                       |
| **A2.2 Operational Standards** | Quality standards, performance expectations, compliance requirements                |
| **A2.3 Interaction Protocols** | How teams coordinate, how layers communicate, meeting rhythms                       |
| **A2.4 Ecosystem Protocols**   | Partnership engagement rules, external communication standards, boundary agreements |
| **A2.5 Evolution Protocols**   | How protocols themselves are reviewed, updated, and retired                         |

{% hint style="info" %}
**Connections:** Core Concept 7 (Holistic Modularity) establishes why clean interfaces between modules require explicit protocols. A2 operationalizes the Charter's governance principles (A1) into day-to-day coordination rules. C4 Governance maps the external governance landscape that A2 must account for.
{% endhint %}

### **A3. Security**

**Protection and Resilience**

The infrastructure that protects organizational integrity, ensures trust, and maintains resilience against threats across all four dimensions. Security is not only digital. Physical access, data protection, human safety, and cultural trust all fall within this domain. A security architecture that protects servers but ignores psychological safety is incomplete by Flexflow's definition.

| Sub-Domain                       | Description                                                        |
| -------------------------------- | ------------------------------------------------------------------ |
| **A3.1 Access & Identity**       | Authentication, role-based permissions, who can access what        |
| **A3.2 Data Protection**         | Encryption, privacy compliance, information classification         |
| **A3.3 Threat Management**       | Detection, response protocols, incident handling                   |
| **A3.4 Resilience & Continuity** | Backup systems, disaster recovery, operational continuity planning |
| **A3.5 Trust Infrastructure**    | Audit trails, transparency mechanisms, compliance verification     |

{% hint style="info" %}
**Connections:** Core Concept 10 (Resonance) identifies trust (P.REL) as a precondition for mutual amplification; security failures in any dimension degrade that trust. A4 Data depends on A3 for data protection and governance integrity. A3.5 Trust Infrastructure supports any governance model that requires transparency and verifiable accountability, including cooperative structures.
{% endhint %}

### **A4. Data**

**Organizational Sense-Making Capacity**

The infrastructure for collecting, storing, governing, and deriving intelligence from organizational data. Data is the raw material that feeds sensing, decision-making, and learning across all three layers. Without well-governed data, the cybernetic loop runs on noise rather than signal.

| Sub-Domain                        | Description                                                        |
| --------------------------------- | ------------------------------------------------------------------ |
| **A4.1 Data Architecture**        | Storage, warehousing, data models, infrastructure design           |
| **A4.2 Data Governance**          | Ownership, quality standards, lifecycle management, classification |
| **A4.3 Analytics & Intelligence** | Analysis tools, reporting, dashboards, visualization               |
| **A4.4 Data Integration**         | Pipelines, APIs, cross-domain data flows                           |

**Connections:** Core Concept 4 (Cybernetic Loop) depends on data flowing between layers at sufficient speed and fidelity. A5 AI Engine consumes what A4 produces. C11 Sensors designs what should be measured; A4 provides the infrastructure to measure it. The Log feeds structured event data into A4 for analysis and pattern detection.

### **A5. AI Engine**

**Intelligent Systems**

The infrastructure for integrating artificial intelligence capabilities across the organization, from simple rule-based automation to advanced agentic workflows. Represents the organization's capacity for machine intelligence at any maturity level. Not every organization needs advanced AI. Every organization benefits from understanding where intelligent systems sit in its architecture.

| Sub-Domain                    | Description                                                                |
| ----------------------------- | -------------------------------------------------------------------------- |
| **A5.1 Core AI Capabilities** | Model selection, configuration, adaptation, capability development         |
| **A5.2 Agentic Systems**      | Autonomous workflows, agent architectures, human-AI collaboration patterns |
| **A5.3 Automation Layer**     | Rule-based automation, scheduled processes, triggered workflows            |
| **A5.4 AI Governance**        | Ethical guidelines, bias monitoring, output validation, human oversight    |

**Connections:** Flexflow's AI-native design principle means the architecture is machine-readable from the ground up. The Unified Taxonomy (stable IDs, controlled vocabulary) and the Log (structured event history) enable AI systems to both navigate and learn from the organizational model. A5 works with A4 Data as its input layer and A8 Workflows as its execution layer.

### **A6. Resources**

**Foundational Assets and Capital**

The stewardship of all organizational assets across the full value spectrum. Financial capital is one resource among many. Human capability, intellectual property, physical infrastructure, natural assets, and cultural knowledge are managed as an integrated portfolio, reflecting the Multi-Flow Value Model's recognition that organizations circulate multiple forms of value.

| Sub-Domain                        | Description                                                         |
| --------------------------------- | ------------------------------------------------------------------- |
| **A6.1 Financial Capital**        | Budgets, revenue streams, capital allocation, financial planning    |
| **A6.2 Human Capital**            | Talent, skills inventory, development pathways, capacity planning   |
| **A6.3 Intellectual Capital**     | Knowledge bases, proprietary methods, patents, institutional memory |
| **A6.4 Physical Capital**         | Spaces, equipment, materials, tangible infrastructure               |
| **A6.5 Natural & Shared Capital** | Environmental assets, commons, shared infrastructure                |

The sub-domains above map to the most tangible resource categories. The Multi-Flow Value Model (Core Concept 9) identifies ten forms of value including Social, Cultural, Ecological, Temporal, Reputational, and Democratic flows.&#x20;

Not all value flows require dedicated sub-domains; several are emergent properties tracked through other domains (C5 Flows, B5 Impact) rather than managed as discrete resource pools. The sub-domain structure here is a starting scaffold. Organizations may add resource categories as their value model matures.

{% hint style="info" %}
**Connections:** Core Concept 9 (Multi-Flow Value Model) provides the theoretical foundation. B2 Programs and B3 Projects draw on A6 for resource allocation. A6 spans all four infrastructure dimensions: financial and physical assets are the visible layer, but human capability (Biological) and institutional memory (Cultural) are equally foundational resources.
{% endhint %}

### **A7. Services**

**External Dependencies and Integrations**

The registry and management of all external services, tools, platforms, and integrations the organization depends on. Every organization operates within a web of external dependencies. A7 maps that web, monitors its health, and manages the risks of dependency.

| Sub-Domain                           | Description                                                                     |
| ------------------------------------ | ------------------------------------------------------------------------------- |
| **A7.1 Small-Scale Services**        | Individual tools, utilities, single-purpose SaaS subscriptions                  |
| **A7.2 Mid-Scale Services**          | Integrated platforms, multi-function tools, departmental systems                |
| **A7.3 Enterprise-Scale Services**   | Core business systems, organization-wide platforms, foundational infrastructure |
| **A7.4 Integration Architecture**    | How services connect, API management, data flow between systems                 |
| **A7.5 Vendor & Partner Management** | Service agreements, vendor relationships, dependency monitoring                 |

{% hint style="info" %}
**Connections:** Core Concept 5 (Fractal Organization) is reflected in A7's three-scale service classification: services exist at different scales with different scopes, mirroring the fractal principle. A7.4 Integration Architecture connects directly to A4 Data Integration and A5 AI Engine. The Unified Taxonomy page includes a worked navigational example tracing a path through A7.
{% endhint %}

### **A8. Workflows**

**Repeatable Operational Flows**

The designed, documented, and maintained patterns of operational activity. How work actually moves through the organization, encoded as reusable, composable process modules. Workflows operate across all four infrastructure dimensions: automated workflows are primarily digital, guided workflows involve biological human capacity and judgment, and emergent workflows often crystallize from cultural patterns of interaction.

| Sub-Domain                   | Description                                                                  |
| ---------------------------- | ---------------------------------------------------------------------------- |
| **A8.1 Automated Workflows** | Fully automated processes, scheduled operations, triggered sequences         |
| **A8.2 Guided Workflows**    | Human-in-the-loop processes, decision-supported flows, assisted operations   |
| **A8.3 Emergent Workflows**  | Adaptive processes, context-dependent flows, learning workflows              |
| **A8.4 Workflow Governance** | Design standards, performance monitoring, optimization, lifecycle management |

{% hint style="info" %}
**Connections:** Core Concept 7 (Holistic Modularity) establishes why workflows should be modular and composable with clean interfaces. A8 is the execution surface for A5 AI Engine capabilities. B3 Projects and B2 Programs define what work needs to happen; A8 defines how it happens repeatably. A8.3 Emergent Workflows reflect the living-systems principle that not all operational patterns can or should be pre-designed.
{% endhint %}

{% hint style="warning" %}
The complete list of domains for all the three core layers A-B-C, will be added here soon.
{% endhint %}


---

# 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://www.lumeon.dev/frameworks/flexflow/architecture/domain-reference.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.