Publication standard
A case study follows rules for honest reporting, not a visual theme. Choose the form by the question. The house materials, disclosure standard, and page layout stay fixed.
Every case study contains these eight moves. Their order may tighten for the story, but none may disappear silently.
01 / Question
Name the disputed question in one sentence. A topic is not a question.
02 / Answer
Give the bounded answer before the background. State what the evidence does and does not establish.
03 / Scope
Name the population, unit, geography, and observed-through date that bound the claim.
04 / Method
Explain how the evidence was gathered, compared, or constructed. Make the method reproducible enough to challenge.
05 / Evidence
Put receipts beside the claim they support. Numbers carry units, baselines, dates, and run counts.
06 / Misses
Show failed runs, excluded records, unavailable sources, and material uncertainty.
07 / Counter-read
Present the strongest reasonable alternative explanation, not a weak objection.
08 / Decision
End with the action the evidence supports and the observation that would change the conclusion.
Style follows the burden of proof. Use one primary form. If a second is necessary, make it a clearly limited section rather than a second visual identity.
Story order
Claim → source trail → corrected measure → limits → citation-safe wording.
Proof to include
Source list, claim-status labels, corrected chart, quotation guidance.
live exemplarAI out-scores 999 of 1,000 people
Story order
Hypothesis → baseline → protocol → results → misses → decision rule.
Proof to include
Run counts, baseline and treatment measures, precommitted graders, failure ledger.
live exemplarA controlled test of deleting temporary support code
Story order
Observed problem → built artifact → behavior → what it proves → use boundary.
Proof to include
Live prototype, annotated still, before/after view, build record.
live exemplarData quality is the third axis
Story order
Units and baseline → evidence → mechanism → strongest alternative → falsifier → bounded decision.
Proof to include
Price or contract tables, source dates, mechanism diagram, counter-read, watch conditions.
needs an updateCompute is tradable
Source coverage is separate from confidence. Label every material source with one of these terms and an observed-through date.
✓complete
The named source was checked through the stated date and supports the bounded claim.
◐partial
Some required evidence was checked; the missing slice is named beside the claim.
?unknown
The authority surface was unavailable or too stale to support a claim. Unknown is not negative evidence.
The page should feel edited before it feels designed. Prose stays narrow; evidence earns the wider canvas.
Page title
36 / 40 mobile
48 / 52
Section
serif, regular
30 / 36
Subhead
serif, regular
20 / 28
Body
sans, regular
16 / 28
Caption
sans, regular
14 / 20
Evidence label
mono, regular
12 / 16
Values are font size / line height in pixels. No rendered text below 12px. A short hero datum may reach 60px; the title does not.
× don't
Start with a visual skin.
A “Bloomberg style” or “terminal style” page turns decoration into borrowed authority and forces the evidence into the costume.
✓ do
Start with the disputed question.
Choose the spine that can answer it, then render the receipts in the same house materials every other page uses.
Every material claim maps to a source, method, or clearly marked conclusion.
Every number has a unit, baseline, date, and population or run count where relevant.
Misses, exclusions, unavailable evidence, and the strongest counter-read are visible.
The rendered page has no text below 12px, wrong font, clipped text, or horizontal overflow.
Desktop and 390px mobile screenshots have been inspected, not merely generated.
Links, alt text, reduced motion, build output, and the matching Markdown have been verified.
