Company OS
What the Runline Framework becomes once it is running the institution: Your Company OS, one governed stack, layer by layer.
The Runline Framework is the architecture Runline builds: a set of primitives, domain-specific app templates, AI-native services, protocols, and designs. Company OS is what that framework becomes once it is running the institution, shaped to your Runlines, your Runners, and your people. In these docs: Your Company OS.
It starts with one Runline. A single process, lifted out of the handoffs that used to lose time, run as a governed service with a Prime Runner and a human gate. As the framework weaves deeper, the same discipline gets applied everywhere work stalls between people and systems, until the sum of those Runlines is the operating system the whole institution runs on.
The stack
Governance wraps everything: NCUA, SEC, BSA. Inside it, six layers rise, each standing on the one below.
| Layer | Concept | What lives here |
|---|---|---|
| 6 | Strategy | Goals, tied down through every layer below. Failure to compose is the roadmap. |
| 5 | People & Culture | How people meet, work, coach, and thank each other. The edge, where the model cannot go. |
| 4 | Operational Model | Runlines: the core processes worth compounding, each gated by a human where it counts. |
| 3 | AI Platform | Runners, compute, runtimes, the harness, the models. |
| 2 | Intelligence | Warehouses, the Knowledge Fabric, and the Compounding Loop: work, thought, decisions, and feedback, all kept as data. |
| 1 | Security | Identity, the Grid, audit, telemetry. The floor everything else trusts. |
The engine
An operating system that only stores state goes stale. The Company OS gets measurably better from its own operating history through Compounding Loops: work, thought, decisions, and feedback, each captured as data and fed back so the next pass is smarter than the last. A real loop has to span four things at once, tech, AI, process, and people; a loop that closes on only one of them stalls.
Internals
A few terms live at the institution level, not on the overview:
- Codex: shared operating principles. One canonical reference instead of a departmental copy of the truth.
- Chronicle: visibility across past (audit), present (what's running), and future (scheduled work). Derived from the Work and Decisions streams.
- Console: the cross-org surface for governance and strategy, distinct from the Tower (ops).
The vocabulary
The platform gives you the Runner (the agent) and the Runline (the governed service it operates in). The human counterpart is the human on the Workstream: reviews, redirects, approves. The human steers; a Runner executes.
See Lexicon & Concepts for the full vocabulary, defined by area.