The Agency Operations Kernel is the provider-independent operational core of the Agency OS ecosystem. It holds durable, confirmed facts that need to remain coherent when applications, interfaces, or connected tools change.
Why agencies need an operational core
An agency can connect a project tool, timer, accounting platform, and mailbox and still have no reliable answer to a basic question: what has the agency actually accepted as true?
Each connected system sees one slice of the relationship. Kernel provides stable identities, explicit commands, authorization, history, and bounded canonical modules without pretending every imported record is trustworthy.
For example, a time record may originate in Chronos or Clockify. The origin matters for provenance, but the accepted provider-neutral time fact can still refer to the same person, client, engagement, project, and task.
What Kernel is not
Kernel is not one enormous user interface, a generic CRM, or a replacement for every specialist tool. Product applications such as Agency OS, Capacity OS, and Retainer OS provide focused work surfaces over sanctioned contracts.
Kernel is also not universally event-sourced. Its adopted architecture uses authoritative transactional state plus immutable audit and domain events, with replayability claimed only for bounded projections that actually support it.