An independent publicationEvery case sourced, dated & graded A–DGet the weekly Casefile →
Standards

Methodology

Every case in the casefile answers three questions: who deployed the agent, what it does, and how strong the evidence is that it worked. We only publish what a source says, and we show you the source.

Header image: Abstract navy grid with a rising gold line chart

Evidence grades

GradeDefinitionCases
Grade ANamed organization, quantified outcome, independent source (news, paper, filing, or customer quote outside vendor marketing).11
Grade BNamed organization with a quantified outcome, from the vendor or the organization's own announcement.126
Grade CNamed organization, no specific outcome (deployment announced only, or only vague qualitative claims).10
Grade DAnonymous or community report, or a demo/concept/product launch with no named deployment. Shown, but labeled and excluded from "proven" filters.5

Rules we apply when grading:

Deployment status

How a case gets in

  1. Collect. Vendor customer stories, press releases, trade press (healthcare and MedTech titles included), research papers, and public developer sources are monitored on a schedule using RSS feeds and official APIs. We respect robots.txt and do not scrape behind logins.
  2. Deduplicate. Multiple articles about the same deployment become one case with multiple sources.
  3. Extract. A model fills the case schema using only the source text. Every factual field must be supported by an exact quote of 40 words or fewer. Fetched pages are treated as untrusted data: the extraction step has no tools and follows no instructions found in content.
  4. Verify. An automated check re-fetches every source and confirms (a) each quote appears verbatim on the page and (b) every number in every reported outcome appears in the cited source. Any mismatch fails the case. Pages that block automated access are checked through a mirror (e.g. Europe PMC for journals) or a dated manual check, recorded in the public repository.
  5. Grade and gate. We assign the grade, then reject anything without a primary source, with fewer than two facts beyond the headline, too similar to an existing case, or making patient-outcome claims without a peer-reviewed or regulatory source.
  6. Human review. During launch, every case is reviewed before publication.
  7. Refresh. Links and quotes are re-verified weekly; the “last verified” date on each case reflects the latest pass.

As of Oct 17, 2026, 152 of 152 published cases passed the latest automated verification.

Hub pages

Industry and role hubs are indexed by search engines only once they contain at least 5 verified cases. Smaller hubs stay visible to readers but carry noindex.

Healthcare and MedTech

We cover operational and commercial workflows. We do not publish PHI, discuss off-label use, or make device or drug efficacy claims. Clinical decision-support cases describe what the tool does and what the organization reported; they are not medical advice.

AI-assistance disclosure

Case summaries are drafted with AI assistance and checked by the verification process above. Outcome figures and quotes are copied from sources, never generated. Each case lists the date it was last verified.

Independence and money

No organization can pay to be included, to change a grade, or to rank higher. Sponsored content is labeled at the placement and flagged in the public data. See our sponsorship policy.

Corrections

Found an error, a newer outcome, or a dead source? See corrections. We aim to fix verified errors within 24 hours and log every change.