The First Operating System for Large Language Models
Tools that make
hidden friction visible.
Five worksheets for meetings, 1-on-1s, classrooms, and change management — when dialogue keeps collapsing for no obvious reason.
Why SANA OS exists
Most systems do not collapse because people are wrong.
They collapse because people are certain too early.
When something is unclear, the human brain does not wait. It replaces the unknown with a story.
THE REPLACEMENT HAPPENS INSTANTLY
"This is a bad decision."
"They don't understand."
"This will never work."
The discomfort disappears. The explanation feels complete. But the structure underneath remains unseen.
Over time, this creates a pattern: structural problems become personal conflicts. Questions become accusations. Correction becomes impossible. And the system loses its ability to update itself.
This is not a failure of intelligence. It is a property of human cognition. We are not built to hold uncertainty for long.
SANA OS exists for one purpose: to make it possible to see structure before replacing it with story.
It does not solve the problem for you. It does not decide who is right. It does something much simpler.
It makes the hidden variables visible.
When that happens, something changes.
The argument stops being about people.
It becomes about the system.
That is where real dialogue begins.
The worksheets
Pick the one that fits your situation.
Fill in Step 1. See what happens.
Priority conflicts in meetings rarely come from bad intentions. They come from different pressures — one person protecting a client relationship (Layer B), another protecting system stability (Layer A). This checklist makes those pressures visible before the argument starts.
Step 1 — Confirm the shared goal
Our goal for this session:
Step 2 — What pressures is each person protecting?
Layer A — Survival
Layer B — Narrative
Layer C — Rules
When all three columns are filled, the disagreement usually explains itself.
When someone is struggling, asking "why can't you cope?" reads as a threat. This worksheet reframes the situation as a structural load problem: where does demand exceed supply? The answer is never the person.
Step 1 — Demand vs. Supply
Current workload demand (1–10, briefly note why):
Current supply capacity — time, energy, headcount (1–10):
If demand > supply, the gap is a structural problem — not a personal failing.
Logically correct reforms fail because Layer B (culture) absorbs change at a fixed rate. When change speed exceeds absorption capacity, the system breaks. This checklist diagnoses that gap before deployment.
Step 1 — Define the change
New system / policy / reform:
Rollout speed:
The faster the rollout, the more critical the absorption capacity check.
Instead of judging past actions as "wrong" or "barbaric," reconstruct the environmental pressures that made those actions rational at the time. Separates fact, perception, and record — because people act on perception, not fact.
Step 1 — Choose your mystery
Historical event or decision to explore:
What was the dominant Layer A pressure at the time?
The answer to "why did they act that way?" usually lives in this field.
A quantitative diagnostic for structural stability — not "is this good or bad?" but "where is the load concentrated, and what is the absorption capacity?" Applicable to states, organisations, or communities. A comparison tool, not a prediction tool.
Step 1 — Three-layer assessment (0–5)
A — Survival
B — Narrative
C — Institution
The layer with the lowest score is the structural bottleneck. That is where to look first.
Where does demand structurally exceed supply? RBM does not ask who is responsible — it asks where capacity is overloaded. Suitable for individual stress diagnosis, team workload analysis, and initial organisational dysfunction diagnosis. Use only after Premise Alignment is established.
Step 1 — Define functions
Subject being analysed:
Function A — what output is this system expected to deliver?
Bottleneck = function with the largest Demand − Supply gap. That is where to look first.
For researchers analysing structural collapse in organisations, institutions, and states. RSM maps six functional roles (Decider / Architect / Integrator / Executor / Observer / Auditor) and identifies failure patterns: Role Capture, Architect Isolation, Succession Deficit. Optimally suited for historical case analysis.
⚠ Research use — not for personnel evaluation or organisational consulting
Subject and timeframe:
RSM analyses structural role relationships — not individuals or personalities.
For researchers analysing how beliefs form under pressure. CPM traces the path from unresolved uncertainty (Variable X) through cognitive triggers to narrative substitution or exploratory simulation. Optimally suited for analysing witch hunts, revolutions, ideological transformation, and social movements.
⚠ Research use — not for psychiatric diagnosis or psychological evaluation
Subject and primary Variable X (dominant unresolved uncertainty):
CPM asks how beliefs form — not whether they are correct.
Why they work
Conflict is rarely about the issue.
It is about which layer is under pressure.
Every person operates simultaneously under three layers of pressure. When these conflict — within one person or between two — the brain defaults to cognitive compression: complex reasoning collapses into a simple label. "Wrong." "Lazy." "Obstruction." The argument escalates. The structural cause stays invisible.
Layer A
Survival
Food, sleep, safety, job security. When threatened, everything else stops.
Layer B
Narrative
Identity, values, unwritten rules, belonging. Challenges here feel like physical threats.
Layer C
Institution
Law, policy, KPIs, contracts. Can change overnight — absorbed only at Layer B speed.
For those who want to go further
If using these tools changed
how you see dialogue itself
These worksheets are practical implementations of a broader framework for structural observation. If the premise-first approach resonates with how you want to think and build, the system behind these tools is available here.
Explore SANA OS →