Sources of truth, memory
L1
Value-First framework
The Five-Layer Model
The Five-Layer Model describes any organization as five layers, stacked bottom-up — from the raw material of the business to the surfaces where humans meet it.
Industrial Age ↔ AI-Native The business world you operate inTrapped ↔ Transformed Who you are / who you become in that world
The Shift Tribal Knowledge → Human Domain ExpertiseFragmented context → Composed context
The five layers are the five layers of an AI-Native Operating System — the operating system is what the five layers compose, not one of them.
The same five layers are present in every organization. What changes between the Industrial Age and the AI-Native world is not which layers exist, but whether they compose.
The stack reads bottom-up: each layer earns the weight of the one above it.
- Inboxes → CRM / CVP
- Spreadsheets → CRM / CVP
- Spreadsheets → ERP
- Slide Decks → Google / Microsoft / GitHub
- PDFs → Google / Microsoft / GitHub
Data, Identity, Context
Sources of truth, memory
What it is
The foundational layer — the org's Data, Identity, and Context, each read at the full breadth of the layer's own name.
- Inboxes → CRM / CVP
- Spreadsheets → CRM / CVP
- Spreadsheets → ERP
- Slide Decks → Google / Microsoft / GitHub
- PDFs → Google / Microsoft / GitHub
- MQL fades
- SQL fades
- BANT fades
- Attribution fades
Customer Value Model
What the data means
What it is
The explicit model of what creates value for your customers, for whom, and why. This is the layer that answers "why does our work matter, and to whom" in operational terms — not as a slogan, but as a structure the rest of the business runs from. In an AI-Native organization, this layer is occupied by the Unified Customer View and the Unified Revenue View.
- MQL fades
- SQL fades
- BANT fades
- Attribution fades
- Subject Matter Experts → Your Humans
- Subject Matter Experts → Your Agents
- Consultants → Your Humans
- Consultants → Your Agents
- Developers → Your Humans
- Developers → Your Agents
Intelligence
Who has context + capability
What it is
The layer that holds the judgment of the business: the pattern recognition, the situational reasoning, the synthesis across context that turns information into a decision. Your Humans and Your Agents hold this layer: Human Domain Expertise, documented and shared, on the human side, and your agents on the technological side, both present in an AI-Native organization.
- Subject Matter Experts → Your Humans
- Subject Matter Experts → Your Agents
- Consultants → Your Humans
- Consultants → Your Agents
- Developers → Your Humans
- Developers → Your Agents
- Manual processes → Safety
- Manual processes → Quality
- Key-person-as-bottleneck → Governance
- Key-person-as-bottleneck → Observability
- KPIs → Observability
- KPIs → Quality
Trust
Why the work can be trusted
What it is
The trust layer, and the one most organizations don't yet have. It lets the layers below interoperate, Layer 3's humans and agents work as a team, and the apps at Layer 5 inherit a trustworthy foundation. Governance writes down who may do what and who approves. Safety guards what must never happen. Quality checks the work before it acts. Observability shows who did what, human or agent, and why.
- Manual processes → Safety
- Manual processes → Quality
- Key-person-as-bottleneck → Governance
- Key-person-as-bottleneck → Observability
- KPIs → Observability
- KPIs → Quality
- Email threads → Customer Value Platform
- Email threads → Workspace UI
- Email threads → Assistant
- Chat (Slack / Teams) → Workspace UI
- Chat (Slack / Teams) → Assistant
- Project tool (Asana / Monday) → Workspace UI
- Website → Public sites & content
- Social posts → Audience touchpoints
- Newsletters → Audience touchpoints
- Your Custom Apps
Interface
Every surface where humans meet you
What it is
Layer 5 is not only internal work tools. It is every surface where a human meets the organization — internal work surfaces (email, chat, project tools, the workspace) and outbound / audience / content surfaces (public sites, social, newsletters, how you show up to an audience).
- Email threads → Customer Value Platform
- Email threads → Workspace UI
- Email threads → Assistant
- Chat (Slack / Teams) → Workspace UI
- Chat (Slack / Teams) → Assistant
- Project tool (Asana / Monday) → Workspace UI
- Website → Public sites & content
- Social posts → Audience touchpoints
- Newsletters → Audience touchpoints
- Your Custom Apps
How leaders use it
Diagnostic
Map your organization against the five layers using the Five-Layer Shift as the reference. Which layers are strong? Which are implicit? Which are held together by tribal knowledge? The diagnostic is the entry point to the program's Mindset work.
Architectural
"Should we add this dashboard?" is a Layer 5 question — and the answer is almost always to fix Layer 4 first. "Should we add another integration?" is a Layer 1 question — and the answer is usually to make the existing data coherent before adding more.
Operational
When something isn't working, the model gives you the question to ask: which layer is producing the problem? Most "AI isn't working" complaints are Layer 1 or Layer 2 problems. Most "we have too many tools" complaints are Layer 4 problems. Most "the team is burning out" complaints are key-person-as-bottleneck — Layer 4 again.
The figure set
