Methodology // what we declined to compute

The Refusal Ledger

This site abstains rather than guesses, and that claim is checkable only if the abstentions are on the record. Every time a surface declines to compute an answer it renders a dated receipt in place of the number, and the same record lands here. Ran, filtered, refused: with the ingestion ledger and the exclusion log, this is the third record that makes “trust us” unnecessary.

14,037 refusals on record since 2026-08-03, newest 2026-09-29, across 5 instrumented surfaces. Counted from the persisted events themselves, so this page and the receipts cannot disagree.

Why we refused, in the reasons’ own words

ReasonCountWhat it means
no-cik-match5,984this ticker does not resolve to a company that files with the SEC, so there are no filings to derive an answer from
stale-input5,217the freshest input we have is too old to present as current
required-facts-missing2,833the filings exist but do not contain the specific figures this answer needs
registrant-lookup-unavailable3the SEC ticker-to-company map could not be reached while building this page

By surface

why-moving5,395
float5,217
financials-export2,845
red-flags424
cash-runway156

Only instrumented surfaces appear. A surface absent here has not started recording, which is not the same as a surface that never refuses.

Most recent refusals

DateSurfaceAsked forTickerReason
2026-09-29red-flagsfiling health scorePLTSno-cik-match
2026-09-29why-movingwhy the stock movedMRUSno-cik-match
2026-09-29why-movingwhy the stock movedMEno-cik-match
2026-09-29why-movingwhy the stock movedEXTOno-cik-match
2026-09-29why-movingwhy the stock movedEXTOno-cik-match
2026-09-29why-movingwhy the stock movedMEno-cik-match
2026-09-29why-movingwhy the stock movedEXTOno-cik-match
2026-09-29floatfloat read from shares outstandingAGMBstale-input
2026-09-29why-movingwhy the stock movedVBTXno-cik-match
2026-09-29why-movingwhy the stock movedHAGHYno-cik-match
2026-09-29red-flagsfiling health scoreHLXno-cik-match
2026-09-29red-flagsfiling health scoreHLXno-cik-match
2026-09-29why-movingwhy the stock movedINFIQno-cik-match
2026-09-29red-flagsfiling health scoreHLXno-cik-match
2026-09-29why-movingwhy the stock movedDEFTFno-cik-match
2026-09-29why-movingwhy the stock movedEGIOno-cik-match
2026-09-29red-flagsfiling health scoreHLXno-cik-match
2026-09-29red-flagsfiling health scoreHLXno-cik-match
2026-09-29red-flagsfiling health scoreHLXno-cik-match
2026-09-29floatfloat read from shares outstandingPCstale-input
2026-09-29red-flagsfiling health scorePLUGBUno-cik-match
2026-09-29floatfloat read from shares outstandingISOUstale-input
2026-09-29why-movingwhy the stock movedBPMCno-cik-match
2026-09-29floatfloat read from shares outstandingMAGHstale-input
2026-09-29why-movingwhy the stock movedSHMPno-cik-match
2026-09-29why-movingwhy the stock movedSHMPno-cik-match
2026-09-29red-flagsfiling health scoreTCNNFno-cik-match
2026-09-29why-movingwhy the stock movedSHMPno-cik-match
2026-09-29red-flagsfiling health scorePLTSno-cik-match
2026-09-29why-movingwhy the stock movedKHOBno-cik-match
2026-09-29why-movingwhy the stock movedERJno-cik-match
2026-09-29why-movingwhy the stock movedTRVNno-cik-match
2026-09-29cash-runwaycash runway and dilution riskQQQno-cik-match
2026-09-29cash-runwaycash runway and dilution riskCRNXno-cik-match
2026-09-29why-movingwhy the stock movedREAESno-cik-match
2026-09-29financials-exportfiscal-year statement table (XLSX)FMXrequired-facts-missing
2026-09-29why-movingwhy the stock movedSEELno-cik-match
2026-09-29why-movingwhy the stock movedREAESno-cik-match
2026-09-29floatfloat read from shares outstandingBIDUstale-input
2026-09-29why-movingwhy the stock movedFOLDno-cik-match
Refusal Ledger FAQ

What counts as a refusal?

A request a surface could have answered with a plausible-looking number and deliberately did not: a metric whose required filings are absent, a history too short to mean anything, a sample below our minimum, an input too stale to present as current, or a ticker that resolves to no SEC registrant at all. Each one renders a dated receipt in place of the number, and lands here.

Why are most refusals "no SEC registrant"?

Because that is what people actually type: symbols that do not file with the SEC, foreign listings, crypto tickers, and typos. The honest answer to those is that no filing-derived answer exists, not a number synthesized from somewhere else. The distribution is reported as it is rather than curated into something more flattering.

Is a refusal a bug?

No. It is the designed outcome when the inputs do not support an answer. The bug this page exists to catch is the opposite one: a surface that stops refusing and starts guessing would show up here as a suspicious silence.

Keep going: methodology · ingestion ledger · exclusion log