The four typed-dollar columns (recoverable cash · exposure at risk · peer-benchmark gap · not scored) are never summed across types. This was the existing discipline; it is enforced on every aggregation surface.
Phase 524.10 (auditor verdict #2 closure, KOK-F-08) replaces the earlier "keep parent, drop components" rule. The replacement: within each lever family the headline is the largest coherent lever — the maximum of (parent impact, sum of components). The reason: parent and components are dollarized on different denominators (CCC drag on COGS/day base, DSO drift on revenue/day base) and cannot strictly nest just because the underlying day-metrics intersect. For revenue ≫ COGS entities (NVDA), a DSO component dollar can legitimately exceed the CCC parent dollar.
lever_family and lever_role ∈ { parent · component · standalone }. The sum_deduplicated field on every bucket is the auditor-aligned headline:
This reads as "the upper-bound recoverable cash from any single execution path that doesn't double-count" — executing the parent strategy and the component strategy will not double the recovery, so the headline takes the larger of the two coherent measures.
Example. NVDA recoverable findings fire as { CCC parent $232M · DSO component $600M · AP early-pay component $36M }. Gross sum = $869M; components sum = $636M. Deduplicated headline = max($232M, $636M) = $636M.
Every figure inherits the lowest tier among its inputs. A derived_cash value computed on an assumed_baseline reports as assumed_baseline. No more "hard_fact · disclosed inputs" tag on values that were neither disclosed nor calculated from disclosed primaries.
| Tier | Definition | Example |
|---|---|---|
| hard_fact | Disclosed primary data, unmodified. | NVDA revenue $60.92B from the 10-K. |
| derived_cash | Arithmetic on hard_fact inputs only. | Carrying cost = trapped working capital × cost-of-capital. |
| researched_estimate | Third-party / OSINT / supplier-side estimate, not in primary disclosure. | NVDA top-vendor share 59.3% inferred from supply-chain research; peer headcount median. |
| assumed_baseline | Analyst-set threshold or baseline driving the trigger. | DSO "excess days" baseline · 45-day CCC target · 15% inventory-old-stock threshold. |
Legacy bands keyed severity to absolute dollars (>$5M Critical). On a megacap that converts every finding to Critical regardless of materiality. Phase 524.9 keys severity to the ratio of finding to revenue (or working capital / equity where appropriate), with absolute dollars shown alongside.
| Tier | Band | Example |
|---|---|---|
| Critical | > 1.00% of base | Veridian vendor concentration $4.9M on $95M revenue = 5.16% of revenue. |
| Material | 0.25% – 1.00% of base | NVDA CCC drag $232M on $61B revenue = 0.38% of revenue. |
| Monitor | < 0.25% of base | NVDA AP early-pay $36M on $61B revenue = 0.06% of revenue. |
Bands are calibrated against the operator's investment-grade peer set.
For vendor concentration specifically, severity additionally consults concentration depth (Phase 524.11 KOK-F-12 closure, revising Phase 524.10 KOK-F-11): <40% top-vendor share = Monitor · 40-60% = Material · ≥60% sole-source = Critical. The final tier is MAX(materiality_tier, concentration_tier) — both rules can RAISE severity, neither lowers it. A $10B realistic LGD cannot collapse to Monitor merely because concentration is shallow (materiality dominates); equally a sole-source 80% dependency cannot collapse to Monitor merely because its absolute dollar is small (concentration dominates). The earlier MIN rule was rejected by the auditor on exactly this asymmetry.
Honest gap · the MAX-rule is asymmetric by design but ungrounded by outcome data today.
The Phase 85 BrainOutcomeLedger schema accepts confirmed / refuted / uncertain per finding, and the /api/control/brains/observation endpoint accepts writes — but no production code path automatically records the verdict of a KOK-F finding after the operator acts on it. So there is no FP-rate per severity-class measured today, and the MAX ratchet has no symmetric anti-inflation check derived from real outcomes.
Phase 524.23B2 wires the operator confirm/refute UI on every finding and surfaces a per-class FP-rate; until that lands, treat KOK-F-12 as conservative by construction, not validated by feedback. The 22-agent ARIN council brain calibration (Phase 85 / 85b) is a separate ledger; it has writers via /ui/agents-live and is unrelated to KOK-F finding outcomes.
Some detectors are mathematically inapplicable for entire business models. Running them on the wrong vertical produces dollarized findings the engine cannot defend. The matrix below is enforced at dispatcher time; suppression produces a visible NOT_SCORED finding tagged inapplicable (vertical=…).
| Detector | Manufacturing | SaaS | Financial | Retail / Wholesale |
|---|---|---|---|---|
| DSO / receivables long tail | ✓ | ✓ | ✓ | ✓ |
| Inventory aging excess | ✓ | NOT_SCORED | NOT_SCORED | ✓ |
| Cash conversion cycle drag | ✓ | partial (no DIO) | NOT_SCORED | ✓ |
| AP terms mismatch | ✓ | ✓ | ✓ | ✓ |
| Vendor concentration | ✓ | ✓ | ✓ | ✓ |
| Headcount / revenue ratio | ✓ | ✓ | ✓ | ✓ |
| Period-over-period flux | ✓ | ✓ | ✓ | ✓ |
Vendor concentration exposure was historically reported as top_vendor_share × total_spend — i.e. 100% of annual supply through the vendor for a full year. Phase 524.9 replaces that headline with a realistic loss-given-disruption computed as gross × switching-cost / lead-time-gap factor over a typical recovery cycle.
dollar_impact = realistic LGD. gross_dollar_impact is retained as secondary disclosure. The LGD factor scales with concentration depth: 20% baseline; 35% when concentration ≥ 60% (sole-source territory where recovery is materially harder).
Example. AAPL: 35.7% × $140B = $50B gross exposure → $10B realistic LGD at 20% factor. The board reads the realistic number; the gross stays auditable as secondary.
Machine-checked invariants enforced at render time. Behaviour on violation: BLOCK refuses to emit · AUTO-FIX applies a deterministic correction from available data. Every renderer change is diffed against a golden-file regression set before release.
— / blank placeholder where the value exists in the same artifact.AUTO-FIXmay refer, possibly) in a control / audit finding.BLOCK[full text in JSON] marker.AUTO-FIXinput → signed → rendered).AUTO-FIXNO_DATA from a real 0.BLOCK"trapped $X ≤ disclosed $Y ✓" or an explicit "check not run". Silent absence is indistinguishable from "floor not run" and the renderer refuses to emit. Phase 524.14 KOK-F-25 closure.BLOCKThe auditor's exit prescription: "По существу аудит закрыт. Дальше — не новые findings, а регрессионный механизм." Phase 524.15 lands that mechanism. Seven canonical scenarios — five demo clients (Veridian, AAPL, NVDA, MSFT, Cascade) plus two edge cases (no_inputs, dso_floor_fail) — are frozen as input / expected pairs under internal/handlers/testdata/golden/.
EnrichFinding, RealDispatcher, or buildRunResult runs make golden-test. Any drift fails the suite with a structural diff (severity / confidence / lever_role / dollar_impact per finding plus a full JSON dump). A TestPhase52415_GoldenFile_DriftIsDetected meta-test injects a synthetic drift and asserts the comparator catches it — so a silently-broken suite cannot exist.
Regenerating goldens after an intentional change: make golden-update. The Makefile prints the diff for review before commit. The auditor's contract: changes to the surface must be diffed; surface drift must not pass silently.
What's locked. Every Phase 524 rule — typed-dollar discipline (524.9 §1) · max-coherent-lever dedup (524.10 KOK-F-08) · materiality + concentration MAX severity (524.11 KOK-F-12) · vertical applicability (524.9 KOK-F-04) · 4-tier confidence taxonomy (524.9 KOK-F-02) · balance-sheet sanity floor (524.12 KOK-F-17) · realistic LGD on every exposure detector (524.13 KOK-F-20) · always-visible floor (524.13 KOK-F-21) · detector-specific narrative (524.14 KOK-F-24) · WC floor mention (524.14 KOK-F-25 / RND-12) · cross-detector / cross-vertical boilerplate detection (524.12+524.14 / RND-11) · data sufficiency (524.13). Future changes that drift any of these without explicit golden-update will fail.
The four controllable gaps the auditor identified — aggregation integrity, confidence taxonomy honesty, calibration normalization, and render integrity — are closed in code under Phase 524.9. Lock-in tests TestPhase5249_AuditorClosure_* exercise each rule against the live engine. The five reviewed demo runs (Veridian Cloud · Apple · NVIDIA · Microsoft · Cascade Outfitters) re-render under these rules and are available at /ui/clients.
This contract supersedes the implicit methodology used in pre-524.9 artifacts. Where a re-rendered figure differs from a prior version, the auditor-aligned figure governs. Earlier figures remain in the WORM ledger for audit, prefixed with the pre-524.9 generation timestamp.