Reading the score trajectory: why convergence beats absolute fit
A single fit score tells you where a build is. A score trajectory tells you whether it's getting better, plateaued, or regressing — and which dimensions are moving. The second question is usually the more important one.
A fit score of 78 is information. A trajectory of 42 → 65 → 78 is a different kind of information — and usually the more useful kind. The score tells you where the build is. The trajectory tells you whether the agent is converging on something good, stuck on a plateau, or introducing new problems while fixing old ones.
These are different questions. The absolute score is an answer to "is this good?" The trajectory is an answer to "is this getting better, and how fast?" For a multi-call build loop, the second question matters more.
What convergence looks like
A converging trajectory climbs with meaningful steps between calls — 42 → 65 → 78, or 58 → 74 → 82. Each call produces a materially better score. The patches are landing; the agent is applying them correctly and the layout is improving on the dimensions that were flagged.
The step sizes matter. A trajectory of 78 → 79 → 80 looks like convergence but isn't — it's a plateau. Three-point increments across three calls means the patches from the previous call are producing minimal improvement. Either the agent isn't applying them, the high-value patches have been applied and what remains is marginal, or the remaining issues are structural and the current patching isn't reaching them.
A trajectory of 84 → 81 → 79 is regression. The agent is making changes — but the changes are introducing new problems faster than they're fixing old ones. This is often a sign that the agent is applying visual patches to a layout that has a structural problem. Adjusting typography and spacing on a layout that's shaped wrong for the job produces visual polish on a fundamentally misaligned artifact.
Pattern: the trajectory matters more than the number. A score of 84 that came from 42 is a healthy build. A score of 84 that's been at 84 for three calls is stuck. A score of 84 that came from 87 is regressing. Read all three.
Sub-score trajectories are where the diagnosis lives
The aggregate fit score averages across sub-scores, which means a rising aggregate can mask a sub-score that's falling. The diagnostic value is in the per-dimension trajectory, not just the overall number.
If jtbd_alignment is climbing but extraneous_load is flat, the layout is getting structurally better but the friction is persisting. The agent is applying the shape patches but not the ceremony-reduction patches. If hierarchy is improving but density_fit is declining, visual patches are being applied selectively — the important-versus-secondary distinction is improving while the overall density is getting worse.
The most common plateau pattern is jtbd_alignment near-ceiling, extraneous_load stuck. The structure is right. The friction remains. This usually means the layout is correctly shaped for the job but individual interactions — confirms, modals, multi-click paths — haven't been addressed. The patches for these are specific and mechanical; they shouldn't be hard to apply. When they're not landing, it's usually because the agent doesn't have clear enough instructions about what "inline" means for this specific context.
How to break a plateau
A build that's been at 78 → 79 → 80 for three calls is telling you something: the patches being applied are small improvements on areas that were already adequate, while the real problem hasn't been touched.
Read the sub-score breakdown from the most recent call. Find the lowest sub-score. Read the patches that target it. If those patches haven't been applied between the last two calls, that's the blocker — apply them. If they have been applied and the score hasn't moved, the patch may have been applied incorrectly, or the issue may be more structural than the patch described.
Providing more codebase context on the next call helps. If the agent can see the actual component structure, not just a description of it, the patches can be more precise. "Move the action inline" is a valid patch. "Move the action from the modal trigger in row-actions.tsx to the row component in data-table.tsx as a conditional render on row focus" is a patch that the agent can apply without ambiguity.
Reading the first build
The init call score sets expectations. A first-build score of 42 on a complex B2B tool isn't alarming — it means discovery ran, the JTBD was identified, and the layout has significant room to improve. The patches from this call should produce a 20-30 point gain on the second call if applied.
A first-build score of 78 on a simple admin form is expected. There's not much structural work to do; the remaining gains are in visual craft and friction reduction. The trajectory from here will be flatter, and that's fine — the ceiling is closer.
The score trajectory is what makes the build loop useful. Each call tells you more than the previous one, and the pattern across calls tells you more than any individual call.