Foundation
Capabilities in use
I already operate separate data, workflow, agent, tool-access, approval, and observability capabilities across real projects. They provide the evidence base for the broader thesis.
A working thesis by Emil Ingemar Karlsson
Company OS
The operating layer between human intent and autonomous execution.
A Company OS connects people, data, AI agents, workflows, and tools so work can continue across systems—not just inside a chat. It makes autonomy legible: priorities are explicit, access is scoped, consequential actions are governed, and outcomes are measured.
The premise
A model is a capability.
An agent is a worker.
Neither is an organisation.
Companies already have an operating system, even when nobody calls it that: goals, meetings, permissions, processes, software, data, and feedback. Today these parts are fragmented across tools and held together by human attention.
Company OS is my attempt to make that coordination layer programmable. It is not another all-in-one suite that replaces every business tool. It is the connective operating layer across them. The hard problem is reliable progress across boundaries while keeping responsibility clear.
Why I arrived here
Company OS is a synthesis, not a departure.
The name is new. The underlying problems have followed my work from native products through enterprise operations, analytics, governance, and data platforms.
- 01
Product
Native apps and product analytics taught me to connect intent with observed behaviour.
- 02
Operations
Infrastructure, GDPR, and security taught me that reliability needs ownership and visible controls.
- 03
Data
Power BI and Databricks taught me how shared context, models, and feedback support better decisions.
- 04
Autonomy
AI, workflows, and MCP made execution programmable; Company OS coordinates the whole loop.
Reference architecture
Six layers, one operating loop.
Each layer has a different failure mode. Treating them as one “AI agent” hides the interfaces that need to be designed, secured, and measured.
- 01
Intent & priorities
A shared view of goals, constraints, ownership, and what matters now. Autonomy without direction only automates activity.
- 02
Context & memory
Business data, decisions, histories, and live signals made available in a form agents can retrieve and people can inspect.
- 03
Agents & workflows
Specialised roles that plan and execute, combined with deterministic workflows where consistency matters more than improvisation.
- 04
Tools & systems
Scoped access to code, data, communication, and operations through APIs and MCP—not a universal key to the company.
- 05
Approvals & guardrails
Explicit boundaries for money, publishing, production changes, and irreversible actions, with a human decision where judgment matters.
- 06
Outcomes & feedback
Observability, cost, quality, and business outcomes flow back into the system so it can be evaluated and improved.
Autonomy ladder
Autonomy is a progression, not a switch.
Most useful systems combine several levels. High autonomy belongs in well-observed, reversible work; consequential decisions should retain explicit human ownership.
- 01AssistAI helps a person complete a bounded task.
- 02ExecuteA workflow performs a defined process after a trigger.
- 03CoordinateAgents divide work, use tools, and maintain shared state.
- 04OperateThe system finds work, executes it, monitors results, and escalates exceptions.
- 05AdaptPriorities and methods change from measured outcomes within explicit policy.
Foundation, build, direction
A working thesis with a staged plan.
Active development
A coherent operating layer
The current work is to bring those capabilities into a clearer shared model for intent, context, work, permissions, human decisions, and measured outcomes.
Direction
Accountable autonomy
The long-term direction is an organisation that can identify and coordinate bounded work from live signals while keeping ownership, limits, and escalation paths explicit.
Company OS is under active development. For now I am publishing the architectural model, the vision, and the build direction. Deeper implementation details will follow only when the interfaces and operating lessons are stable enough to be useful.
Continue exploring
The thesis and the path behind it.
Read the first operating note, follow the technical journey that led here, or explore the practitioner definition behind the work.