While a report measures one system, the Executive Report measures the whole unit — subunits included. A consolidated index with the rule printed, a decision matrix per area and assessments with a declared degree of certainty. Ready to print and circulate.
DERIVED FROM THE REPORTS YOU ALREADY HAVE — NO NEW SCAN
Each section answers a decision-maker's question — with the source declared and evidence linked to the originating reports.
Each subunit with its own index, its own coverage, trend and worst dimension named.
The matrix of what was measured — and what is still missing. An empty cell is an invitation, not silence.
Aggregation with the rule printed per row; security aggregates by worst severity.
Three separate layers — measured fact, interpretation and recommendation — with a/b/c paths, including "do not act" with a date.
Authorship per area and silos — with no person's name in the document.
Separation points ready × still coupled; dependency per vendor with measured calls.
Complexity health, runtimes at end of support and known dependency vulnerabilities.
The demand × condition matrix — maintain, invest, contain or modernize — with evidence and a datable cost of waiting.
Convergences between reports and dated external sources — legislation, news, market — plus the company registry record.
Natural owner per role, timeline and expected return — derived from the verdict, never invented.
The rule that runs through the whole document: numbers come from a deterministic scale; the text narrates and the decision is yours.
Measured and citable — every number links to the originating report, section and file.
The interpretation of the facts, always separate from them and marked as interpretation.
Possible paths with consequences — including the path of not acting, with a date.
Opinion only appears with sufficient, convergent evidence. Below the threshold, the sentence is suppressed — and the suppression is declared, with the report that would unlock it.
An automatic reviewer blocks any assessment that cites a number not on the page or claims certainty under suppression. What does not pass, does not publish.
The cost of not acting is always datable (end of support, trend) — never an invented figure.
The document declares the provenance of every extraction: which report, which version, from when.
The limits are part of the document — and every new platform connection shrinks this list, declaredly.
The report probes external sources — legislation, news, market movement — and crosses what it finds with what the code analysis revealed. The crossing becomes a recommendation; it never becomes a score.
In one analyzed unit, the crossing linked two facts: a law about to come into force, found in the external sources — and a critical point flagged by the code analysis, exactly in the area that law reaches.
The recommendation named where to start the adjustments: it was not just technical debt — it was the company's business model that stood exposed if nothing was done before the law took effect.
This kind of finding changes no number in the report — the scores keep coming only from the deterministic scale over the code. It exists to guide decisions, not to grade.
The crossing between the external source and the code finding is only published when the relationship can be established with a degree of certainty. Below that threshold, nothing appears — a speculative link does not enter the document.
Every external fact enters citing its source and date — verifiable like everything else in the document, and clearly separated from what was measured in the code.
The model is simple and printed in the product:
Index, matrices, coverage and sub-indexes are derived from the reports you already have — they update when the reports update, at no additional cost.
The interpretive narrative — diagnosis, assessments and cross-analysis — is generated on demand, always over that moment's set of reports.
If the reports change after the verdict, the document says there is new data — it never pretends the narrative kept up.
The report was submitted to the critique of a real corporate client — and 8 of the 9 points became published improvements.
EXTERNAL CRITIQUE RECEIVED AND ANSWERED IN AUGUST 2026 — EVOLVING UNDER SCRUTINY IS PART OF THE METHOD
Tell us how many systems the unit has and what you need to decide. We build the demo on your context.