Diagnosis & Framing
Produce a defensible, fact-first strategic diagnosis that a leadership team or board can act on. Do the work in the order a top-tier consultant would: build the baseline before debating solutions, isolate the one or two constraints that actually bind, surface…
Runs on Jetty's managed sandbox. No setup. Free for your first 10 runs.
Real runs, real outputs.
Meridian — should we raise a $40M Series B to go upmarket?
Structural (not cyclical) deceleration across win rate, CAC, NRR and churn while a PE-backed competitor bundles a free substitute. The diagnosis isolates the binding…
5 steps · start to finish.
- 1Step 1
Setup & Input Guard
▶mkdir -p {{results_dir}}- Read
{{situation}}. If it is empty, whitespace, or still the literal placeholder, fail fast: writevalidation_report.jsonwithstages[0] = {name:"setup", passed:false, message:"situation input missing"},overall_passed:false, and stop. - Read
{{decision}}. If empty, infer the single most consequential decision the situation implies and record it; you will state it explicitly in the Executive Read. - If
init_params.file_pathsis non-empty, read each file and fold its facts into the fact base (label them by source).
Do not start recommending yet. The next step is to separate what you know from what you believe.
- Read
- 2Step 2
Build the Fact Base (separate facts, interpretations, assumptions)
▶Before any analysis, sort everything the situation gives you into three labelled buckets:
- 3Step 3
Write `diagnosis.md` (the three methods, composed)
▶Write {{results_dir}}/diagnosis.md with exactly this structure. Every section is required; tables must have the named columns (the Step 4 validator checks for them).
- 4Step 4
Evaluate, Validate & Iterate (max 3 rounds)
▶Run a programmatic structural check on diagnosis.md and write the result. This does not grade prose taste — it enforces the method's non-negotiables so a weak pass can't slip through.
- 5Step 5
Write Executive Summary
▶Write {{results_dir}}/summary.md: