Company OS
Lexicon & Concepts
The words we use, defined once, tagged by area.
The vocabulary is precise on purpose. Area sorts each term into Concepts, Data, Security, Infrastructure, Apps, or Approach.
| Term | Area | What it is |
|---|---|---|
| Runline Framework | Concepts | The platform: primitives, domain Runlines, AI-native services, protocols, and designs. Composite of the Grid, Circuit, the Fabric, the Tower, and the Runner fleet. |
| Company OS | Concepts | What the Framework becomes once it is running the institution. In these docs: Your Company OS. Same stack, shaped to your Runlines, your Runners, your people. |
| Interlay | Approach | How we show up. Become the connective tissue across the systems the credit union already runs. Accelerate the flow of information to humans and agents. Not a product. Not a sixth foundation. Circuit moves bytes; Interlay is why those bytes reach the Workstream. |
| Runline | Apps | A governed workflow service for one domain: state, gates, audit, sync. Ships a Prime Runner and a web app. |
| Workstream | Concepts | Container for work inside a Runline. Can be an SOP as code or a loose project. Holds Items. |
| Item | Concepts | Unit of work on a Workstream. Specializes into the nouns of the domain: Loan, Task, Contract, Alert, and so on. |
| Item type | Concepts | Org-scoped key + field_schema + state_model + flags (workable, timeline, gates, record). Loan / Alert / Task are types; schema_version is the compatibility contract. |
| Stream | Concepts | The container for workable Items inside a Runline. |
| Runner | Concepts | An agent operating inside a Runline, executing Items on a Workstream. |
| Prime Runner | Concepts | The durable, named Runner for a domain at a specific institution. The fleet around it is ephemeral. |
| Intelligence | Concepts | Employees + Runners, on the same Workstreams. Not a layer that replaces the department. The point is a credit union 100× more capable, not a smaller headcount. |
| Knowledge Fabric | Data | CDC pipelines, normalized cross-core schemas, cited semantic search. The intelligence foundation. |
| Circuit | Infrastructure | Org nervous system: real-time event / CDC layer moving data across systems. |
| The Grid | Security | AI control plane: auth, rate limits, kill-switch, audit on every agent hop. |
| Identity | Security | Self-hosted, org-scoped auth. The OIDC provider every Runline app authenticates against. |
| Interface | Apps | The web app that ships with each Runline. CUs can also build custom apps on the same primitives for personal views. |
| The Tower | Apps | Cross-cutting observability and command: Runner activity, cost, audit. |
| Harness | Infrastructure | Runtime the Runner fleet executes on. Runner is who; run.sh is where. |
| api.runline.run | Infrastructure | The unversioned API host (https://api.runline.run/items). Zod contract, no OpenAPI as source. |
Company OS internals
Used on the Company OS page. Not required to read the overview.
| Term | Area | What it is |
|---|---|---|
| Codex | Concepts | Shared operating principles. One canonical reference instead of a departmental copy of the truth. |
| Chronicle | Concepts | Visibility across past (audit), present (what's running), future (scheduled work). |
| Console | Apps | Cross-org surface for governance and strategy. Distinct from the Tower (ops). If those two collapse into one app later, this row dies. |
| Compounding Loop | Concepts | Improvement wired into the work: every completed Item becomes training signal for the next one. |
How the four outputs map
What the Framework produces (the Block cut) in our nouns:
| Produce | Our words |
|---|---|
| Capabilities | Runline + Prime Runner + Workstream / Items |
| World model | Knowledge Fabric + Circuit (Interlay into systems you already have) |
| Intelligence | Employees + Runner fleet on Workstreams |
| Interfaces | Per-Runline web app; custom apps on primitives; The Tower |
| Floor | The Grid + Identity |