AT

The human protocol

EASE.

The human protocol for data products in the agentic era.
FLUID compiles the data. EASE compiles the people.

Four phases — Educate, Activate, Shape, Embed — that turn a domain from passenger into operator.

The four phases

Educate. Activate. Shape. Embed.

One protocol for people. The centre of gravity shifts phase by phase — from our kitchen to yours — until your domains run the line themselves.

Educate

Chef teaches the room

Activate

Chef cooks with one

Shape

Cook leads, chef coaches

Embed

Chef has left the kitchen

The centre of gravity shifts as the kitchen learns to run itself — ● chef ○ domain.

  1. Phase 1 E

    Educate

    Mise en place. Get the room agreed before the heat goes on.

    Shared vocabulary. What is — and isn't — a data product. Decompose a real use case backwards. The Periodic Table mapped to your sector. The eCoE leads; domain SMEs are guests in the kitchen.

    You walk out with A shared map, a queue of candidate data products, and an aligned room.

  2. Phase 2 A

    Activate

    First service. The thin slice goes out the door.

    The first thin-slice data product in production. One use case live. The eCoE pairs with the domain DPO and Steward — same atomic identity as the eventual full product: same primary key, same contract, fewer protons.

    You walk out with One data product in production, one use case live, a DPO and Steward appointed.

  3. Phase 3 S

    Shape

    The line is running. Many meals from one kitchen.

    Three to five data products live. Peer-reviewed designs. Reuse credits — producing domains earn from consuming domains. Quality gates that hold. The domain DDO leads; the eCoE consults on request.

    You walk out with A working portfolio, a reuse economy, and a domain DDO running the squad.

  4. Phase 4 E

    Embed

    The kitchen runs itself. Chef gone. Dinner served.

    Twenty-plus products. Decentralised. The platform self-serves. Agentic access by default, compliance by design. New data products are designed in the domains, by the domains, with no eCoE in the room.

    You walk out with Data-mesh-at-scale, and the eCoE freed for the next horizon.

Who runs the kitchen

The cast, in plain words.

EASE moves accountability into the business. These are the roles it builds — owned by your domains, not by us.

Domain
A business area that owns its data end to end — Sales, Network, Finance.
eCoE
Enterprise Center of Excellence — the central team that carries the method and transfers it into the domains.
DDO
Domain Data Officer — accountable for a domain's whole portfolio of data products.
DPO
Data Product Owner — owns one data product: its contract, quality and consumers. (Not a Data Protection Officer.)
Steward
Data Steward — curates meaning, quality and policy for the data, day to day.

Why two protocols, not one

Two protocols. One substrate.

FLUID compiles the data into governed, agent-ready products. EASE compiles the people who own them. They are designed to run together — in your domain, with your team.

FLUID Your data Compiles EASE Your people
FLUID The data product Unit of work EASE The domain team
FLUID A contract — fluid.yaml Input EASE A use case + a domain
FLUID Governed, deployed data products Output EASE Owners who run the methodology
FLUID Data agents can't trust Prevents EASE Teams that can't ship
FLUID Snowflake · AWS · GCP · DuckDB Runs on EASE Educate · Activate · Shape · Embed

Compile the data with FLUID. Compile the people with EASE. The two are designed to run together.

The capability matrix

What changes, phase by phase.

A methodology, not a slogan. Ownership, output and governance move on a known curve — so you always know which phase you're in and what "done" looks like.

EASE capability matrix — how ownership, output and governance progress across the four phases.
Capability Educate Activate Shape Embed
Who leads eCoE leads · SMEs guest eCoE + domain DPO pair Domain DDO leads Domain owns · eCoE gone
Data products live 0 — mapped & ranked 1 thin-slice in prod 3–5 in production 20+ across domains
Ownership triad Candidates identified DPO + Steward appointed DDO running the squad Federated DDO/DPO/Steward
Vocabulary & design Shared map built Contract + primary key set Peer-reviewed designs Designed in-domain, no eCoE
Reuse & economics Queue prioritised One use case live Reuse credits in operation Reuse economy at scale
Governance & agents Standards introduced Quality gates seeded Gates that hold Compliance by design · agentic

Educate

Who leads
eCoE leads · SMEs guest
Data products live
0 — mapped & ranked
Ownership triad
Candidates identified
Vocabulary & design
Shared map built
Reuse & economics
Queue prioritised
Governance & agents
Standards introduced

Activate

Who leads
eCoE + domain DPO pair
Data products live
1 thin-slice in prod
Ownership triad
DPO + Steward appointed
Vocabulary & design
Contract + primary key set
Reuse & economics
One use case live
Governance & agents
Quality gates seeded

Shape

Who leads
Domain DDO leads
Data products live
3–5 in production
Ownership triad
DDO running the squad
Vocabulary & design
Peer-reviewed designs
Reuse & economics
Reuse credits in operation
Governance & agents
Gates that hold

Embed

Who leads
Domain owns · eCoE gone
Data products live
20+ across domains
Ownership triad
Federated DDO/DPO/Steward
Vocabulary & design
Designed in-domain, no eCoE
Reuse & economics
Reuse economy at scale
Governance & agents
Compliance by design · agentic

How to get started

EASE in a single
working day.

Walk in with your sector map. Walk out with your first data product designed, drafted, and ready for build. We'll tell you in 30 minutes whether we can help.