rb.
$ readiness --help
AI-Based Data Engineering · 18-point framework

The AI-readiness arc: 4 → 18

Six dimensions. Eighteen points. One arc from raw data platform to production-grade AI infrastructure. Every point is a concrete, measurable property of your data estate.

What the score measures

0–6
Foundation required

Data platform can support human workflows but AI agents will fail silently: wrong answers, unauditable outputs, no quality gates.

7–12
Targeted investments

Selective AI use cases are viable. Specific dimensions are blocking production; targeted fixes get you to the next capability tier.

13–18
Production AI ready

AI agents can reason correctly, produce auditable outputs, operate within governance boundaries, and be evaluated for correctness.

The 6 dimensions scored 0–3 each

Each is scored None, Partial, Mostly, or Complete. The six are independent, and a weakness in any one undermines the others, because AI systems expose all six failure modes at once.

D1
Schema Freshness

Column-level descriptions in INFORMATION_SCHEMA, kept current. The model cannot reason correctly about data it cannot describe.

OpsPulse end state 3/3 · addressed in Ch2, Ch8
D2
Semantic Coverage

MetricFlow semantic models and metric definitions. Without semantics, AI generates plausible-but-wrong answers to business questions.

OpsPulse end state 3/3 · addressed in Ch1, Ch4
D3
Test Coverage

dbt data_tests: or equivalent quality assertions. Quality checks have to gate AI inference up front; monitoring after the fact is too late.

OpsPulse end state 3/3 · addressed in Ch9, Ch11
D4
Eval Readiness

Golden datasets, snapshot history, regression harnesses. AI outputs cannot be verified without reference data to compare against.

OpsPulse end state 3/3 · addressed in Ch11
D5
Governance Scope

Column masking policies, row access policies, audit logging. AI agent queries must be governed with the same rigor as human queries.

OpsPulse end state 3/3 · addressed in Ch7, Ch12
D6
Lineage Coverage

Upstream and downstream lineage queryable at column level. Without lineage, AI outputs are unauditable and incidents are undiagnosable.

OpsPulse end state 3/3 · addressed in Ch2, Ch6

The chapter-by-chapter arc

OpsPulse starts at 4/18, a realistic baseline for most enterprise data platforms. Each chapter closes one or more dimension gaps; the score is the state of the platform at the end of that chapter.

4
4/18
ch 1
baseline
8
~8/18
ch 2
+4 catalog
9
~9/18
ch 3
+1 patterns
11
11/18
ch 4
+2 prompting
12
~12/18
ch 5
+1 context
13
~13/18
ch 6
+1 graph
14
~14/18
ch 7
+1 MCP
15
15/18
ch 8
+1 ingestion
16
16/18
ch 9
+1 SQL gen
16
16/18
ch 10
holds
17
17/18
ch 11
+1 evals
18
18/18
ch 12
+1 governance
18
18/18
ch 13
holds
18
18/18
ch 14
complete

Dimension fill map darker = higher

dimensionch1ch2ch3ch4ch5ch6ch7ch8ch9ch10ch11ch12ch13ch14
D1 Schema Freshness12223333333333
D2 Semantic Coverage01122223333333
D3 Test Coverage11122222333333
D4 Eval Readiness11222222223333
D5 Governance Scope11111122222333
D6 Lineage Coverage02222333333333
total4891112131415161617181818
Scores are approximate OpsPulse state at chapter end. Intermediate chapters hold while building enabling infrastructure.

Score your platform two minutes

Select the level (0–3) that best describes your platform for each dimension. Same 18-point checklist as Chapter 1 of the book.

D1Schema Freshness
none
D2Semantic Coverage
none
D3Test Coverage
none
D4Eval Readiness
none
D5Governance Scope
none
D6Lineage Coverage
none
0 / 18foundation required

your weakest dimensions, and where the book closes them

AI-Based Data Engineering, Packt 2026

Score your platform. Then read the book.

Each chapter closes specific dimension gaps in a deliberate order. The OpsPulse arc takes you from wherever you are to 18/18, one concrete pattern at a time.