Company OS and operating model
How the customer-owned operating system, operating model, Runtime, and backend fit together.
The operating system is the customer-owned software through which people and AI agents understand, run, and improve a business. Each Continual project contains one operating system for a business or genuinely independent division. Company OS is the short name for that customer-owned artifact after it has been defined; it does not refer to the Continual platform.
The Company Runtime is the technical name for its live implementation. It brings the company's knowledge, business state, capabilities, feedback, permissions, and connections together. Those pieces encode its operating model: what the business knows, how it works, and what can be done. The backend is the source-owned implementation that stores and serves the Runtime.
Why one shared system matters
Most software fragments the business. A CRM knows accounts, a support tool knows tickets, documents explain policy, and people remember the exceptions. Every new automation or agent has to reconstruct the same context and rules.
The operating system makes that business meaning reusable. A decision made in conversation follows the same rules as one made in an app or by an external agent. New capabilities build on what the company already taught the system instead of creating another silo.
What belongs in it
You do not need every piece on day one. A starter proposes a coherent foundation, and the first meaningful system establishes only the parts it needs. Later teams and apps reuse those foundations.
How people and agents use it
The operating system is not a screen. It is the durable software behind several ways of working:
- Conversation is best for intent, judgment, and creating or changing the system.
- The work queue holds exceptions, questions, approvals, and follow-up until they are resolved.
- Apps provide specialized visual interfaces for customers, teams, or the public.
- MCP and project APIs let authorized external agents and software use the same governed contract.
Why the source is yours
Continual implements the Company Runtime as ordinary source, documents, and a project database you own. Code is the implementation—not a required user interface.
- Changes are visible as diffs instead of hidden settings.
- Types, tests, and evaluations catch mistakes before release.
- Branches provide isolated environments for safe changes.
- Every deployed state can be traced, explained, and reversed.
- Technical teams can inspect and extend the system when useful.
Continual does not silently impose a domain model or change production behavior. Starters become source you adopt and control. Durable changes remain explicit, even when an agent creates them.