What an AI-agent-native data platform actually needs
Agents now do the data engineering. The bar for a platform that can run them safely has a name — ADER: Autonomous Data Engineering Readiness — and it comes down to four things: Context, Control, Choice, and Cost.
Four things, above any platform
Governing agents in data engineering takes more than deciding what they may access — it takes governing what they actually do, plus a fourth axis, Cost, that access framing leaves out. And data is not code: each axis bites differently when the work is data, which is why the examples below matter as much as the definitions.
Context (M1–M4)
Context that persists and compounds, not a metadata layer served on request — durable specs, accumulating knowledge, observability, one Intent from build into operate. Why data is different: perfect SQL can still be wrong because of what the data contains — grain, semantics, source quirks.
Control (M5–M8)
Govern what agents do, not just what they can reach. Access control says who can read a table; Control says whether a wrong change can ever ship — gates verify every change by independent execution, and the gate's result decides when work is done. Why data is different: a bad change fails quietly — a bad join drops 10% of rows and the dashboard still renders green.
Choice (M9)
Any model, any cloud, native per Adaptor, any channel — one accountable driver at a time. Cross-platform by construction. Why data is different: code is portable, but data has gravity — the lock-in lives in the warehouse's dialect, governance, and bill.
Cost (M10)
Spend you can see and cap: per-run attribution down to the turn, budgets and caps at the policy point. Why data is different: a runaway loop spends warehouse compute on every scheduled run, not just tokens.
Turning the four Cs into something you can measure
ADER (Autonomous Data Engineering Readiness) turns the four Cs into a measurable capability set, scored 0 to 1.0 on one durable primitive. ADER 1.0 is the complete set — and most platforms land well below it. It breaks into 10 markers and about 30 sub-markers. The framework is ours; every marker is already recognized and practiced in the industry. The contribution is the synthesis: nobody else has assembled the full list and scored platforms against it.
Grounded, not theoretical: poor data quality already costs the average enterprise about $12.9M a year (Gartner), and 40% of enterprise apps will run task-specific AI agents by 2026 (Gartner, up from under 5% in 2025).
The full set, grouped by the four Cs
Full pillar → marker → sub-marker detail lives in the ADER whitepaper.
Context — durable, compounding grounding
| Marker | Name | Why data agents need it |
|---|---|---|
| M1 | Durable requirements & spec-first | Without a durable spec, an agent executes literally and ships the wrong outcome. |
| M2 | Accumulating, portable knowledge | Quirks, house rules, and incident fixes must compound and outlive any session — and survive model and platform changes. |
| M3 | Observability, lineage & documentation | An agent must see the current state — what it did, what the data did, what already exists — before it changes or diagnoses anything. |
| M4 | Full lifecycle on one primitive | An agent that only builds, or only operates, leaves half the lifecycle uncoordinated. |
Control — govern what the agent does
| Marker | Name | Why data agents need it |
|---|---|---|
| M5 | Three-level isolation | A wrong hypothesis must be disposable; without isolation, one wrong action corrupts shared code, compute, or data. |
| M6 | Verification against real data | Silent data failures throw no error — an agent must prove a fix on real data, not tidy unit tests. |
| M7 | In-loop gates + deploy lock | Quality must be enforced as deterministic gates the agent can't skip, not prompt requests it can ignore. |
| M8 | Governed access; data in perimeter | The agent must act under scoped, short-lived credentials, and raw data must never leave the perimeter. |
Choice — reachable anywhere, any model, any platform
| Marker | Name | Why data agents need it |
|---|---|---|
| M9 | Multi-channel, multi-user | Agents must be reachable where the work happens, one accountable driver at a time, surviving a dropped surface. |
Cost — spend visible and capped
| Marker | Name | Why data agents need it |
|---|---|---|
| M10 | Per-run cost attribution & control | Agents scale unpredictably; spend must be attributable and capped before the bill surprises the team. |
Everyone has a data engineering agent. The difference is what it's allowed to do.
Every marker is already practiced somewhere. What's missing is the priority to assemble all ten into one coordinated lifecycle — spec → CI → deploy → operate — above the platform. The mature platforms are strong on observability and governed access (M3, M8) because those are commoditized; they stall on full lifecycle on one primitive (M4) and in-loop gates and a deploy lock (M7), because their agent layers exist to drive consumption of their own platform, not to own the whole requirements → build → deploy → operate lifecycle across platforms. Those two markers are where trust is decided: one primitive spanning build and operate, with gates that verify every change by executing it, is what positions hallucination structurally out of the picture.
The markers also interlock, which is why the list is not a menu. Gates without isolation is a gate with no floor; verification without a durable spec verifies the wrong thing. Give an agent half the list and you don't get half the value — you get silent failure that demos well.
And whoever would assemble the missing pieces is an already overworked data team. Data engineers already lose 53% of their time to maintaining pipelines rather than building new ones (Fivetran, 2026), and spend about 40% of their time troubleshooting data quality — roughly 793 engineering hours a month on the average team (Monte Carlo, 2022). They don't have the time to build and maintain a coordination layer on top of a generic coding agent — and "build it yourself" drifts every time the models change.
Built on these axes, above your platform
Vibedata is the coding agent built to clear the bar, with the world around it that clearing the bar requires — the four Cs delivered above whatever platform you run, on one durable primitive (the Intent — the goal you hand the agent). See how the harness delivers each C on the Product page, or watch the Control markers in action in the sandbox: an isolated run that can't touch production state.
