Methodology // our AI, settled by the filings

The filed outcomes our AI reads name, settled by the next filing

Our AI reads may not predict, so they do not say “revenue will grow 10%”. They name scenarios on filed figures instead: “if growth slows from the current 9.7% pace”, “any further sales contraction”, “continued double-digit revenue growth”. Each such scenario is written down by code as one condition on a figure the company's next 10-Q or 10-K reports, and settled when that filing reaches our derivation: the condition held or did not hold. Never a price level. A scenario is not a forecast, so a condition that held is a record of what the filing said, not a score of the AI.

The record (checked 2026-11-05)

10 stored brief and committee reads; 9 name at least one condition, 12 conditions in all. 3 held, 4 did not hold, 5 are pending the next filing and 0 were abstained. No share is printed: 7 settled conditions are below the floor of 20, and a share of so few says little.

ReadWrittenCondition, in codeThe read’s wordsSettled
TSLA committee2026-10-26revenue growth, year over year below 0% in the next 10-K“Profitability is thin, with a 4.1% net margin and EPS of just $1.08, which leaves little cushion if sales keep sliding.”pending: our newest figure was filed 2026-01-29, on or before the read; waiting for the next 10-K
TSLA committee2026-10-26net margin below 4.1% in the next 10-K“If sales keep sliding, earnings could fall faster than revenue and compress the already razor-thin margin.”pending: our newest figure was filed 2026-01-29, on or before the read; waiting for the next 10-K
QCOM brief2026-09-23revenue growth, year over year at or above 10% in the next 10-K“Continued double-digit revenue growth at 13.7% could support the earnings base”did not hold: 10-K filed 2026-11-04, FY ending 2026-09-27: -2.6%
CPRT brief2026-08-02revenue growth, year over year below 9.7% in the next 10-K“At 18.3 times earnings, the valuation leaves less room for error if growth slows from the current 9.7% pace”held: 10-K filed 2026-09-29, FY ending 2026-07-31: 0.4%
CPRT committee2026-08-02revenue growth, year over year at or above 9.7% in the next 10-K“The market cap of $26.96B against $4.65B in revenue and a 18.3x P/E prices in continued growth, yet revenue rose only 9.7% year over year, so any slowdown could pressure the multiple.”did not hold: 10-K filed 2026-09-29, FY ending 2026-07-31: 0.4%
CPRT committee2026-08-02revenue growth, year over year below 9.7% in the next 10-K“At 18.3x earnings and a $26.96B market cap on $4.65B revenue, any slowdown in that single-digit growth rate could pressure the multiple.”held: 10-K filed 2026-09-29, FY ending 2026-07-31: 0.4%
MU committee2026-07-25revenue growth, year over year below 48.9% in the next 10-K“Any slowdown from the 48.9% revenue growth rate would leave little cushion.”did not hold: 10-K filed 2026-10-09, FY ending 2026-09-03: 256.3%
NOW brief2026-07-22revenue growth, year over year at or above 20.9% in the next 10-K“High revenue growth of 20.9% could support continued top-line expansion”pending: our newest figure was filed 2026-01-29, on or before the read; waiting for the next 10-K
PLTR committee2026-07-21revenue growth, year over year below 56.2% in the next 10-K“At 214× earnings, the stock prices in years of flawless execution, making it highly vulnerable to any growth deceleration or disappointment.”pending: our newest figure was filed 2026-02-17, on or before the read; waiting for the next 10-K
NVDA brief2026-07-14revenue growth, year over year at or above 0% in the next 10-K“Strong revenue momentum could sustain further top-line expansion if growth continues”pending: our newest figure was filed 2026-02-25, on or before the read; waiting for the next 10-K
SNDK committee2026-07-14net margin below 0% in the next 10-K“continued losses would invalidate the bull's turnaround framing.”did not hold: 10-K filed 2026-08-17, FY ending 2026-07-03: 56.5%
SNDK committee2026-07-14revenue growth, year over year at or above 10.4% in the next 10-K“Conversely, if revenue growth accelerates toward profitability, the bear's valuation concern eases.”held: 10-K filed 2026-08-17, FY ending 2026-07-03: 175.3%

How a condition is written and settled

  1. Code reads each sentence of a stored brief or committee read. A scenario word near a growth word (slows, decelerates, continues, sustains, accelerates, keeps sliding) becomes a condition on revenue growth; margin compression or continued losses becomes a condition on net margin. A sentence asking whether something will happen commits to no direction and is skipped.
  2. The threshold is the figure the read was given: “slows from 9.7%” is revenue growth below 9.7%. “Double-digit” is 10%. Growth that “continues” with no rate named is growth at or above 0%. One read repeating a condition counts it once.
  3. The condition settles on the first figure our derivation reports from a filing filed after the day the read was written, read from the same cached company card the brief and committee use (no new filing fetch). Before that it is pending. With no prior-year figure, or no named filing, it is abstained with the reason.
  4. The figure is our own: revenue growth year over year, and net income over revenue, from the company's XBRL facts. The basis (fiscal year or trailing twelve months) is the one our derivation uses at settlement.

Reads written from 5 November 2026 also store their conditions beside the read; older reads yield the same conditions from their stored text, because the extraction is a fixed function of it. The same rule as the settlement referee: what could not be settled is counted, never dropped.

Keep going: our AI's figures, checked against our own · the investment committee · the AI Answer Ledger · methodology