ATOM • the four parts

Four parts. Kept separate.

ATOM keeps four things separate that tend to get blurred together. When they blur, a method starts to sound like a product, the delivery scaffolding starts to sound like customer software, and tooling gets implied before anyone has agreed there is a real gap.

Where it starts
Customer reality
PeopleSystemsPoliciesWorkSourcesKPIs
↓
The work itself — always present

The framework

the lens

The concepts, boundaries, and maturity model for making sense of enterprise AI work.

ProducesA shared language for work, context, control, evidence, ownership, and measurement.

The engagement method

the method

How an engagement is scoped, baselined, configured, enabled, read, and pointed at what to build next.

ProducesA staged motion that adapts to each customer.

The tooling — only what is justified

Internal delivery tools

team-side

Baseline builders, inventories, contracts, receipts, readiness gates, readouts.

ProducesConsistent, rigorous delivery; they never become customer software.

Customer software

optional · gated

Source registers, context registries, review workflows, enablement and custom agents.

Enters scope only whenthe tools already owned plus the method leave a real gap.

↓
What it builds toward
A customer-owned work system
Approved contextSafe actionReusable memoryEconomics
Why it matters The framework and the method are always part of the work. The delivery tools keep delivery consistent. The customer software earns its place only when the tools already owned and the process leave a real gap.

ATOM · four parts, one customer-owned work system.

ATOM