TechTalk · AI Readiness Portfolio

Parent repo with submodules

platform-group · 2026-08-14
Coverage3 of 3 subjects assessed; 0 stale; 0 unreachable.
Gap spread−0.21 (api) to +0.14 (workers) — range 0.35
Synthetic example — constructed to illustrate the report shape. These figures are invented to show the report shape. They are not a reading of any real estate.

Coverage ledger

SubjectStatusReport dateAgeNote
webassessed2026-08-0410d
apiassessed2026-08-0410d
workersassessed2026-08-059d

3 of 3 subjects assessed; 0 stale; 0 unreachable.

Dimension matrix

SubjectABAIWFOMTPOROAHRWPACADTeObGv
web33434333333324
api33434333333334
workers32434333223224

Level in cell, coloured L1–L5. inherited · inherited-unbound · unmarked is local. Red outline marks the weakest cell in the column among active subjects. Non-active rows are de-emphasised and do not set the ceiling.
AB Agent behaviour · AI Agent input · WF Workflow · OM Operating model · TP Teams provide · OR Output role · OA Output artefact · HR Humans review · WP Work patterns · AC Agent composition · AD Agents… · Te Testing · Ob Observability · Gv Governance

Gap table

SubjectHabitat maturity meanCognitive level GapRegime
api3.213-0.21Coherent
web3.143-0.14Coherent
workers2.863+0.14Coherent

Spread

api -0.21
web -0.14
workers +0.14
-0.26gap = cognitive read − 14-dimension habitat mean+0.19

A narrow spread is the signature of a habitat that genuinely reaches everything it claims to. The same team, working the same way, meets substantially the same environment in all three submodules.

Portfolio regime

Portfolio regime

Federated

Split ceiling

Common weak — enablement backlog

Observability — weak in two of three subjects. The root harness supplies no observability scaffolding, so each submodule invents its own. Fixing it once at the root fixes it three times.

Locally weak — team backlogs

workers: Agent input, Work patterns, Agent composition, Testing. Real but local; they do not generalise.

What this estate should do next

Lift observability at the root, not in each submodule — the binding already works, so a change there propagates without asking three teams to act.

Leave the workers gaps to the workers team. Pulling them into an estate-wide programme would slow the fix and blur who owns it.

Do not chase levels. All three subjects are Coherent; nothing here is out of step with itself.