Reports · Consequences
What the findings mean — for you.
A survey lists what's wrong with the code. The consequences report answers the question you actually have: what does it mean for the business, in money and risk, and what should I do about it? In plain language — no jargon, no dashboard to learn.
What's inside
The condition, the money, and the asks.
Value-at-risk
How much business value is exposed by the state of the code — distinct from rebuild cost. Rebuild cost says what replacing it would take; value-at-risk says what's on the line if you don't act.
The risks to raise
The handful of findings that matter at your altitude — key-person exposure, security gaps, rot in the modules the business depends on — each translated into a plain ask.
Decide and delegate
Each risk arrives as something you can hand to your team: "share ownership of this module", "add a security gate". You decide; they execute; the next survey shows whether it landed.
SAMPLE · CONSEQUENCES SUMMARY
Consequences report — checkout-platform
- Overall condition — Adequate — trending up
- Value at risk — €480K–720K
- Replacement cost (for contrast) — €1.0M–1.6M
- Key-person exposure — 2 modules depend on one person
- Risks to raise — 3 — each with a plain ask
Illustrative. The real report is built from your engagement's signed evidence, pinned to a commit and a rubric version.
Built on evidence, not on a walkthrough
The consequences read is derived from the same signed CAI evidence every other report uses — reproducible, commit-pinned, and verifiable at cai.canine.dev/verify. The plain language changes what the artifact says, never the number.
Know what it means before you sign off on it.
Activate this reportTalk to usPriced per engagement · built on a shared or commissioned evidence package.