# Architecture ### **The structural map of Flexflow. Three layers, twenty-five domains, and a unified taxonomy that makes every element findable, connected, and machine-readable.** The Architecture section is where the framework becomes navigable. The Core Concepts develop the ideas. The Architecture organizes them into a coherent structure you can work with: layers that describe how organizations function, domains that map what each layer contains, and a taxonomy that gives every element a stable address. Start with the Overview to see the whole. Go to the Domain Reference when you need the detail.

Overview

The three Core Layers, how they connect through the cybernetic feedback loop, and why every organization contains all three at every scale./pages/EyR8QwKM5TKgPho4LvGL

Domain Reference

All twenty-five domains across Infrastructure, Operation, and Ecosystem. What each domain covers, its sub-domains, and how it connects to the rest of the architecture./pages/qFSNDVBCttspPTswW8at

Unified Taxonomy

The naming and numbering system that gives every element in Flexflow a stable address. Dual IDs, six hierarchical levels, and a worked example showing how navigation works.

Architecture in Practice

Scenario walkthroughs showing how the layers, domains, and taxonomy work together in real organizational contexts. From founding a startup to redesigning an established organization.

Design Principles

The architectural properties that emerge from Flexflow's design choices. Each principle traced to the Core Concept that produces it.
--- # 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/architecture.md?ask= ``` 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.