Executive Summary

Overview

The Executive Summary sits at the top of every report because it's the only block designed to be read before anyone has looked at a single finding. It answers one question in isolation: does this workflow need attention right now, or can it wait? Everything below it — the Controls Matrix, Break Points, Cost Hotspots, the full findings list — exists to back up whatever this block says, not to replace it.

It's also the block most likely to be forwarded on its own, to a manager, a client, a teammate who didn't build the workflow. It's built to survive that: short enough to read in full, specific enough that a risk band isn't the only thing anyone takes away from it.

What question it answers

"If I only have ten seconds, what do I need to know?" Not what's wrong in detail — that's what Break Points and the findings list are for — but how bad, in which direction (production reliability versus spend), and what single thing is most responsible for that answer.

How to read it

Two fields set the headline, four more name what's actually driving it.

• productionRisk (critical / high / medium / low) — the single highest Production Impact Tier across every finding in the report. Not an average, not a count: one critical-tier finding is enough to make the whole workflow's productionRisk critical, even if everything else is clean. That's deliberate — the worst single failure mode is what production risk means here.
• costExposure (critical / high / medium / low) — the highest band reached by any one of the twelve Cost Exposure Score factors (see the Cost Risk article for the full breakdown). Like productionRisk, this is a ceiling, not an average — one factor maxing out is enough to move the whole band.
• primaryBottleneck — the title and likely consequence of the single highest-ranked finding in the report. This is effectively Break Point #1, restated here so it's visible without scrolling further.
• primaryReliabilityRisk, primaryCostRisk, primaryObservabilityGap — the top finding within each of those three categories specifically, when one exists. primaryCostRisk only appears once costExposure rises above low; when there's no cost_risk finding to point to directly, it falls back to a plain-language description of whichever Cost Exposure Score factor is driving the band — for example, "Premium model inside loop — Each loop iteration bills at premium token rates" — rather than leaving the field blank.

Example: productionRisk: critical, costExposure: medium, with primaryBottleneck pointing at an unguarded financial write and primaryCostRisk pointing at "Premium model inside loop — Each loop iteration bills at premium token rates." Read together: the workflow's biggest risk is operational — a write that can duplicate or fail silently — and its spend risk, while real, is secondary.

How to decide what to do

Use productionRisk as the gate for urgency, costExposure as the gate for spend review, and treat the primary-* fields as a starting point rather than the full picture.

• productionRisk: critical or high — treat this as a pre-production blocker. Go straight to primaryBottleneck, then to Break Points for the full ranked list, rather than waiting for a full findings review before starting to fix it.
• productionRisk: medium or low with costExposure: critical or high — the workflow probably won't fail outright, but it can get expensive fast. Start at Cost Hotspots instead of Break Points.
• Both low — the Executive Summary is doing its job by telling you nothing is urgent. The rest of the report is still worth a read for maintainability findings, not an emergency response.
• A missing primary-* field isn't an omission. No primaryObservabilityGap means there's no finding in that category — itself useful information.

Related reading

• Break Points — the ranked list primaryBottleneck is drawn from
• Cost Hotspots — where to go when costExposure is elevated
• Overview — how Production Impact Tier and the Cost Exposure Score are calculated