| Subject | Status | Report date | Age | Note |
|---|---|---|---|---|
| orders-api | assessed | 2026-08-01 | 13d | — |
| billing | assessed | 2026-07-29 | 16d | — |
| reporting | assessed | 2026-08-06 | 8d | harness pinned 412d |
| legacy-batch | assessed | 2026-08-02 | 12d | harness declared, not bound |
4 of 4 subjects assessed; 0 stale; 0 unreachable.
| Subject | AB | AI | WF | OM | TP | OR | OA | HR | WP | AC | AD | Te | Ob | Gv |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| orders-api | 3 | 3 | 4ᶦ | 3 | 4ᶦ | 3 | 3 | 3 | 3 | 3 | 3 | 4ᶦ | 3 | 4ᶦ |
| billing | 3 | 3 | 4ᶦ | 3 | 4ᶦ | 3 | 3 | 3 | 3 | 2 | 3 | 4ᶦ | 2 | 4ᶦ |
| reporting | 3 | 2 | 3ᶦ | 3 | 3ᶦ | 3 | 3 | 3 | 2 | 2 | 3 | 3ᶦ | 2 | 3ᶦ |
| legacy-batch | 2 | 1 | 1ᵘ | 2 | 1ᵘ | 2 | 2 | 2 | 2 | 1 | 2 | 1ᵘ | 1 | 1ᵘ |
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
| Subject | Habitat maturity mean | Cognitive level | Gap | Regime |
|---|---|---|---|---|
| orders-api | 3.29 | 3 | -0.29 | Coherent |
| billing | 3.14 | 3 | -0.14 | Coherent |
| reporting | 2.71 | 3 | +0.29 | Coherent |
| legacy-batch | 1.50 | 3 | +1.50 | Ambition outpaces enablement |
One team, one way of working, four habitats. The same engineers who sit comfortably Coherent in orders-api are working a full level and a half ahead of their environment in legacy-batch. That is not a capability difference — it is an environment difference, and a single-repository assessment of orders-api would have reported a healthy team and missed it.
Observability, Agent composition — weak in three of four, including subjects where the harness does bind. The shared harness does not supply these, so binding harder will not fix them.
legacy-batch: Workflow, Teams provide, Testing, Governance — all four inherited-unbound. A binding failure, not a team failure. It belongs to whoever owns the harness.
Bind the harness in legacy-batch. The cheapest uplift in the estate, and not a build — the testing policy and governance model already exist. Four dimensions move the day it lands.
Refresh the reporting pin. It is bound, which is the hard part. It is 412 days behind, which is the easy part.
Then lift observability and agent composition in the harness itself — after the binding work, not before, or you improve a harness half the estate cannot see.
The instinct on seeing this matrix is to treat legacy-batch as a struggling team. The provenance marks say otherwise: the capability exists twenty metres away.