Agent OS · Architecture
Four layers, one governance plane.
The page for the architect in the room. Everything here is shared by every application, which is why the security review happens once.
Experience
Each application ships complete journeys, not a chat box. Structured editors for long documents, tables bound to source data, forms for regulated fields, dashboards for state, chat where it earns its place. Humans and agents work in the same surface with the same permissions model.
Workflow
Journeys compose agentic and deterministic steps. Deterministic where the rules are known (structure checks, format validation, publishing gates), agentic where judgment-shaped work happens (drafting, comparison, classification). Every step is logged, versioned and replayable.
Agents
Purpose-built agents rather than one generalist: tool-using agents for system actions, retrieval agents over your document layer, structured-data agents for tables and listings, browser agents for the public record. Each carries evals that run on every workflow change.
Data & knowledge
Connectors into your systems (document and quality management, lab and clinical data, safety databases, RIM and publishing; SharePoint live today; MCP-native, a standard connector in about a week). Ingestion that reads scanned and handwritten records. The guideline corpus, the public record, and your own templates, SOP checklists and past submissions.
The governance plane, under all four.
- Audit trail
- Every run logged; every authored value linked to its source page.
- Version control
- Documents, workflows and configurations, all versioned together.
- Access
- Role-based access and enterprise SSO across every application.
- Evals
- Every workflow carries its eval set; changes don't ship past a regression.
- Credentials
- Brokered at the boundary, never sitting inside a workflow.
Deployment details, data residency and certification status live on Trust and security →
Want the deeper walkthrough?
We'll take your architects through the OS on a live deployment, not slides.
Talk to usYour data stays in your environment. Customer data never trains foundation models.