TechTalk · AI Readiness Assessment

AI Readiness Assessment — re-assessment

Project: ai-readiness-assessment · 2026-06-03
AI Readiness — Habitat Maturity: Level 3 (Regulating)
Next Step / Gap: +1.1 to Level 4 (Orchestrating)
1Dictating
2Commanding
3Regulating← you are here
4Orchestrating→ target
5Supervising
Habitat Maturity (model)Level 3 Cognitive readLevel 4 — Specification-led Habitat Build Gap +1.1 · Ambition outpaces enablement

Progression. The baseline (view) read a coherent L3 (gap +0.2). Enforcing spec-first lifted the cognitive read to L4 — but the operational habitat didn’t move with it, so the gap flipped to +1.1 — ambition outpaces enablement. The discipline jumped; now the habitat must catch up.

A re-assessment of the plugin against its own repository, after spec-first became an enforced discipline (specs 0001–0003, the Spec-first constraint + gate).

Habitat Maturity Profile

Habitat Maturity Level: L3 (mean L2.93) — held back by L2 Testing, Observability, and Agent composition.

Discipline Maturity

Context Engineering
4 / 5
Architectural Constraints
4 / 5 · was 3
Guardrail Design
4 / 5 · was 3

AI Readiness Score — five readiness dimensions

A view over the same evidence; the headline level is the 14-dimension Habitat Maturity.

Context
L4
Conventions
L4
Architectural guidance
L4 · was L3
Guardrails
L3
Agent readiness
L2

Operational Axes (Part D)

Composition
L2
Testing
L2
Observability
L2
Governance
L4 · was L3

Habitat Build Gap

Habitat Maturity Level (model):  L3  (14-dim mean L2.93)
Cognitive read (Parts A–C):      L4
Habitat Build Gap:               +1.07   (cognitive − 14-dim mean)
Interpretation:                  Ambition outpaces enablement

Lifting the spec discipline to L4 moved the cognitive read up; the operational habitat (Testing, Observability, Composition still L2) did not move with it. Not a regression — the expected, healthy consequence of a deliberate discipline jump, and it names the next work: build the habitat the L4 thinking now implies.

Strengths & Gaps

Strengths

  1. Spec-first is lived and enforced (a required gate), with adversarial review at plan approval.
  2. Policy-as-code governance — four required CI gates on a protected main.
  3. The progression was executed spec-first (spec 0002 drove its own change).

Gaps

  1. Operational habitat lags the discipline (Testing / Observability / Composition at L2) — the +1.1 gap.
  2. Thin spec practice (3 specs, 2 about the spec system).
  3. No orchestration acting on specs (the L4→L5 edge).

Prioritised Improvement Plan

Team develops = practice the team builds; Org provides = enablement the organisation supplies.

The gap flipped, so the advice flips — build the habitat your thinking now implies:

  1. Lift Testing off L2 — behavioural/semantic verification (golden-output or LLM-judge for the B/C tiers): Asserting → Verifying.
  2. Lift Observability off L2 — capture agent-activity / cost signals.
  3. Lift Agent composition off L2 — a read-only critic on PRs (primary-plus-critic).

Reading Path

Assessed at L4 — Specification-led. Next read: the Level 5 (systems and orchestration) chapter — specs are in place; the next leverage is agents that orchestrate around them.

Read on Leanpub

Next Steps

The gap is now +1.1 — ambition outpaces enablement: the habitat needs to catch up to the thinking. TechTalk can support a habitat-build engagement on the lagging operational axes — verification depth, observability, and agent composition — so the environment delivers what your L4 specs already imply.

Book a call with TechTalk
thomas.stangl@techtalk.at