What is the Agency Operations Kernel?
Kernel is the provider-independent operational core that keeps durable agency facts coherent across changing tools and product surfaces.
ReadThe operating layer behind the work
Agency operations,
made legible.
Connected tools can move information. Kernel gives that information stable identity, authority, history, and meaning.
Durable meaningKernelprovider-independent
WorkTimePeopleEvidenceTermsCapacityWhy Kernel
Your timer knows time. Your project tool knows tasks. Your accounting platform knows invoices.
None of them, alone, knows the relationship.
Evidence before certainty
Information earns its authority.
Kernel preserves what a provider reported, resolves identity, and accepts operational truth only through explicit policy.
- 01Provider recordWhat the connected system supplied
- 02Raw evidenceThe source preserved with provenance
- 03ObservationA provider-neutral interpretation
- 04BindingIdentity confirmed and reusable
- 05Canonical factAccepted operational truth
- 06ProjectionA useful, rebuildable view
“Fact Promotion” is proposed vocabulary for the authorization between binding and canonical acceptance—not a claim that every module uses one generic command.
Explore the operating model
Start with the distinction that matters.
01
Start Here
Why agencies need an operating layer between connected tools.
3 guides02Organizations and People
Client Accounts, identities, affiliations, roles, and permissions.
1 guide03Work and Commercial Structure
How engagements, projects, tasks, and deliverables fit together.
2 guides04Responsibility, Access, and Capacity
What people owe, what they may do, and when effort is reserved.
2 guides05Connected Systems and Data Authority
Evidence, observations, bindings, canonical facts, and projections.
4 guides06History, Corrections, and Events
How changes stay explicit without silently rewriting the past.
2 guides07Time and Dates
Why one business fact may need several different timestamps.
1 guide08Financial Concepts
Evidence, accepted financial facts, policy, and projections.
1 guide09Communications and Mailboxes
Approved correspondence, mailbox boundaries, and content access.
1 guide10Product and Integration Architecture
Kernel modules, product applications, providers, and contracts.
Framework readyEssential reading
Three ways into the system.
What is the difference between an Engagement and a Project?
An Engagement authorizes and governs work; a Project organizes a bounded unit of delivery inside that Engagement.
ReadHow does a provider record become a canonical fact?
Provider information moves through evidence, normalization, identity resolution, authorization, and only then—when policy allows—canonical acceptance.
ReadA shared operational sentence
“Engagements authorize work; Projects organize work; Tasks execute work; Deliverables embody outcomes.”See the work hierarchy