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.

87,864 refusals on record since 2026-08-03, newest 2026-11-14, 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-match57,073this ticker does not resolve to a company that files with the SEC, so there are no filings to derive an answer from
required-facts-missing17,042the filings exist but do not contain the specific figures this answer needs
stale-input13,738the freshest input we have is too old to present as current
registrant-lookup-unavailable11the SEC ticker-to-company map could not be reached while building this page

By surface

financials-export23,533
cash-runway18,605
why-moving16,610
red-flags15,378
float13,738

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-11-14red-flagsfiling health scoreSNUSPHno-cik-match
2026-11-14cash-runwaycash runway and dilution riskSNUSPHno-cik-match
2026-11-14red-flagsfiling health scoreFORDno-cik-match
2026-11-14red-flagsfiling health scoreBZWRno-cik-match
2026-11-14cash-runwaycash runway and dilution riskBZWRno-cik-match
2026-11-14why-movingwhy the stock movedBZWRno-cik-match
2026-11-14cash-runwaycash runway and dilution riskBZWRno-cik-match
2026-11-14red-flagsfiling health scoreBZWRno-cik-match
2026-11-14cash-runwaycash runway and dilution riskMVLLno-cik-match
2026-11-14financials-exportfiscal-year statement table (XLSX)MGFrequired-facts-missing
2026-11-14cash-runwaycash runway and dilution riskSDCno-cik-match
2026-11-14cash-runwaycash runway and dilution riskFFIEno-cik-match
2026-11-14why-movingwhy the stock movedWSLSno-cik-match
2026-11-14cash-runwaycash runway and dilution riskJMBSno-cik-match
2026-11-14cash-runwaycash runway and dilution riskSPLGno-cik-match
2026-11-14cash-runwaycash runway and dilution riskRSPno-cik-match
2026-11-14cash-runwaycash runway and dilution riskADVMno-cik-match
2026-11-14cash-runwaycash runway and dilution riskATXSno-cik-match
2026-11-14cash-runwaycash runway and dilution riskBBJPno-cik-match
2026-11-14why-movingwhy the stock movedCDMOno-cik-match
2026-11-14cash-runwaycash runway and dilution riskFLOTno-cik-match
2026-11-14cash-runwaycash runway and dilution riskDFEMno-cik-match
2026-11-14why-movingwhy the stock movedSWTXno-cik-match
2026-11-14cash-runwaycash runway and dilution riskINTWno-cik-match
2026-11-14floatfloat read from shares outstandingDTEstale-input
2026-11-14cash-runwaycash runway and dilution riskIGIBno-cik-match
2026-11-14why-movingwhy the stock movedBABXno-cik-match
2026-11-14cash-runwaycash runway and dilution riskGDXYno-cik-match
2026-11-14cash-runwaycash runway and dilution riskMSTYno-cik-match
2026-11-14why-movingwhy the stock movedNETIno-cik-match
2026-11-14cash-runwaycash runway and dilution riskSPYVno-cik-match
2026-11-14cash-runwaycash runway and dilution riskNETIno-cik-match
2026-11-14cash-runwaycash runway and dilution riskFIXDno-cik-match
2026-11-14cash-runwaycash runway and dilution riskFENIno-cik-match
2026-11-14why-movingwhy the stock movedWCMIno-cik-match
2026-11-14cash-runwaycash runway and dilution riskBILZno-cik-match
2026-11-14cash-runwaycash runway and dilution riskBMNGno-cik-match
2026-11-14cash-runwaycash runway and dilution riskINTWno-cik-match
2026-11-14cash-runwaycash runway and dilution riskIAGGno-cik-match
2026-11-14cash-runwaycash runway and dilution riskVIAOYno-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