← all hypotheses

PMO Weekly Status-Report Claim Autopsy Ledger for Multi-Vendor Programs

killed [TRIANGULATED] filter 7.0/15 spread ±1.5 signals: 2 independent
What is this?
A claim-autopsy ledger for the PMO / program ops lead at a 100-500 person org running 3-8 active strategic programs delivered by external consultancies, SI partners, or contractor pods (£50-500k each). Each Monday the PMO enters the substantive claims from that week's vendor status reports as structured tuples — 'milestone X on track because dependency Y cleared', 'scope still feasible given assumption Z', 'blocker resolved via mitigation M' — typically 10-20 claims per week across the portfolio. AE runs each claim through the 6-pattern autopsy: Concession Laundering on 'on track*' hedges, Cosmetic Confidence on team-vibes justifications, Premise-Conclusion Severing on dependency-to-milestone logic, Temporal & Transmission Blindness on roll-forward dates. Resolution is the next milestone gate, slip notice, or change-order within 2-6 weeks, logged back. Over 1-2 quarters the PMO has a per-vendor, per-pattern, per-project-type ledger that defends renew/scope-down/replace decisions to the exec sponsor. £600-1200/month. Volume is low enough that entry is justified; each claim is multi-variable enough that AE's taxonomy bites on real substance, not pedantic flags on 'will sign'.
Why did we consider it?
PMO weekly claim-autopsy ledger lands AE's taxonomy on the densest natural stream of laundered vendor claims, with externally-validated demand, defensible £600-1200/mo pricing, and async delivery that fits a solo UK operator.
What breaks?
  • Manual Tuple Friction: PMOs capable of translating vague vendor prose into structured logical tuples already know the vendor is lying, making the AE redundant.
  • Political Suicide: Exec sponsors choose the vendors; a PMO generating a ledger proving the sponsor's chosen SI is incompetent creates political blowback, not ROI.
  • Governance vs. Linguistics: As the VA OIG reports show, vendor failures stem from weak structural controls and misaligned incentives, which a linguistic autopsy cannot fix.
Fatal objection: The PMO cannot politically buy a tool whose output indicts the executive who hired the vendors and signs the invoice.
What did we learn?
Killed: fatal_objection_both_confirm.

Filter scores

Five axes, each scored 0-3. Three independent runs by different model perspectives. Median shown.

AxisWhat it measures
data moatDoes this product accumulate proprietary data that compounds?
10x model testDoes a better model make this more valuable, or redundant?
fast feedback loopsCan outputs be graded against reality in <30 days?
solo founder feasibleCan a solo operator build and run this without a team?
AI providers cant eat itDo hyperscalers have structural reasons NOT to build this?
Composite median: 7.0 / 15. Graduation threshold: 9.0. IQR across runs: 1.5.

Evidence

Signal B — Competitor with documented gap

Clarity PPM displays 'schedule dates, work status, and status report indicators across projects' — purely quantitative project-level metrics. It has no capability for decomposing vendor narrative claims into structured tuples, applying rhetorical-pattern taxonomies (concession laundering, premise-conclusion severing, etc.), or building a per-vendor, per-pattern accountability ledger over time.

Signal D — Demand proxy

{"found":true,"summary":"Practitioner and community interest in better PMO reporting quality, vendor governance analytics, and procurement oversight challenges, though none mention claim-level rhetorical analysis specifically.","sources":["https://www.pmi.org/learning/library/anatomy-highly-effective-status-report-2198","https://github.com/topics/pmo","https://www.cappo.org/news/689607/Navigating-Procurements-Biggest-Challenges-Insights-from-the-2024-State-of-Procurement-Survey.htm"],"reason":"PMI [3] publishes guidance on 'creating status reports that get read by stakeholders,' indicating kno…

Evaluation history

WhenStagePhase
2026-05-13 12:18fatal_objectionranked
2026-05-13 12:12filter_scorescored
2026-05-13 12:06filter_scorescored
2026-05-13 10:54filter_scorescored
2026-05-13 10:49evidence_searchargument
2026-05-13 01:48evidence_searchargument
2026-05-12 23:54evidence_searchargument
2026-05-12 22:06evidence_searchargument
2026-05-12 20:24evidence_searchargument
2026-05-12 18:24evidence_searchargument
2026-05-12 16:36evidence_searchargument
2026-05-12 14:48evidence_searchargument
2026-05-12 13:00evidence_searchargument
2026-05-12 11:06evidence_searchargument
2026-05-12 09:24evidence_searchargument
2026-05-12 07:42evidence_searchargument
2026-05-12 05:54evidence_searchargument
2026-05-11 19:54evidence_searchargument
2026-05-11 18:24evidence_searchargument
2026-05-11 16:54evidence_searchargument
2026-05-11 15:24evidence_searchargument
2026-05-11 13:54evidence_searchargument
2026-05-11 12:30evidence_searchargument
2026-05-11 05:54evidence_searchargument
2026-05-11 05:00evidence_searchargument
2026-05-11 04:36evidence_searchargument
2026-05-11 04:12evidence_searchargument
2026-05-11 03:42evidence_searchargument
2026-05-11 03:12evidence_searchargument
2026-05-11 02:42evidence_searchargument
2026-05-11 02:24evidence_searchargument
2026-05-11 02:18evidence_searchargument
2026-05-11 02:12audience_simulationargument
2026-05-11 02:06red_team_killargument
2026-05-11 02:00steelmanargument
2026-05-11 01:57genesisargument