You are seeing every checkable call the DeltaSignal archive carries, graded and carded one by one. It matters because the record runs from July 2025, long before the current grading desk existed, and every card quotes the call in the words it was published in.
Grades from the house archive audit, October 2026. Each call grades on its own published terms: its window, its thresholds, its stated test. The 32 true calls with an X proof post stand as entries on the track record page. The SEC filings record stands at atlas7.app/filings.
41 calls. Each resolved as called, on the terms the article itself published. The 32 with an X proof post stand on the track record page; all 41 stand here.
The call, as published: “Outlook (30 Days): Positive bias remains.”
Window, as published: 30 days from publication, 2025-08-01 to ~2025-08-31
How it resolved: End-of-window close above the publication-date close (+3.1%). The mid-window drawdown is printed in the settling event; the grade follows the article's own window and endpoint framing.
The call, as published: “Absent new income streams or regulatory landmines, RIOT will continue accumulating until external events (regulation, market, or liquidity) force a pivot—likely within the next two or three quarters.”
Window, as published: next two or three quarters
How it resolved: Both legs occurred in sequence inside the stated window: continued accumulation first, then an externally driven pivot (AI/HPC demand) funded by treasury sales. No published follow-up answers this article.
No follow-up was published for this call.
The call, as published: “Bullish Path (20%): Services revenue ramps quickly over the next 2–3 quarters; segment reporting emerges; margins expand; equity issuance slows.”
Window, as published: next 2–3 quarters
How it resolved: Windowed path whose measurable legs occurred inside the window: services revenue ramped, segment reporting emerged in the form the article specified, and equity issuance slowed against the article's own Q2 baseline. Funding shifted to convertible debt, which is printed in the settling event. No published follow-up answers this article. Quote verified against the published HTML per the mismatch flag. Caveat on the article's own Q2 revenue figure is in the notes file.
No follow-up was published for this call.
The call, as published: “🟢 Bullish Path — 75% (Upside Acceleration): If the S-4 clears on time, shareholder approvals are strong, and Trump’s network delivers traction, then American Bitcoin doesn’t just launch — it launches as a visionary dual-platform leader.”
Window, as published: September 2025
How it resolved: The observable legs all occurred inside the stated September window: on-time clearance and close, shareholder approval (the merger completed), a September launch, and Trump-network traction on the debut tape. The remaining phrase ('visionary dual-platform leader') is qualitative and is not separately graded; the grade rests on the launch legs, as in C04.
The call, as published: “🟡 Most Likely Path — 85% (September Launch): If the expected sequence plays out: S-4 → Proxy → Vote → Close → Launch, then ABTC trades in September, as filings already imply.”
Window, as published: September 2025
How it resolved: Windowed binary call; ABTC traded in September, on day 3 of the stated month, through the filing sequence the article mapped. The chain (Sep 3 follow-up and both December ledgers) records the same settlement.
The call, as published: “If hype (Trump premium + listing headlines) meets Hut 8’s credibility, then ABTC can spike from ~$1.50 toward $1.90–$2.20.”
How it resolved: Graded through the chain: the Sep 3, 2025 follow-up settles this arc as the realized path, and the debut tape independently confirms a momentum spike (intraday surge, repeated halts, elevated close). The grade is TRUE on the spike condition; the fact that the move outran the $1.90–$2.20 range is printed at full size in the settling event and the follow-up's own words.
The call, as published: “DFDV filed a PRE 14C on Aug 26, 2025. Based on its flawless history, a DEF 14C is almost certain to follow within 10–20 days — meaning by mid-September.”
Window, as published: by mid-September 2025
How it resolved: Windowed, dated, binary filing call; the filing landed on day 10 of the stated 10–20 day window. No published follow-up in the index answers this article, so the grade rests on the filing record alone.
No follow-up was published for this call.
The call, as published: “Regulatory friction or filing delays dominate. CRO trades as a volatility vehicle rather than pre-IPO proxy. Liquidity thins and the band loses reliability.”
How it resolved: Condition occurred on its observable legs: the disjunctive trigger (filing delays) is documented, and the band losing reliability is a dated tape fact (support break Sep 13, 2025, before the market-wide Oct 10 crash). The two matched follow-ups restate the setup but never scored this path; the grade rests on outcome evidence, per the resonance-first rule that the chain is a path, not a filter.
The call, as published: “Expansion (Alt Path): Replication Arrives — 20% probability”
How it resolved: Graded on the inventory's own settling condition: both legs (replication arrives; exclusivity premium narrows) occurred, with dates and figures sourced. No published follow-up ever revisited this grid.
No follow-up was published for this call.
The call, as published: “Fragility (Alt Path): Token and Structure Under Pressure — 15% probability”
How it resolved: Graded on the inventory's own settling condition: token under pressure and SUIG underperformance versus SUI both occurred and are sourced. Note C04 also graded TRUE: the grid's two alt paths were not mutually exclusive ex post (see Flags). No published follow-up ever revisited this grid.
No follow-up was published for this call.
The call, as published: “The last step is direct CRO integration into Truth Social, whether through payments, tipping, or governance inside the platform.”
How it resolved: Discrete observable event, graded as in C04/C05 (no window required where the condition is a binary event): the gems-to-CRO conversion inside Truth Social is direct integration on the article's own terms (rewards/payments inside the platform). No published follow-up in the index answers this article.
No follow-up was published for this call.
The call, as published: “Bearish Tilt — 25% probability. If SUI stagnates or issuance pace runs ahead of appreciation, NAV/share can collapse.”
How it resolved: Graded on the inventory's own settling condition (condition occurred), with the collapse quantified per share so dilution and token decline are not double-counted: SUI per share actually rose (1.14 to 1.34) while its dollar value fell about 62%. No published follow-up ever revisited this grid: FOLLOW-UP MISSING.
No follow-up was published for this call.
The call, as published: “Bearish Tilt — 25% probability. break lower toward sub-$3.40 if issuance pace outruns demand.”
How it resolved: Graded on the inventory's own settling condition (condition occurred): a dated, sourced break to sub-$3.40 closes beginning Sep 22, 2025. The matched follow-up (Sep 17) answered the article before the settling break and asserted the opposite path; it is recorded in the chain, and the grade follows the tape.
The call, as published: “Bullish Break — 65% Direction is upward, but uneven. The re-rate comes when acquisitions and infrastructure show up on the balance sheet.”
How it resolved: Graded on the inventory's own settling condition (condition occurred): deployment into infrastructure on the record plus an upward, uneven re-rate on the tape. Quote verified against the published HTML (mismatch-list article; operative sentence matches).
The call, as published: “Bullish Break — 65% Probability. Liquidity gives Hut 8 first-mover advantage when peers are capital-constrained.”
How it resolved: Graded on the inventory's own settling condition (condition occurred): rapid deployment with first-mover contracting, and an upward break, both sourced. No published follow-up graded this grid; the matched items are listings/restatements only.
The call, as published: “The alert math points to –5% to –10% near-term pressure as issuance continues.”
Window, as published: near-term
How it resolved: Graded on the call's own stated terms: a -5% to -10% near-term move under continuing issuance occurred on the Sep 26, 2025 close (-6.4%). The quick recovery (printed in the settling event) does not unsettle a call that predicted pressure, not a permanent level.
The call, as published: “Bearish Tilt (5%) • Buybacks: Revenues stall, scarcity loop breaks. Scarcity never materializes. WLFI drifts despite branding.”
How it resolved: Graded on the inventory's own settling condition (condition occurred): token drifted down about 72% over 13 months while buyback-and-burn volumes remained a rounding error against circulating supply, so scarcity never materialized. The Oct 4, 2025 follow-up's contrary 'confirmed' framing is recorded, not adopted as evidence.
The call, as published: “Gold above 30 percent of COFER for consecutive quarters”
How it resolved: The article's gradeable stance was negative: the crossover alone is not yet a regime change, and its own test defines what would change that. A year on, the test remains untriggered on every citable figure, so the 'not yet' stance stands. Flagged FOLLOW-UP MISSING in the scored-to-date sense: the test has no window, but its state is checkable at every COFER print and no published follow-up has ever scored it.
No follow-up was published for this call.
The call, as published: “6 percent bearish tilt”
How it resolved: Graded on the inventory's own settling condition: the complex tilted bearish, decisively, in the article's own foresight window: -14.6% from the Nov 13 close to the Nov 21 close, a low of $84,683.99 on Nov 23, and record November ETF outflows. The 6% path is the one that occurred. The December follow-ups are matched above; they restated the article as verified foresight and did not record that the realized path was the 6% leg, which is printed here at full size.
The call, as published: “SEC publishes final guidance confirming tokenized securities remain securities.”
Window, as published: 2027
How it resolved: Graded on the inventory's own settling condition: guidance confirming tokenized securities remain securities was published, in staff-statement form in January 2026 and in a Commission interpretive release in March 2026. The form caveat is printed at full size: the January document is staff guidance, not a Commission rule; the March release is the Commission-level confirmation. No published follow-up recorded this hit, so FOLLOW-UP MISSING.
No follow-up was published for this call.
The call, as published: “2 to 3 consecutive positive BTC ETF flow days”
Window, as published: The first 7 to 10 trading days of January 2026, after desks fully return
How it resolved: Graded on the stance leg, which is the call's operative content: because the full condition set (including the no-fresh-local-high qualifier) was not met, the article's stated position was 'do not chase,' and the Jan 6-8 reversal (+$1.128B out) proved that position right. The failed qualifier is printed at full size in the settling event: the accumulation signal did NOT fire, by ~$185 on the January 5 high.
No follow-up was published for this call.
The call, as published: “The key zone for Bitcoin market cap dominance sits at 57–58%, where prior rotation attempts have repeatedly stalled.”
Window, as published: January 2026
How it resolved: Dominance held the 57-58% zone for the test month and rotation weakened, exactly the article's hold-branch outcome. Measurement variance across providers is printed in the settling event.
No follow-up was published for this call.
The call, as published: “The baseline remains the first path: a headline-driven move that overshoots briefly and then fades”
Window, as published: Monday, January 5, 2026, and the days immediately following
How it resolved: The baseline path (contained Monday, pop fades, no break condition) is what occurred, sourced to the Monday settle and same-day reporting.
No follow-up was published for this call.
The call, as published: “Path A, roughly 25%: a named PDK host appears, access persists, qualification expands, and paid programs emerge.”
How it resolved: Graded on the inventory's own settling condition and the article's own three gates (named PDK host with access; qualification expands; paid programs emerge): all three legs have sourced instances in 2026, the paid leg in its early form (a material supply and licensing agreement in place, Stage 3 paid-program pipeline). Full commercialization has not occurred and is not what the path as extracted requires. No published follow-up graded these paths, so FOLLOW-UP MISSING.
No follow-up was published for this call.
The call, as published: “Path C, roughly 20%: competitors ship first through existing foundry paths.”
How it resolved: Graded on the inventory's own settling condition: competitor EO/optical products shipped first, ahead of any LWLG commercialization, which has still not occurred at the audit date. Note the construction overlap printed in the notes: this path and Path A both realized, because competitor shipment was never exclusive of LWLG's own PDK progress. No published follow-up graded these paths, so FOLLOW-UP MISSING.
No follow-up was published for this call.
The call, as published: “Path 1: The constraint persists Probability: ~45% Tariff rhetoric continues. The dollar remains firm to resilient. Liquidity stays tight. Coordination remains slow or fragmented.”
Window, as published: next 3–6 months
How it resolved: Every leg of the ~45% path occurred over the stated 3-6 month window: tariff rhetoric continued, the dollar stayed firm to resilient, liquidity stayed tight, and coordination remained fragmented. No published follow-up graded these paths, so FOLLOW-UP MISSING.
No follow-up was published for this call.
The call, as published: “Constraining: 10–15%. Rationale: Volatility expands from current compressed levels or the dollar strengthens, tightening financial conditions.”
Window, as published: Short-term (1–3 month horizon)
How it resolved: Window (1-3 months from Mar 17, 2026) closed Jun 17, 2026. The path's stated conditions occurred inside it: volatility expanded from the compressed base, demand weakened relative to supply (record ETF outflows), and the market lost its ability to absorb distribution cleanly (a 22% fall in 19 days to the Jun 6 close). Graded on outcome evidence; the Aug 19 follow-up's contrary self-grade rests on an August move outside the window and is recorded, not adopted.
The call, as published: “Ranging / Neutral: 35% probability”
Window, as published: 1–3 month horizon (from 2026-03-20)
How it resolved: TRUE (condition occurred): over the 1-3 month window AXT's approval flow was inconsistent, inventory built modestly, and backlog grew faster than it converted, which is the ranging path as written. The window's settling print is the Q1 report; the Q2 blowout ($47.6M, reported Jul 30) fell after the window closed on Jun 20, 2026 and is not used here.
The call, as published: “Ranging / Neutral: 55% probability.Persistent power and grid delays plus electrical-component shortages keep deployment timelines stretched; backlog grows faster than revenue without a clear turning point.”
Window, as published: Short-term (1-3 month horizon)
How it resolved: TRUE (condition occurred): persistent delays and shortages kept deployment timelines stretched and backlog outgrew revenue across the whole short-term window, which is the ranging path as written.
No follow-up was published for this call.
The call, as published: “Constraining: 20% probability.Fresh delays or cancellations in 2026-2027 builds make the wait even longer, further pushing back usable capacity and widening the gap between orders and actual money coming in.”
Window, as published: Short-term (1-3 month horizon)
How it resolved: TRUE (condition occurred): the short-term constraining path requires fresh delays or cancellations pushing back usable capacity and widening the orders-to-revenue gap; both are documented in-window. It overlaps the ranging path (C177), whose regime description the same evidence also satisfies; the overlap is a construction finding, recorded in the notes.
No follow-up was published for this call.
The call, as published: “Base case: 45%. Riot remains liquid, relevant, and narrative-supported, but issuer-level stress prevents a clean upgrade.”
Window, as published: Short-term (1-3 months)
How it resolved: TRUE (condition occurred): over the 1-3 month window RIOT remained liquid and narrative-supported while its financial stress prevented a clean structural upgrade, which is the base case as written. Graded on in-window evidence; the Aug 10 lease announcement is excluded from this grade and counted in the long-term paths' interim state.
No follow-up was published for this call.
The call, as published: “Bear case: 25%. Weak Bitcoin, fading AI/HPC enthusiasm, or visible cash-flow pressure pushes investors back toward the stress profile.”
Window, as published: Short-term (1-3 months)
How it resolved: TRUE (condition occurred): the path is disjunctive (weak Bitcoin, fading AI/HPC enthusiasm, or visible cash-flow pressure) and at least two legs fired, with the stated result (investors pushing RIOT back toward the stress profile) visible in the July tape. It overlaps the base case across sub-periods of the window; that construction overlap is recorded in the notes.
No follow-up was published for this call.
The call, as published: “Premium compression risk rises if dilution moves higher, Bitcoin remains below the dilution-adjusted breakeven level, financing gets more expensive, or BTC per assumed diluted share stalls.”
Window, as published: 1–3 months horizon
How it resolved: TRUE (condition occurred): premium compression on higher dilution, Bitcoin below the breakeven level, and more expensive financing, ending with MSTR trading as a volatile Bitcoin proxy at a discount to NAV (0.68x basic mNAV), which is the bear path's end state and beyond it.
No follow-up was published for this call.
The call, as published: “In this path, the event remains active but does not produce enough post-event evidence to support a strong MSTR-specific divergence claim.”
Window, as published: Through T+5
How it resolved: TRUE (condition occurred): through T+5 the post-event evidence did not support a strong MSTR-specific divergence claim, which is exactly the neutral outcome. No published follow-up ever scored the validation window, so follow_up_missing is set.
No follow-up was published for this call.
The call, as published: “In this scenario, MSTR's movement is mostly explained by BTC-linked exposure.”
Window, as published: Through T+5
How it resolved: TRUE (condition occurred): through T+5 MSTR's movement was explained by BTC-linked exposure without independent confirmation separating it. This is the same tape that makes the neutral path (C191) true; the two paths as written are not mutually exclusive, which is recorded as a construction finding in the notes.
No follow-up was published for this call.
The call, as published: “Capping long-end Treasury yields devalues paper currency, while statutory codification directs escaping capital straight into spot ETP rails. Capital will continue exiting negative real yields to capture hard monetary scarcity and decentralized compute infrastructure.”
Window, as published: Aug 20 to Sep 19, 2026 (the article's stated tactical horizon, 0-30 days).
How it resolved: TRUE on the chain's own published terms: the staking article's tactical horizon, its named assets, and its named benchmarks, measured close to close over the full stated window. Follow-up matched (the Aug 28, 2026 Proof of Execution piece links the staking article and audits the forecast), so no FOLLOW-UP MISSING flag.
The call, as published: “Call 2, market vs consensus: the print lands closer to the Kalshi-implied medians (headline ~0.25% to 0.3% MoM, core ~0.2% to 0.25%) than to the consensus forecast (headline +0.4%, core +0.3%).”
Window, as published: Wednesday, September 30, 2026 print; graded Friday, October 2, 2026
How it resolved: Condition occurred on both legs: the prints landed closer to the Kalshi-implied medians than to consensus, measured on the published prints as the article specified (absolute distance). The Oct 3 scorecard graded this call HIT; the audit's independent check of the BEA prints against both benchmarks agrees.
The call, as published: “The call: relief rally, not a bullish trend.”
How it resolved: Stance leg, graded on the C07/C08 precedent in the free-corpus ledger: the call is a standing negative stance (relief rally, not a bull trend) with a public test, and the test state at every check through Oct 17, 2026 still supports it. Zero of three flip conditions met, and the $80.5K clean-close invalidation never triggered, so the relief-rally read stands as published. The chain graded it twice (Oct 12 and Oct 17) with the same result.
The call, as published: “The $81.3K-$83.5K range carries into Monday.”
Window, as published: Into Monday, October 12, 2026
How it resolved: The Monday close settled inside the range, on the closing basis the article itself specified.
The call, as published: “Path B, core warm: core prints 0.3%. Probability: ~25%. The odds of a rate hike at the Oct 27-28 Fed meeting move from 15.5% toward 1 in 3. The 10-year tests 5.34%. Bitcoin tests the $81.3K range low.”
Window, as published: Oct 14, 2026 print and that day's closes; hike-odds leg settles at the Oct 27-28 Fed meeting
How it resolved: The path's defining condition occurred: core printed exactly 0.3%. Its named market legs moved as stated on the intraday/test basis the path used: the 10-year tested 5.34% (5.335% peak) and Bitcoin tested the $81.3K range low (low $81,332.15). Hike odds moved from 15.5% per the article (about 22% in futures reporting) toward and past 1 in 3. Caveat printed at the same size: on a closing basis the yield leg did not hold (close 5.19%), which is why the publication's framework grade was UNTESTED; this grade is for the Path B print-and-test condition as extracted. The extraction notes the hike-odds leg settling at the Oct 27-28 meeting; the odds movement itself occurred at the print.
The call, as published: “The line that settles the rest is $80,500. One clean close below it grades the Bessent Put failed on its price leg and ends the Oct 12 call.”
Window, as published: The week of October 26-30, 2026
How it resolved: Graded the way the Oct 13, 2026 probability paths (C230-C233) were graded: a conditional path grades TRUE when its stated condition occurs inside its window. The $80,500 close-below condition occurred on Oct 26, 2026, so the settlement the article attached to it applies on its own terms: the Bessent Put failed on its price leg and the Oct 12 relief-rally call ended. No article in the Oct 19-29 window reported this settlement (the only later article, Oct 27, is on a different subject), so the item carries FOLLOW-UP MISSING on the article record; the daily Morning Read and scoreboard lanes sit outside this audit's article corpus.
No follow-up was published for this call.
102 calls inside windows that had not closed at the audit date. Each card carries the window and the state of the call when the audit read it.
The call, as published: “SUI adoption strengthens, token price approaches $10. SUIG's NAV expands, and the stock re-rates as the only Nasdaq-listed SUI proxy.”
Window, as published: Advantage window ~12–18 months from 2025-09-06 (to ~2027-03)
State at the audit date, October 29, 2026: Window runs to ~March 2027, so the base case is not yet gradeable as final. The interim trajectory is printed in full: at month 13 the token is 71% below its publication price and roughly 90% below the base case's $10 marker.
The call, as published: “Setup: PQ-resilient chains begin gaining premium flows before 2030, once disclosures hit ETF and custody rules.”
Window, as published: before 2030
State at the audit date, October 29, 2026: Stated window (before 2030) has not closed. The trigger the article itself names (disclosures hitting ETF and custody rules) has not occurred yet, so the path is neither settled nor failed.
The call, as published: “Option A: Status Quo (2025–2029) — 55% BTC and ETH dominance continues near term. Post-quantum risk remains niche in public narratives while custodians and standards bodies work in the background.”
Window, as published: 2025–2029
State at the audit date, October 29, 2026: Stated window (2025–2029) has not closed; grading now would require shortening the article's own horizon (precedent C11-C13). Interim state printed in the settling event. The article states these options are explicitly not mutually exclusive, so they are graded path by path, not as a partition.
The call, as published: “Option B: Regulatory Push (2029–2032) — 70% NIST and related agencies drive adoption. Custodians migrate the resilient cohort. Compliance and disclosure frameworks begin to force the issue.”
Window, as published: 2029–2032
State at the audit date, October 29, 2026: Stated window (2029–2032) has not closed; grading now would require shortening the article's own horizon (precedent C11-C13). Interim state printed in the settling event. The article states these options are explicitly not mutually exclusive, so they are graded path by path, not as a partition.
The call, as published: “Option C: Hardware Breakthrough (2030s) — 20% Quantum progress arrives faster than expected. Dormant ECDSA wallets face real exploitation risk. Governance stress rises. This is the low-probability, high-impact tail.”
Window, as published: 2030s
State at the audit date, October 29, 2026: Stated window (2030s) has not closed; grading now would require shortening the article's own horizon (precedent C11-C13). Interim state printed in the settling event. The article states these options are explicitly not mutually exclusive, so they are graded path by path, not as a partition.
The call, as published: “Option D: Hybrid Drift (2025–2032) — 45% Interim hybrids and loop strategies buy time. They coexist with A and B as the market bridges toward compliance.”
Window, as published: 2025–2032
State at the audit date, October 29, 2026: Stated window (2025–2032) has not closed; grading now would require shortening the article's own horizon (precedent C11-C13). Interim state printed in the settling event. The article states these options are explicitly not mutually exclusive, so they are graded path by path, not as a partition.
The call, as published: “Tokenized Treasury issuance exceeds 50 billion dollars.”
Window, as published: 2026
State at the audit date, October 29, 2026: Window is calendar 2026 per the article's hardening timeline and has not closed. Interim state printed in full: the marker is failing so far and would require more than a tripling in Q4. Final grade after Dec 31, 2026.
The call, as published: “Stablecoin reserve demand pushes tokenized AUM past 200 billion dollars.”
Window, as published: 2027
State at the audit date, October 29, 2026: Window runs to 2027. Interim state printed in full. Final grade in 2027.
The call, as published: “Stablecoin market reaches 2 trillion dollars.”
Window, as published: 2028
State at the audit date, October 29, 2026: Window runs to 2028. Interim state printed in full: the market would need roughly a 6.7x expansion in the remaining window. Final grade in 2028.
The call, as published: “Expect 40 to 60 percent re-rating by 2028 as governance demand accelerates from the 120 billion dollars stablecoin reserve base.”
Window, as published: by 2028
State at the audit date, October 29, 2026: Window runs to 2028. Interim state printed in full: the re-rating band has not been entered at any point since publication. Final grade in 2028. The grade rests on the Coinbase tape only, not on the article's stablecoin-reserve inputs.
The call, as published: “That implies a price corridor between $240,000 and $360,000.”
Window, as published: before mid-2027
State at the audit date, October 29, 2026: Window runs to mid-2027. Interim trajectory printed in full: at the audit date the price is about 67% below the corridor floor, so the path is failing on its own terms so far, but the window governs and it has not closed.
The call, as published: “Scenario 2. Fragmentation (most likely)”
Window, as published: 2025 to 2028
State at the audit date, October 29, 2026: Stated window 2025 to 2028 has not closed; grading now would require shortening the article's own horizon. Interim state printed in the settling event. Note: the grade rests on external interim evidence only, not on the Dual-Dollar series' own internal figures, which extraction flagged as disputed.
The call, as published: “Digital Collateral Surpasses Bank Deposits”
Window, as published: 2028
State at the audit date, October 29, 2026: Window runs to 2028. Interim state printed in full. Final grade in 2028. Note: this call's article is in the Dual-Dollar series, whose internal figures were flagged as disputed in extraction; the grade rests only on the external interim figures above, not on any figure from the article.
The call, as published: “Private Rails Surpass Fed Rails in Settlement Volume”
Window, as published: 2028
State at the audit date, October 29, 2026: Window runs to 2028. Interim trajectory is printed in full: private-rail volume is growing but sits orders of magnitude below the surpass point. Final grade in 2028.
The call, as published: “Scenario 1: The Fusion Dollar (Most Likely)”
Window, as published: 2028 to 2032
State at the audit date, October 29, 2026: Stated window is 2028 to 2032; grading now would require shortening the article's own horizon.
The call, as published: “One G20 admission resets correlations. The market re-prices sovereign hedging.”
Window, as published: 2026
State at the audit date, October 29, 2026: Window is calendar 2026 and has not closed. The specified trigger (a G20 admission) has not occurred through Oct 18, 2026. Final grade after Dec 31, 2026.
The call, as published: “2026 is when the first big country (Saudi, UAE, Singapore, maybe Japan) will very likely say “yes, we hold Bitcoin” on its official balance sheet. Call it 65% odds.”
Window, as published: 2026
State at the audit date, October 29, 2026: Window is calendar 2026 and has not closed. The call's specific event (an official balance-sheet confirmation by a named first major country) has not occurred through Oct 18, 2026; third-party wallet attribution and sovereign-fund ETF stakes are printed in the settling event and are not adopted as the confirmation the article specified. Final grade after Dec 31, 2026.
The call, as published: “1. Boom: AI delivers, energy scales (45%)”
Window, as published: 2026
State at the audit date, October 29, 2026: Window is calendar 2026 and has not closed. Interim trajectory is printed in full; final grade after Dec 31, 2026.
The call, as published: “2. Bottleneck: adoption stalls, overcapacity builds (30%)”
Window, as published: 2026
State at the audit date, October 29, 2026: Window is calendar 2026 and has not closed. Interim evidence is printed in full; the path's full marker set (utilization below 70%, crypto absorbing idle GPU capacity, robotics slippage) cannot be finally graded until the year closes. Final grade after Dec 31, 2026.
The call, as published: “3. Bloodbath — correction and stranded assets (25%)”
Window, as published: 2026
State at the audit date, October 29, 2026: Window is calendar 2026 and has not closed. One trigger leg (capex above $400B) is met at the interim; the settling legs (large losses, funding pullbacks, grid reliability failure, correction) have not occurred through Oct 18, 2026. Final grade after Dec 31, 2026.
The call, as published: “Orderly stabilization (~50%):”
Window, as published: the next year (from 2026-01-26)
State at the audit date, October 29, 2026: Window has not closed. Interim evidence runs against orderly stabilization so far: Q2 2026 GAAP results were obscured by the $12,529M escrowed-shares mark-to-market loss (GAAP net loss $11,033M vs non-GAAP income $2,197M), the opposite of traceable earnings. The path can still be rescued by clean Q3/Q4 prints; grade at Jan 26, 2027.
The call, as published: “Disclosure debt (~35%):”
Window, as published: the next year (from 2026-01-26)
State at the audit date, October 29, 2026: Window has not closed. Interim evidence tracks this path: earnings attribution in Q2 2026 was dominated by a $12,529M non-operating mark-to-market item and Altera deconsolidation / non-controlling-interest adjustments, so attribution is not yet clean and repeatable. Final grade at Jan 26, 2027.
The call, as published: “Another reset (~15%):”
Window, as published: the next year (from 2026-01-26)
State at the audit date, October 29, 2026: Window (the next year from Jan 26, 2026) has not closed. Interim: restructuring charges continued in Q2 2026 ($170M) and a fresh DCAI layoff round was reported in July 2026, so the reset leg is tracking, but the path's break condition (structure stable across multiple reporting periods) cannot be judged until the year closes. Grade at Jan 26, 2027.
The call, as published: “Bullish break: ~30% Requires sustained institutional inflows above $50B annually, effective circulating supply below 1M BTC, easing macro pressure, and volatility compression.”
Window, as published: 6–12 Months
State at the audit date, October 29, 2026: Window runs to Feb 2027 and has not closed. Interim state is against this path so far: H1 2026 ETF flows were net negative (about $5B out) rather than on a $50B annual inflow pace, and the effective-circulating-supply leg (below 1M BTC) was not sourced in this pass. Still pending: flows and price through Feb 2027.
The call, as published: “Ranging / neutral: ~45% Partial macro alignment and thinning supply support rallies, but insufficient capital persistence and elevated volatility cap follow-through.”
Window, as published: 6–12 Months
State at the audit date, October 29, 2026: Window runs to Feb 2027 and has not closed. Interim state is broadly consistent with this base case so far (rallies supported but capped, no sustained follow-through in either direction across the full period, elevated volatility in June). Final grade at Feb 2027.
The call, as published: “Bearish tilt: ~25% Dollar strength, tighter liquidity, or renewed outflows reintroduce drawdown dynamics even if longer-term structure remains intact.”
Window, as published: 6–12 Months
State at the audit date, October 29, 2026: Window (6-12 months from Feb 9, 2026) runs to Feb 2027 and has not closed. Interim state includes a genuine drawdown phase in this path's direction (the May-Jun 2026 fall on record ETF outflows and tighter liquidity), followed by a recovery into October, so the bearish tilt describes part of the window but not yet its settled state. Final grade at Feb 2027.
The call, as published: “Expansionary (Activity-Led Scaling): 20–30%”
Window, as published: 6–12 months (from 2026-02-16)
State at the audit date, October 29, 2026: Window runs to Feb 2027 and has not closed. Interim state partially matches this path (agent usage and credit consumption growing, margins improving), with its retention leg against it: net revenue retention eased to 102% rather than trending higher. Still pending: HubSpot's prints through Feb 2027.
The call, as published: “Ranging (Offsetting Forces): 50–60%”
Window, as published: 6–12 months (from 2026-02-16)
State at the audit date, October 29, 2026: Window runs to Feb 2027 and has not closed. Interim state is tracking closest to this base case (seat/customer growth moderating but not contracting, credit adoption growing, retention near current levels at 102%, revenue growth at the top of the mid-to-high teens in constant currency at 17.5%, margins improving rather than materially shifting). Final grade at Feb 2027.
The call, as published: “Constraining (Seat Compression Dominant): 15–25%”
Window, as published: 6–12 months (from 2026-02-16)
State at the audit date, October 29, 2026: Window (6-12 months from Feb 16, 2026) runs to Feb 2027 and has not closed. Interim state shows early pressure in this path's direction (net additions below expectation, retention down a point, guidance trimmed) but not its settled condition: the customer base still grew 14% YoY, seats did not contract in the sourced record, and margins improved rather than coming under pressure. Final grade at Feb 2027.
The call, as published: “Expansionary (Control Deepens): 25–35%”
Window, as published: 6–12 months (from 2026-02-17)
State at the audit date, October 29, 2026: Window runs to Feb 2027 and has not closed. Interim state is tracking toward this path on all four stated legs (AI + Data Cloud ARR grew materially beyond the roughly $1B base to nearly $3.9B; RPO expanded at or above revenue growth; subscription growth of 11.7% sits near the roughly 10% marker; non-GAAP margin of 34.1% sits at the top of the roughly 33-34% range), but under the window-governs rule the grade stays OPEN until Feb 2027.
The call, as published: “Neutral (Stability Holds): 45–55%”
Window, as published: 6–12 months (from 2026-02-17)
State at the audit date, October 29, 2026: Window runs to Feb 2027 and has not closed. Interim state sits above this path on its AI leg: AI + Data ARR of nearly $3.9B is no longer a small percentage marker against an $11.35B quarter, although RPO in line with revenue, stable margins, and no visible pricing deterioration all match the neutral description. Still pending: Salesforce's prints through Feb 2027.
The call, as published: “Constraining (Abstraction Emerges): 15–25%”
Window, as published: 6–12 months (from 2026-02-17)
State at the audit date, October 29, 2026: Window (6-12 months from Feb 17, 2026) runs to Feb 2027 and has not closed. Interim state is the opposite of this path so far (AI ARR grew more than 210% rather than slowing, RPO growth ran at or above revenue growth, and non-GAAP margin held at 34.1% against the roughly 33-34% baseline, with no sourced discounting shift). Final grade at Feb 2027.
The call, as published: “Expansionary: 30–40% Governance deepens as AI-driven workflow volume scales inside the platform.”
Window, as published: 6–12 Month
State at the audit date, October 29, 2026: Window runs to Feb 2027 and has not closed. Interim state partially matches this path (margins held above the 28-29% range at 29.5%, net new ACV expanded, AI governance products are the company's stated growth driver), with one leg short on the latest print: cRPO growth of 21% ran below subscription revenue growth of 24.5% rather than at or above it. Still pending: ServiceNow's prints through Feb 2027.
The call, as published: “Neutral: 40–50% AI adoption continues, but governance economics remain incremental.”
Window, as published: 6–12 Month
State at the audit date, October 29, 2026: Window runs to Feb 2027 and has not closed. Interim state is broadly consistent with this base case (cRPO growing roughly in line with subscription revenue, attach improving gradually on the AI ACV figures, margins steady to slightly above range). Final grade at Feb 2027.
The call, as published: “Constraining: 20–30% Execution coordination begins migrating outward.”
Window, as published: 6–12 Month
State at the audit date, October 29, 2026: Window (6-12 months from Feb 20, 2026) runs to Feb 2027 and has not closed. Interim state does not match this path: cRPO grew 21% alongside 24.5% subscription growth rather than decelerating away from it on migration outward, net new ACV deals rose about 40%, and the non-GAAP margin held at 29.5%, above the recent 28-29% range rather than drifting below it. Final grade at Feb 2027.
The call, as published: “Centralization: 25–30%”
Window, as published: 6–12 months (from 2026-02-22)
State at the audit date, October 29, 2026: Window runs to Feb 2027 and has not closed. Interim state is tracking toward this path (product growth reaccelerated to 37%, above the 30% marker; retention 126%, at or above the 120% marker; management links AI workloads to the acceleration), with one leg short: RPO growth of 30% ran below revenue growth of 35% rather than at or above it. Under the window-governs rule the grade stays OPEN until Feb 2027.
The call, as published: “Neutral: 50–55%”
Window, as published: 6–12 months (from 2026-02-22)
State at the audit date, October 29, 2026: Window runs to Feb 2027 and has not closed. Interim state sits above this path's ranges on its two headline figures (product growth 37% versus the low-to-mid-20% band; retention 126% versus the 115-118% trend), while margin expansion at a steady pace does match. Still pending: whether growth decelerates into the neutral band by Feb 2027.
The call, as published: “Growth Compression: 20–25%”
Window, as published: 6–12 months (from 2026-02-22)
State at the audit date, October 29, 2026: Window (6-12 months from Feb 22, 2026) runs to Feb 2027 and has not closed. Interim state is the opposite of this path so far (product growth accelerated to 37% rather than decelerating below the low-20% range; retention 126% rather than trending toward 110%). One leg matches the path's description: RPO growth of 30% lagged revenue growth of 35%. Final grade at Feb 2027.
The call, as published: “Scenario 1: Business as Usual, Slightly Better Probability: ~50%”
Window, as published: 6 to 12 months (from 2026-02-25)
State at the audit date, October 29, 2026: Window runs to Feb 2027 and has not closed. Interim state is broadly consistent with this path (double-digit revenue and ARR growth, pricing power not visibly broken), with one printed exception: non-GAAP operating margin at 44% sits below the year-earlier 46.3% rather than holding flat. Final grade at Feb 2027.
The call, as published: “Scenario 2: AI Becomes a Revenue Boost Probability: ~25–30%”
Window, as published: 6 to 12 months (from 2026-02-25)
State at the audit date, October 29, 2026: Window runs to Feb 2027 and has not closed. Interim state partially matches this path: AI-first ARR is now disclosed and large (above $650M, up more than 150% YoY), which is the path's monetization-disclosure marker, but sourced evidence of AI features moving customers to higher tiers and accelerating revenue per user is not yet in the interim record at that specificity. Still pending: Adobe's prints through Feb 2027.
The call, as published: “Scenario 3: Creative Tools Become Interchangeable Probability: ~20–25%”
Window, as published: 6 to 12 months (from 2026-02-25)
State at the audit date, October 29, 2026: Window (6-12 months from Feb 25, 2026) runs to Feb 2027 and has not closed. Interim state shows only one leg of this path (non-GAAP operating margin eased from 46.3% to 44%); retention deterioration and prosumer churn at the scale described are not in the sourced interim record, and revenue and ARR grew double digits. Still pending: Adobe's prints through Feb 2027.
The call, as published: “Scenario 1: Commercial Momentum Continues Probability: ~50%”
Window, as published: 6–12 months (from 2026-02-26)
State at the audit date, October 29, 2026: Window runs to Feb 2027 and has not closed. Interim state does not match this path's central figure: US commercial growth printed 149% YoY in Q2 2026, not the mid-to-high 20% sustain the scenario describes, while government steadiness, margin hold, and free cash flow expansion do match. Still pending: whether growth decelerates into this scenario's range by Feb 2027.
The call, as published: “Scenario 2: AI Deployment Accelerates Probability: ~30%”
Window, as published: 6–12 months (from 2026-02-26)
State at the audit date, October 29, 2026: Window runs to Feb 2027 and has not closed. Interim state is tracking strongly toward this path (larger contracts: 220 deals of $1M+, RDV up 124%, free cash flow margin rising to a $1.22B quarter at a 62% adjusted operating margin), but under the window-governs rule the grade stays OPEN until Feb 2027.
The call, as published: “Scenario 3: Deployment Simplifies Probability: ~20%”
Window, as published: 6–12 months (from 2026-02-26)
State at the audit date, October 29, 2026: Window (6-12 months from Feb 26, 2026) runs to Feb 2027 and has not closed. Interim state is the opposite of this path so far (commercial growth accelerated to 149% YoY rather than slowing below the mid-20% range, and margins expanded rather than flattening), but the final grade waits on the window. Still pending: Palantir's prints through Feb 2027.
The call, as published: “For Anthropic and its frontier peers: Institutional embedding (~45%)”
Window, as published: the next one to two years (from 2026-02-28)
State at the audit date, October 29, 2026: Stated window of one to two years from Feb 28, 2026 has not closed; grading now would require shortening the article's own horizon.
The call, as published: “Political friction, moderated growth (~35%)”
Window, as published: the next one to two years (from 2026-02-28)
State at the audit date, October 29, 2026: Stated window of one to two years from Feb 28, 2026 has not closed; grading now would require shortening the article's own horizon.
The call, as published: “Compound shock (~20%)”
Window, as published: the next one to two years (from 2026-02-28)
State at the audit date, October 29, 2026: Stated window of one to two years from Feb 28, 2026 has not closed; grading now would require shortening the article's own horizon.
The call, as published: “Expansionary Liquidity — 35% Liquidity stabilizes or eases. Real yields soften. ETF inflows resume consistently. Basis spreads widen back toward prior 15–25% ranges. Structured capital re-engages.”
Window, as published: 12–24 Months
State at the audit date, October 29, 2026: Window runs to Mar 2027-2028 and has not closed. Interim state printed in the settling event: inflows did resume consistently for two months (Mar-Apr 2026), then reversed to record outflows in June, so the path's full condition set (including basis spreads widening back toward 15-25%, which this pass did not source) is not the interim state. Still pending: the window's settled liquidity state by Mar 2027-2028.
The call, as published: “Ranging / Transitional — 40% Liquidity remains mixed. ETF flows oscillate. Basis spreads stay compressed but functional. Bitcoin trades with macro sensitivity but without persistent directional pressure.”
Window, as published: 12–24 Months
State at the audit date, October 29, 2026: Window runs to Mar 2027-2028 and has not closed. Interim state is closest to this path so far (flows oscillating, no persistent directional pressure across the full period), but under the window-governs rule the grade stays OPEN until the window closes.
The call, as published: “Constraining Liquidity — 25% Liquidity tightens further. ETF outflows extend beyond the recent ~$3.8B window. Basis compresses materially. Structured unwind continues.”
Window, as published: 12–24 Months
State at the audit date, October 29, 2026: Window (12-24 months from Mar 1, 2026) runs to Mar 2027 at the earliest and has not closed. Interim state printed in the settling event: the June 2026 record outflow month extended well beyond the article's roughly $3.8B reference window at the time, which is this path's direction, but flows oscillated before and after it. Still pending: whether tightening persists as the window's settled state by Mar 2027-2028.
The call, as published: “Expansionary: 45% probability AI infrastructure spending continues expanding and electricity availability becomes the pacing factor for new data centers.”
Window, as published: next 6–12 months
State at the audit date, October 29, 2026: Window runs to Mar 2027 and has not closed. Interim state is tracking toward this path (spending expanding, electricity named as the pacing factor in Oct 2026 reporting), but under the window-governs rule the grade is OPEN until the window closes in Mar 2027.
The call, as published: “Ranging: 35% Efficiency improvements delay the pressure on power systems.”
Window, as published: next 6–12 months
State at the audit date, October 29, 2026: Window runs to Mar 2027 and has not closed. Interim state printed in the settling event: spending and power pressure both kept rising through Oct 2026, with no sourced evidence that efficiency gains have yet delayed the pressure on power systems at system scale. Still pending: the balance of efficiency gains against load growth through Mar 2027.
The call, as published: “Constraining: 20% A physical bottleneck appears earlier than expected.”
Window, as published: next 6–12 months
State at the audit date, October 29, 2026: Window runs to Mar 2027 (6-12 months from Mar 11, 2026) and has not closed. Interim state printed in the settling event: grid and equipment constraints are visibly binding (128-144 week transformer lead times, about half of planned 2026 US capacity delayed), which is this path's stated mechanism, but a final grade waits on the window. Still pending: whether bottlenecks slow deployments at the scale the path describes by Mar 2027.
The call, as published: “Base case (55–70%)”
Window, as published: 6–12 months (from 2026-03-21)
State at the audit date, October 29, 2026: OPEN because the window runs to Mar 2027. Pending: whether higher-bandwidth products keep ramping on schedule with stable or improving margins through the window's end.
The call, as published: “Stress case (30–45%)”
Window, as published: 6–12 months (from 2026-03-21)
State at the audit date, October 29, 2026: OPEN because the 6-12 month window runs to Sep 2026-Mar 2027. Pending: whether the 1.6T-to-3.2T ramp slows or margins compress later in the window.
The call, as published: “Scenario 1: Controlled Pressure Absorption Probability: 60–70%”
Window, as published: 6–12 month horizon (from 2026-03-24)
State at the audit date, October 29, 2026: OPEN because the 6-12 month window runs to Mar 2027. Pending: the full-window state, including whether margins settle back toward the stated band; the overshoot is recorded as an interim deviation in the favorable direction, not graded early.
The call, as published: “Scenario 2: Constraint Escalation Probability: 30–40%”
Window, as published: 6–12 month horizon (from 2026-03-24)
State at the audit date, October 29, 2026: OPEN because the window runs to Sep 2026-Mar 2027. Pending: whether yield challenges at higher speeds widen the supply gap beyond 30% and slow deployment before the window closes; nothing in the evidence so far points that way.
The call, as published: “Expansionary: 65% probability.”
Window, as published: 6–12 months (from 2026-03-28)
State at the audit date, October 29, 2026: OPEN because the 6-12 month window runs to Mar 2027. Pending: whether backlog converts into revenue closer to order demand with hyperscaler mix still rising, which would settle this path true.
The call, as published: “Ranging / Neutral: 25%.”
Window, as published: 6–12 months (from 2026-03-28)
State at the audit date, October 29, 2026: OPEN because the window runs to Mar 2027. Pending: whether backlog stabilizes and converts unevenly (this path), keeps expanding (C175), or converts toward order demand (C173) by the window's end.
The call, as published: “Constraining: 10%.”
Window, as published: 6–12 months (from 2026-03-28)
State at the audit date, October 29, 2026: OPEN because the 6-12 month window runs to Sep 2026-Mar 2027; per the grading rules a path inside its window stays OPEN even when its marker has triggered early. Pending: whether backlog keeps expanding past $7B with revenue lagging, or conversion (the expansionary marker) takes over before the window closes.
The call, as published: “Expansionary: 40% probability.Sustained hyperscaler capex ($820-860B+ in 2027) forces the coordination problems to get solved; backlog starts turning into revenue as the physical systems finally run together smoothly.”
Window, as published: Long-term (6-12 months)
State at the audit date, October 29, 2026: OPEN because the 6-12 month window runs to Apr 2027 and the path turns on 2027 capex and backlog conversion that cannot be observed yet.
The call, as published: “Ranging / Neutral: 35% probability.Deployment improves unevenly across regions and hyperscalers; returns stay concentrated in coordination and efficiency layers while timing-sensitive segments lag.”
Window, as published: Long-term (6-12 months)
State at the audit date, October 29, 2026: OPEN because the 6-12 month window has not closed. Pending: whether uneven deployment with concentrated returns, rather than solved coordination (C179) or persistent structural delay (C181), describes the full window.
The call, as published: “Constraining: 25% probability.Power and component constraints persist at scale, extending the wait; backlog-to-revenue conversion stays structurally delayed, concentrating durable value in early-paid layers only.”
Window, as published: Long-term (6-12 months)
State at the audit date, October 29, 2026: OPEN because the long-term window runs to Oct 2026-Apr 2027. Pending: whether backlog-to-revenue conversion stays structurally delayed through the window's end or a turning point arrives.
The call, as published: “Bear case: 40%. This is the leading long-term risk case until Riot proves financial improvement.”
Window, as published: Long-term (6-12 months)
State at the audit date, October 29, 2026: OPEN because the 6-12 month window runs to Nov 2026-May 2027. Pending: whether financial improvement is proven within the window; if it is not, this path (the article's leading long-term risk case at 40%) is the one that grades true.
The call, as published: “Base case: 35%. Riot remains an incomplete transition.”
Window, as published: Long-term (6-12 months)
State at the audit date, October 29, 2026: OPEN because the 6-12 month window has not closed. Pending: whether weak treasury strength and negative operating cash flow still block a full structural upgrade at the window's end, or the contracted leases convert fast enough to change the state.
The call, as published: “Bull case: 25%. Riot proves that its power assets can become durable AI/HPC infrastructure revenue.”
Window, as published: Long-term (6-12 months)
State at the audit date, October 29, 2026: OPEN because the long-term window runs to Nov 2026-May 2027. Pending: whether contracted megawatts become durable non-mining revenue with improving operating cash flow, stronger treasury coverage, and limited dilution.
The call, as published: “HUT delivers into 2027, Bitcoin remains supportive, the pipeline converts into additional contracted demand, and the market rewards the company with a higher infrastructure multiple.”
Window, as published: next 12 to 18 months
State at the audit date, October 29, 2026: OPEN because the window runs to Jun-Dec 2027 and the path's settling test is delivery into 2027 with a higher infrastructure multiple. Pending: on-time energization, pipeline conversion, and whether the market re-rates HUT as a scarce power platform.
The call, as published: “The company executes, but not cleanly. Timelines slip modestly, Bitcoin remains volatile, and investors wait for cash flow before assigning additional value to the AI-infrastructure story.”
Window, as published: next 12 to 18 months
State at the audit date, October 29, 2026: OPEN because the stated window (next 12 to 18 months, to Jun-Dec 2027) has not closed; the grade follows the window even though the follow-up chain and the tape both show the base case tracking. Pending: whether modest slips and Bitcoin volatility, rather than clean delivery or a 12-month slip, describe the full window.
The call, as published: “Construction slips by 12 months or more, capex rises materially, AI demand cools, financing becomes more dilutive, or Bitcoin weakness compounds the pressure.”
Window, as published: next 12 to 18 months
State at the audit date, October 29, 2026: OPEN because the window runs to Jun-Dec 2027. The bear path requires a 12-month-plus construction slip, materially higher capex, cooling AI demand, more dilutive financing, or compounding Bitcoin weakness leaving HUT treated as a miner with an unfinished AI story; none has occurred, and the financing and contracting markers so far point the other way.
The call, as published: “Scenario 1: Expansionary Integration (42–48%)”
Window, as published: The next few years (the article's next-cycle horizon)
State at the audit date, October 29, 2026: OPEN because the article's window ('the next few years') has not closed. Pending: whether stablecoin settlement, tokenized-Treasury collateral use, and ETF normalization compound into business and institutional dependency on crypto rails. Settles at the end of the article's next-cycle horizon; the article states no date.
The call, as published: “Scenario 2: Functional but Episodic Adoption (38–42%)”
Window, as published: The next few years (the article's next-cycle horizon)
State at the audit date, October 29, 2026: Window governs: the scenario settles over the next few years, which have not elapsed. What is pending: whether adoption stays fragmented and episodic through the cycle, versus deepening into Scenario 1 integration or breaking into Scenario 3 reversal (graded in other chunks / C200).
The call, as published: “Scenario 3: Constraining Reversal (12–18%)”
Window, as published: The next few years (the article's next-cycle horizon)
State at the audit date, October 29, 2026: Window governs: the scenario settles over the article's next-cycle horizon (the next few years), which has not closed. What is pending: the six named reversal conditions occurring together. Distinguished from the AAPL grid (C201-C203): this scenario names concrete co-occurring events and a horizon, so it is OPEN rather than UNSETTLED.
The call, as published: “Base Case (70% Probability): 8.5 to 9.5 Million bpd (~40% to 45% Bypass).”
Window, as published: 24 months from August 2026
State at the audit date, October 29, 2026: Window governs: the base case (70%) settles at the end of the 24-month horizon. What is pending: total crude bypass capacity at Aug 2028 against the 8.5-9.5 million bpd band, with LNG flows remaining inside the Persian Gulf.
The call, as published: “Accelerated Shift (20% Probability): 11.5 to 12.5 Million bpd (~55% to 60% Bypass).”
Window, as published: 24 months from August 2026
State at the audit date, October 29, 2026: Window governs: the accelerated-shift path settles at the end of the 24-month horizon. What is pending: total crude bypass capacity at Aug 2028 against the 11.5-12.5 million bpd band.
The call, as published: “Systemic Failure (10% Probability): Under 7.5 Million bpd (Under 35% Bypass).”
Window, as published: 24 months from August 2026
State at the audit date, October 29, 2026: Window governs: the systemic-failure path settles at the end of the 24-month horizon. What is pending: total crude bypass capacity at Aug 2028 against the under-7.5 million bpd (under 35%) line.
The call, as published: “Crude bypass capacity reaches 60% to 70%, partially protecting oil exports while gas flows slowly begin to adapt.”
Window, as published: Months 24 to 60 from August 2026
State at the audit date, October 29, 2026: Window governs: this phase settles in months 24-60 from August 2026. What is pending: crude bypass capacity reaching 60% to 70% of Hormuz flows on completed pipelines and greenfield LNG.
The call, as published: “By 2027, the sheer volume of programmatic machine-to-machine transactions will force a complete split in digital asset infrastructure.”
Window, as published: By 2027
State at the audit date, October 29, 2026: Window governs: the call settles by 2027. What is pending: consumer rails remaining bound to synchronous compliance checks while machine commerce migrates into hardware-enclosed state channels backed by institutional underwriting vaults.
The call, as published: “Base Case: Range-Bound Consolidation (60% Probability | $60k–$75k Target): TIPS yields stay anchored near 2.41%, Fed Net Liquidity remains suppressed near $5.84 trillion, and global M2 velocity stays sluggish at +1.15%.”
Window, as published: Through 2027
State at the audit date, October 29, 2026: Window governs: the base path settles through 2027, so it is OPEN, but its price leg is failing on interim evidence: Bitcoin left the $60k-$75k range upward within two weeks of publication (first close above it on Aug 21, 2026) and has not returned to it through Oct 17, 2026. What is pending: the through-2027 record on price and on the stated TIPS, Fed Net Liquidity, and M2 levels. The Aug 22, 2026 follow-up restated the framework without grading this path.
The call, as published: “Bull Case: The Monetary Catch-Up (25% Probability | $100k–$170k+ Target): All four liquidity gates trigger—TIPS yields break below 1.75%, Fed Net Liquidity expands, global M2 growth accelerates above +2.50%, and DXY drops below 96.0.”
Window, as published: Through 2027
State at the audit date, October 29, 2026: Window governs: the bull path settles through 2027. What is pending: all four liquidity gates triggering together (TIPS below 1.75%, Fed Net Liquidity expanding, global M2 growth above +2.50%, DXY below 96.0) with Bitcoin rallying into $100k-$170k+. The Aug 22, 2026 follow-up claimed the framework flipped under Treasury yield caps; the audit records that claim and does not adopt it, since the gates as stated had not all verifiably triggered.
The call, as published: “Bear Case: Real-Yield Compression Spike (15% Probability | $50k–$58k Target): Commodity input inflation pushes TIPS yields above 2.75% while Fed Net Liquidity contracts below $5.50 trillion.”
Window, as published: Through 2027
State at the audit date, October 29, 2026: Window governs: the bear path settles through 2027. What is pending: TIPS yields above 2.75% together with Fed Net Liquidity contracting below $5.50 trillion and Bitcoin falling into $50k-$58k. The Aug 22, 2026 follow-up restated the gates without grading this path.
The call, as published: “1.6T pluggable transceivers handle early 1.6T cluster builds, but hyperscalers will deploy Broadcom’s Tomahawk 6-Davisson CPO switches in volume at scale-out tiers to prevent switch power consumption from exceeding 2kW per chassis.”
Window, as published: 2026-2027
State at the audit date, October 29, 2026: Window governs: Milestone 1 settles across 2026-2027. Interim evidence shows previews and early production, not the volume scale-out deployment the milestone requires. What is pending: hyperscaler volume deployment of TH6-Davisson CPO switches while 1.6T retimed pluggables peak.
The call, as published: “Pre-packaging wafer probing becomes mandatory across every advanced foundry, allowing FormFactor (FORM) and Keysight (KEYS) to expand gross margins toward 50%+.”
Window, as published: 2026-2027
State at the audit date, October 29, 2026: Window governs: Milestone 2 settles across 2026-2027. What is pending: mandatory pre-packaging wafer-level photonic probing across advanced foundries and FORM/KEYS gross margins expanding toward 50%+.
The call, as published: “Because InP lasers suffer exponential degradation when operated at temperatures above 85°C, hyperscalers will standardize on External Light Source Small Form-factor Pluggable (ELSFP) architectures.”
Window, as published: 2027-2028
State at the audit date, October 29, 2026: Window governs: Milestone 3 settles in 2027-2028. What is pending: hyperscaler standardization on ELSFP architectures decoupling lasers from hot switch dies.
The call, as published: “Optical I/O engines will replace copper backplanes in GPU-to-GPU NVLink fabrics, expanding silicon photonics silicon content per rack by over $30,000.”
Window, as published: 2027-2028
State at the audit date, October 29, 2026: Window governs: Milestone 4 settles in 2027-2028. What is pending: CPO expansion from scale-out Ethernet into scale-up GPU fabrics and the $30,000+ per-rack content expansion.
The call, as published: “Macro Liquidity Trigger (3-12 months): Buybacks sustained at or above $4 billion per session alongside weekly spot ETF net inflows holding between $300M and $700M confirm the baseline demand required to push prices toward the $70,000 liquidity pocket. Invalidation: if the 30-year breaks above 5.23% and the 10-year holds above 4.70% despite sustained $4B+ buybacks.”
Window, as published: 3-12 months from Aug 20, 2026; closes Aug 20, 2027.
State at the audit date, October 29, 2026: OPEN: the call's window runs to Aug 20, 2027 and its conditions are persistence conditions across that window. Interim evidence is favorable (Bitcoin crossed and has held above the $70,000 pocket) but the grade cannot settle inside the window.
The call, as published: “🔺 For the next 120 to 180 days, Scott Bessent’s $400 billion TGA drawdown provides the cleanest, most predictable liquidity tailwind digital assets will see this year.”
Window, as published: Next 120 to 180 days (from 2026-08-24; the article's 4-to-6 month clock)
State at the audit date, October 29, 2026: Window has not closed: the 120-180 day clock from Aug 24, 2026 runs to about Dec 22, 2026 through Feb 20, 2027. Interim evidence runs against the call so far (the balance rose into October rather than drawing down), printed here at the same size as the grade. What is pending: a TGA drawdown toward the $550B floor releasing roughly $400B into reserves before the clock ends. No follow-up in the index answers this article, but no settling event has occurred, so follow_up_missing is false.
The call, as published: “Base Case: Successful Sovereign Realignment (65% Probability)”
Window, as published: Over coming quarters (from 2026-08-29)
State at the audit date, October 29, 2026: Stated window has not closed.
The call, as published: “Bear Case: Supply Friction & Yield Breakout (35% Probability)”
Window, as published: Over coming quarters (from 2026-08-29)
State at the audit date, October 29, 2026: Stated window has not closed.
The call, as published: “As cash runways compress toward the 2027–2028 window, public small-caps with high monthly burn rates will face severe valuation compression.”
Window, as published: 2027–2028
State at the audit date, October 29, 2026: Window governs: the call settles in the 2027-2028 window. What is pending: whether high-burn public small-cap quantum/hardware names undergo severe valuation compression and distressed asset pickups in that window.
The call, as published: “Kill condition: if the 200ms step activates and SOL fails to take out $119.07 within 30 days, the speed premium is priced in and this leg is wrong.”
Window, as published: 30 days from activation of the 200ms step (still pending at publication, 2026-09-21)
State at the audit date, October 29, 2026: Activation occurred Oct 9, 2026; the article's 30-day window closes Nov 8, 2026. Interim state printed in full: no takeout yet and price falling, so the leg is tracking toward its own kill condition but has not reached it.
The call, as published: “Kill condition: if Strategy goes a full quarter without buying while BTC falls, the accumulator bid is gone and this read is wrong.”
Window, as published: A full quarter (from 2026-09-21)
State at the audit date, October 29, 2026: The kill condition requires a full quarter; one month in, the accumulator bid is intact on the filing record. Final grade at Dec 21, 2026.
The call, as published: “HUT below $40, 25%: the stock would have to fall more than half from $86.10. Possible in a crypto drawdown. Ho delivers all 1.5M shares, effectively out at ~$38.88. His insurance pays.”
Window, as published: By May 17, 2027 (valuation window May 13-17, 2027)
State at the audit date, October 29, 2026: Window has not closed: the below-$40 path settles on the May 13-17, 2027 valuation window at the May 17, 2027 maturity. What is pending: HUT's settlement VWAP against the $40 floor in May 2027.
The call, as published: “HUT between $40 and $221, 60%: where the stock trades today, and the 52-week high of $140.80 sits well under the cap. The base read: Ho delivers a fraction of the shares and keeps the appreciation above $40.”
Window, as published: By May 17, 2027 (valuation window May 13-17, 2027)
State at the audit date, October 29, 2026: Window has not closed: the base path (60%) is tracking inside its band on interim prices, but it settles only on the May 13-17, 2027 VWAP at the May 17, 2027 maturity. What is pending: the settlement VWAP and the resulting fractional share delivery.
The call, as published: “HUT above $221, 15%: requires roughly a 157% rally from the September 30 close. Ho's upside stops at the cap; JPMorgan keeps everything past $221.”
Window, as published: By May 17, 2027 (valuation window May 13-17, 2027)
State at the audit date, October 29, 2026: Window has not closed: the path settles on the May 13-17, 2027 valuation window at the forward's May 17, 2027 maturity. What is pending: HUT's settlement VWAP against the $221 cap in May 2027.
The call, as published: “The most probable path from here, roughly 70% by our judgment: the funding machine keeps running into the IPO, and the public S-1 is the first real test of every number in this piece.”
Window, as published: Into the Anthropic IPO (S-1 expected public by late October; marketing as soon as the week of November 9, trading before Thanksgiving)
State at the audit date, October 29, 2026: Window still open: the call runs into the Anthropic IPO, whose public S-1 (expected by late October ahead of November 9 marketing) had not appeared at the audit date. What is pending: the public S-1 filing and whether the funding machine keeps running into it; settles when the S-1 becomes public or the IPO timetable fails.
The call, as published: “The most probable outcome for the week ahead: Bitcoin stays under the range it left. The break holds. No daily close this week reclaims $81,300. What would change our mind on the break: a close back above $81,300 on any day this week.”
Window, as published: The week of October 26-30, 2026 (the article names the Friday Oct 30 close as the settlement point)
State at the audit date, October 29, 2026: Window closes with the Oct 30, 2026 close, after this addendum's audit date. Interim closes are consistent with the call (no reclaim through Oct 28). Grade after the Oct 30, 2026 close.
The call, as published: “The stack stalls, 45 to 60%. Nothing switches on inside this horizon. The law waits for its start date, the market ends the quarter where it began, and the funding share does not move.”
Window, as published: 1-3 months from Oct 28, 2026; closes Jan 28, 2027. Named triggers: Nov 30, 2026 Federal Reserve GENIUS Act rules comment close; monthly supply print against $299.1B
State at the audit date, October 29, 2026: In settleable form (window, baselines $299.1B and 0.64%, and the settling measure all printed in the piece, unlike the AAPL grid C201-C203) with the window still running; interim state is the baseline itself and nothing has settled. FOLLOW-UP MISSING not flagged: no settling event has occurred.
The call, as published: “The stack grows, 20 to 30%. Monthly supply prints turn up, the Federal Reserve's rules move from proposal toward final, and the funding share moves above 0.64% before the law takes effect.”
Window, as published: 1-3 months from Oct 28, 2026; closes Jan 28, 2027
State at the audit date, October 29, 2026: Settleable form, window running; no monthly print since the baseline has landed and the share has not moved above 0.64% on any print to date.
The call, as published: “The stack shrinks, 15 to 30%. Supply falls for a second year, the onshore build stalls in court, and the funding share slips below 0.64% on the same bills and repos count.”
Window, as published: 1-3 months from Oct 28, 2026; closes Jan 28, 2027
State at the audit date, October 29, 2026: Settleable form, window running; the share has not slipped below 0.64% on any print to date; the CME v. CFTC suit in its grounds is live and undecided, which is grounds, not settlement.
The call, as published: “The stack grows, 35 to 50%. The law switches on, the rulebooks land, and issuer buying resumes at the fast pace of the trend years, so the funding share climbs off its floor and supply holds above its baseline through the year.”
Window, as published: 6-12 months from Oct 28, 2026; final grade at the window's close, Oct 28, 2027, unless the printed trigger settles it earlier
State at the audit date, October 29, 2026: Settleable form (window, baselines, and the two-release trigger all printed), window running; no Treasury release since the set date has tested the trigger.
The call, as published: “The stack stalls, 30 to 45%. The stack grows at about the speed of the debt itself, the share stays under 1%, and the doctrine remains a statement with a small machine under it.”
Window, as published: 6-12 months from Oct 28, 2026; final grade at the window's close, Oct 28, 2027
State at the audit date, October 29, 2026: Settleable form, window running; the interim state (share at its 0.64% baseline, under 1%) is consistent with the leg one day into a 6-12 month window, and consistency at the start is not settlement.
The call, as published: “The stack breaks, 10 to 30%. A run on a large coin, a court ruling against the onshore contracts, or a rulebook that never lands breaks the chain, and issuers sell bills into a falling market instead of buying.”
Window, as published: 6-12 months from Oct 28, 2026; final grade at the window's close, Oct 28, 2027, or on a break event inside the window
State at the audit date, October 29, 2026: Settleable form, window running; no break event has occurred; the CME suit is live (filed Jun 18, 2026; CFTC moved to dismiss Oct 16, 2026), which keeps the leg live without settling it.
71 calls that carry no settling test as published: no window, no threshold, or no measure a public record can check. They are printed at full size, not graded on terms the article never set.
The call, as published: “Historical analogs suggest 10–15 day lag before price momentum shifts.”
Window, as published: 10–15 days from the 2025-07-29 filing analysis (article published 2025-08-01)
Why it carries no grade: The call states no observable definition of a momentum shift (no direction, no threshold), so no grade can be given without inventing criteria. The dated moves that did occur fall outside the stated 10-15 day band on both sides.
The call, as published: “Unless future filings show diversification or stronger liquidity, MARA's critical profile persists through at least the next 1–2 quarters. Any external shock in that window has outsized downside impact.”
Window, as published: next 1–2 quarters
Why it carries no grade: The call's baseline is a proprietary composite whose recomputation was never published, and its escape condition ('show diversification or stronger liquidity') has no threshold for what counts as showing either. Grading would require the audit to rebuild the tier and set the escape test itself. Precedent: C06 (undefined baseline).
The call, as published: “Bearish Path (25%): Financing window narrows; new issuance required; dilution accelerates; cash burn rises; regulatory headwinds hit custody/staking.”
Window, as published: Within 1–2 quarters if equity markets tighten
Why it carries no grade: Conditional window ('if equity markets tighten') whose trigger did not occur; grading the bundle FALSE would grade a condition the article never made unconditional. Quote verified against the published HTML per the mismatch flag.
The call, as published: “Most Likely Path (55%): Services narrative inches forward in disclosures, but real revenue scale lags; equity issuance slows but doesn't stop.”
Window, as published: Over the next 6–12 months
Why it carries no grade: Window stated but no observable threshold or baseline for any leg, so no date exists on which the path matures into a grade. Precedent: C14–C16 logic (a window alone does not settle a threshold-free path). Quote verified against the published HTML per the drive-quote-mismatch flag; wording matches the extraction.
The call, as published: “Bullish Path (15%): Custody KPIs show up soon; fee revenue scales; losses narrow.”
Window, as published: within 1–2 quarters
Why it carries no grade: Per the disputed-figures rule: the path's central leg (fee revenue scaling) rests on a flagged figure, the loss leg is split between GAAP (widened) and adjusted EBITDA (improved) with no stated basis in the call, and the custody-KPI leg could not be verified from a citable filing source after real effort. No grade is forced.
The call, as published: “Most Likely Path (55%): Neutral-bearish blend. More disclosures, little revenue. Issuance slows but continues.”
Why it carries no grade: No window and no observable threshold or baseline, and the central revenue leg is a disputed figure under the audit's disputed-figures rule. Precedent: C14–C16.
The call, as published: “Future filings would show: EFFECT + 424B5 clusters followed by disclosures of custody balances, WLFI revenue lines, or service fees in 8-Ks/MD&A.”
Why it carries no grade: No window and no observable threshold for the specified sequence. Precedent: C14–C16.
The call, as published: “Future filings would show: Frequent EFFECT + 424B5 clusters, each leading to more share issuance, but with no new revenue lines or custody KPIs. WLFI allocations stagnate or shrink.”
Why it carries no grade: No window and no observable threshold or baseline. Precedent: C14–C16.
The call, as published: “Future filings would show: EFFECT + 424B5 sequences continue reliably. WLFI allocations dominate new disclosures, but custody/service revenue remains minimal.”
Why it carries no grade: No window and no observable threshold or baseline for any leg. Precedent: C14–C16. The two matched follow-ups restate the article's WLFI framing; neither scores these paths.
The call, as published: “If ABTC settles into correlation with Bitcoin, then it trades in a $1.50–$1.70 band, moving with BTC’s $80K–$100K range at ~1.5× beta.”
Why it carries no grade: No window, a three-leg joint condition with an unmeasured beta leg, and a price band whose basis is corrupted by the merger's 1-for-5 reverse split. Grading would require inventing both the window and the conversion. See notes file.
The call, as published: “If hype fades and no fresh catalysts appear, then ABTC could drift back toward $1.00.”
Why it carries no grade: No window, and the price leg cannot be settled without the audit choosing a split conversion the article never stated. Unlike C41, no follow-up in the chain grades this arc. See notes file.
The call, as published: “Most Likely Path (90%): Coinbase continues scaling as the de facto crypto utility. Custody, stablecoin payments, and compliance-grade reporting expand further.”
Why it carries no grade: No window and no observable threshold or baseline. Precedent: C14–C16.
The call, as published: “Bearish Path (10%): Regulation or competition slows adoption. Coinbase still functions as utility infrastructure, but momentum weakens.”
Why it carries no grade: No window and no observable threshold or baseline. Precedent: C02, C14–C16.
The call, as published: “it is most probable (75%) that DFDV will continue strengthening its position through Solana-driven treasury actions.”
Why it carries no grade: No window and no observable threshold or baseline for 'strengthening.' Precedent: C14–C16. The companion dated call in the same article (C46) carried a window and graded TRUE; this path carried neither.
The call, as published: “Base case (65% probability): Near-term volatility, then continuation higher.”
Why it carries no grade: No window and no observable threshold for 'higher.' The audit does not grade a path TRUE for matching a shape the article never quantified. Precedent: C14–C16.
The call, as published: “Bullish acceleration (20% probability): Faster upside if U.S. demand (CPI) rebounds while ETFs continue adding and netflows flip negative.”
Why it carries no grade: No window and no observable threshold. Precedent: C02, C14–C16.
The call, as published: “Bearish stall (15% probability): Extended consolidation if ETF inflows stall and reserves stop draining while leverage keeps building.”
Why it carries no grade: No window and no observable threshold for the consolidation or its triggers. Precedent: C02, C14–C16.
The call, as published: “Base case (55%): Near-term turbulence, long-term upside. Expect chop or a flush before the squeeze resumes.”
Why it carries no grade: Two-leg path whose second leg (upside/squeeze resumption) has no observable threshold or window. Precedent: C14–C16 (grids with no window and no threshold are UNSETTLED even when early legs resemble the tape).
The call, as published: “Bearish tilt (30%): If inflows remain this heavy and ETFs stall, selling pressure dominates, leaving ETH stuck in weakness longer.”
Why it carries no grade: No window, no duration, no price level, no flow threshold. Grading the tape against invented terms is barred by the audit rules. Precedent: C02, C14–C16.
The call, as published: “Bullish break (15%): If ETFs accelerate and CPI rebounds, ETH could spring higher sooner than expected.”
Why it carries no grade: No window and no observable threshold for the trigger legs or the price leg; 'sooner than expected' has no stated expectation to measure against. Precedent: C02, C14–C16.
The call, as published: “Base Case — 60% probability. The model works as designed — treasury growth continues, warrants get exercised as price levels are hit, NAV/share tracks SUI but compresses under issuance.”
Why it carries no grade: No settling window and no observable threshold or baseline for any leg (growth pace, compression rate, or which price levels trigger exercise). Grading would require inventing all three. Precedents: C02, C06, C14–C16 in the free-corpus ledger. Quote re-taken from the published HTML per the drive-quote-mismatch flag; wording matches the extraction.
The call, as published: “Base Case — 60% probability. distribution holds. Rallies capped until velocity cools.”
Why it carries no grade: No window and an undefined proprietary threshold ('velocity cools'); grading would require inventing the metric (precedent C02).
The call, as published: “Bullish Break — 15% probability. upside only if velocity drops under 4 and new demand inflows arrive.”
Why it carries no grade: Necessary-condition form plus an unverifiable proprietary trigger and no window: there is no outcome the audit could source that settles this path as written (precedents C02, C14-C16).
The call, as published: “The only buy map is below $3.40 with velocity under 4. That is when accumulation returns.”
Why it carries no grade: Conjunctive condition whose second leg (velocity under 4) rests on an undefined, unpublished metric; the price leg alone cannot settle it. Price leg printed at full size in the settling event (precedent C02: no definition, no grade).
The call, as published: “Bull Case (70%): Bitmain's US factory is already in motion. If the US factory stays on schedule, Hut 8 resets the cost curve.”
Window, as published: Early 2026
Why it carries no grade: Evidence gap, stated plainly: the article's own checkpoints are checkable in principle but no public source found in this pass records them, and the second leg (Hut 8 resets its cost curve via the factory) has no sourced confirmation. No grade from absence alone.
The call, as published: “Moderate Case (25%): Minor delays or faster competitors narrow Hut 8's advantage, but don't erase it. Hut 8 still expands, stock ~$28.”
Why it carries no grade: No window, and the path's one numeric marker ($28) contradicts the tape from publication day onward (the same stale-baseline defect as C70), so the scenario as written never had a gradeable settling state. Expansion leg and full tape printed in the settling event.
The call, as published: “By 2026, when other miners report hashrate and operating costs, the performance gap should show up as 20–30% outperformance in Hut 8's favor.”
Window, as published: By 2026
Why it carries no grade: Relative call with no defined peer basket, metric, or measurement date (precedent C06: no defined baseline, no grade).
The call, as published: “By 2026, Hut 8 is scaling cheaper and faster. That takes capacity to 33+ EH/s.”
Window, as published: By 2026
Why it carries no grade: The target is numeric but its basis is not: the article's 9.3 EH/s starting point and the company's reported totals (which consolidate ABTC differently) cannot be reconciled from sourced figures, and the stated delivery mechanism did not occur as described. A grade would require the audit to choose a consolidation basis the article never stated.
The call, as published: “Q1 2026 is when the moat becomes real. If the build stays on pace, Hut 8 doubles.”
Window, as published: Q1 2026
Why it carries no grade: Baseline defect of the C06 kind: the article defines its baseline in words ($21-22) that the publication-week tape contradicts ($36-38), and the grade flips with the choice. The audit does not pick a baseline the article did not settle. Both baselines and both outcomes are printed in the settling event.
The call, as published: “Ranging Phase — 30% Sentiment may keep the stock capped until acquisitions or energy projects translate into visible earnings.”
Why it carries no grade: No window and no defined cap, band, or threshold; grading would require inventing all three (precedents C02, C14-C16). Quote verified against the published HTML (this article is in the Drive-quote mismatch list; paths, probabilities, and wording of the operative sentence match the published text).
The call, as published: “The SEC filings already point to a 20–30% valuation gap that reopens as markets price each business on its own terms.”
Why it carries no grade: No settling window and no defined baseline figure; any numeric grade would require the audit to invent both. The publication's qualitative self-grade in the Oct 25, 2025 retrospective is recorded as a follow-up, not adopted as evidence.
The call, as published: “Ranging — 30% Probability. Investor sentiment may keep Hut 8 stuck in a band until acquisitions or energy projects translate into visible earnings.”
Why it carries no grade: No window and no defined band or threshold, so the path cannot be settled without inventing both (precedents C02, C14-C16). The full tape is printed in the settling event.
The call, as published: “Soft Landing – 40% PMI stabilizes above 50, AI capex continues, financing holds. Crypto impact: ranging path with a bullish tilt. Crypto grinds higher on liquidity support.”
Why it carries no grade: The grid states no settling window, and each path's legs matured at different times or split (PMI leg, financing leg, crypto leg pointing different ways in different quarters), so no date exists on which this path settles as written. Grading would require inventing a window (precedents C14-C16). The leg-by-leg record is printed in the settling event.
The call, as published: “Super Cycle – 35% PMI rebounds, AI demand proves sticky, capex accelerates. Crypto impact: bullish path. Broad risk-on surge, BTC and ETH rally with AI equities.”
Why it carries no grade: The grid states no settling window, and each path's legs matured at different times or split (PMI leg, financing leg, crypto leg pointing different ways in different quarters), so no date exists on which this path settles as written. Grading would require inventing a window (precedents C14-C16). The leg-by-leg record is printed in the settling event.
The call, as published: “Unwind – 25% PMI drops sharply, vendor financing breaks, equities sell off. Crypto impact: bearish path. Forced selling drags crypto down first, recovery comes later with policy easing.”
Why it carries no grade: The grid states no settling window, and each path's legs matured at different times or split (PMI leg, financing leg, crypto leg pointing different ways in different quarters), so no date exists on which this path settles as written. Grading would require inventing a window (precedents C14-C16). The leg-by-leg record is printed in the settling event.
The call, as published: “Ranging (35%) • Buybacks: Small burns, symbolic without major revenues. Price chops sideways until significant fees fuel the loop.”
Why it carries no grade: No window and an open-ended 'until' clause; one leg occurred and one leg failed, so no single grade follows from the article's own terms without inventing a horizon (precedents C02, C14-C16). Both legs are printed at full size in the settling event.
The call, as published: “Setup: PQ-ready chains trade on narrative while BTC and ETH remain flow-heavy until compliance is forced.”
Why it carries no grade: No window and no observable threshold; grading would require inventing both (precedents C14-C16).
The call, as published: “Setup: BTC and ETH dominance persists, PQ chains get no reward, early investors sit on dead money.”
Why it carries no grade: No window and no observable threshold for the path's outcome terms; grading would require inventing both (precedents C14-C16).
The call, as published: “🔺 Next compression window forming early 2026”
Window, as published: early 2026
Why it carries no grade: No publicly observable threshold or baseline exists for an Atlas-7 'compression window'; the grade cannot be sourced from live evidence after real effort, and the publication's own follow-up does not settle this call.
The call, as published: “If BTC oscillates above $90K while ABTC executes Phase 2 funding, energy-to-equity coupling should push markets into a positive resonance zone. Expect a systemic reflexivity surge.”
Window, as published: Q1–Q2 2026
Why it carries no grade: Conjunctive call whose outcome ('positive resonance zone / systemic reflexivity surge') has no observable definition or threshold; the two checkable legs point opposite ways (funding executed, BTC mostly below $90K and falling). Grading would require inventing the surge criterion (rule 1; precedents C02, C14-C16).
The call, as published: “Bullish Break: 65 % probability. Reason: Custody growth totaling $47 B with consistent quarter-over-quarter increases across Robinhood, PayPal, and Bakkt. Repricing likely within the next two earnings cycles as disclosure adoption becomes standard.”
Window, as published: next two earnings cycles
Why it carries no grade: Window closed but the call carries no observable threshold or baseline for 'repricing' across its five named firms, so any grade would require inventing both (precedents C06, C14-C16). The divergent tape for the named names is printed in the settling event.
The call, as published: “Ranging / Neutral: 25 %. Reason: Temporary valuation pause possible if analyst coverage fails to isolate custody metrics or if earnings attribution remains opaque.”
Why it carries no grade: No settling window and no observable threshold in the call as extracted, per the free-corpus precedents (C14-C16). Grading a 'pause' would require the audit to invent the band and the clock.
The call, as published: “Bearish Tilt: 10 %. Reason: Regulatory intervention could cap balance-sheet recognition, especially if auditors reclassify custody as contingent liability.”
Why it carries no grade: No grade: the path states no settling window, so the non-occurrence of its trigger cannot mature into FALSE, and the trigger's occurrence would be the only route to TRUE. Per the free-corpus precedents, UNSETTLED, with the trigger's absence and the opposite regulatory direction printed in the settling event.
The call, as published: “Ranging / Neutral – 20%. Reason: A temporary pause could occur if inflows level off or if analyst coverage delays recognition of ETF-driven revenue. Outlook: Valuations may consolidate while disclosure adoption becomes standard.”
Why it carries no grade: No grade: the call as extracted states no settling window and no observable threshold for 'valuations consolidate' (which valuations, what band, how long), per the free-corpus precedents (C14-C16). The inflow leg's occurrence is printed in the settling event; it is not enough to grade a path whose price leg is undefined.
The call, as published: “Bearish Tilt – 10%. Reason: Regulatory or accounting reclassification of redemption mechanics could slow near-term inflows.”
Why it carries no grade: No grade: the path states no settling window, and its specified trigger (a reclassification of redemption mechanics) never occurred, while its outcome leg (slowed inflows) did occur for unrelated, sourced reasons. Grading TRUE would adopt an outcome the path's own mechanism does not describe; grading FALSE would require a window the article never gave. Per the free-corpus precedent (C02, C06), the grade is UNSETTLED and the split record is printed in the settling event.
The call, as published: “Neither regime can eliminate the other. Both are locked in as permanent layers of the same currency. ... The 2025 to 2028 governance window is the last period in which relative pricing between the two regimes will be mispriced by more than basis-point noise.”
Window, as published: The 2025-2028 window is named for the mispricing leg; the permanence leg carries no window (permanent is unbounded).
Why it carries no grade: No grade. 'Relative pricing between the two regimes' names no price, spread, index, or pair of instruments whose pricing could be observed; 'more than basis-point noise' names no measurable quantity; and no observable condition is stated that would settle 'permanent' for the split itself. Committed language with portfolio instructions attached, but no instrument, metric, or test by which the state could settle inside any finite window. Same disposition as C238. No outcome evidence attached; the grade rests on the published text's absence of terms.
The call, as published: “Compression with control (~55%)”
Why it carries no grade: No settling window and no observable threshold in the call as extracted, per the free-corpus precedents (C14-C16). The interim figures are printed in the settling event: they show mild, well-attributed margin compression, which is consistent in tone with more than one path at once, and grading among them would require the audit to invent the threshold that separates them.
The call, as published: “Explainable AI deleverage (~30%)”
Why it carries no grade: No settling window and no observable threshold in the call as extracted, per the free-corpus precedents (C14-C16). The interim figures are printed in the settling event: they show mild, well-attributed margin compression, which is consistent in tone with more than one path at once, and grading among them would require the audit to invent the threshold that separates them.
The call, as published: “Auditability decay (~15%)”
Why it carries no grade: No settling window and no observable threshold in the call as extracted, per the free-corpus precedents (C14-C16). The interim figures are printed in the settling event: they show mild, well-attributed margin compression, which is consistent in tone with more than one path at once, and grading among them would require the audit to invent the threshold that separates them.
The call, as published: “Optical Demand Surge: 40–50% probability Rationale If AI clusters continue expanding toward hundreds of thousands of GPUs and networking speeds move toward 1.6 Tbps and beyond, demand for optical interconnects could accelerate quickly.”
Why it carries no grade: No grade: the article states no settling window and no observable threshold or baseline for this path, so grading would require inventing both (precedents C14-C16 in the free-corpus ledger). Specifically, demand growth alone cannot settle it, because the article states no demand figure, date, or share threshold that would separate a surge from the Supply Expansion path running alongside it.
The call, as published: “Supply Expansion: 30–35% probability Rationale Manufacturers of Indium Phosphide substrates, photonic devices, and optical components expand capacity as orders increase.”
Why it carries no grade: No grade: the article states no settling window and no observable threshold or baseline for this path, so grading would require inventing both (precedents C14-C16 in the free-corpus ledger). Specifically, capacity announcements alone cannot settle it, because the same reporting documents shortages persisting alongside the expansions; the article states no test for 'prevents sustained bottlenecks.'
The call, as published: “Architectural Efficiency: 15–20% probability Rationale Advances in chip packaging, interconnect architecture, or training techniques reduce the amount of data that must move across clusters.”
Why it carries no grade: No grade: the article states no settling window and no observable threshold or baseline for this path, so grading would require inventing both (precedents C14-C16 in the free-corpus ledger). Specifically, no metric in the article defines how much data-movement reduction would count, or by when.
The call, as published: “Localized Supply Shock: 5–10% probability Rationale The photonics ecosystem depends on specialized materials and manufacturing processes.”
Why it carries no grade: No grade: the article states no settling window and no observable threshold or baseline for this path, so grading would require inventing both (precedents C14-C16 in the free-corpus ledger). Specifically, a shortage headline alone cannot settle it, because the same reporting also documents the capacity expansion of the Supply Expansion path; the paths are not mutually exclusive on any stated test.
The call, as published: “Expansionary: 60–65% probability”
Why it carries no grade: Unlike the SUIG and Anthropic grids, this grid carries no horizon at all. Grading it would require the audit to invent both a window and a threshold. Recorded as a construction finding in Flags.
The call, as published: “Ranging / Neutral: 20–25% probability”
Why it carries no grade: Unlike the SUIG and Anthropic grids, this grid carries no horizon at all. Grading it would require the audit to invent both a window and a threshold. Recorded as a construction finding in Flags.
The call, as published: “Constraining: 15–20% probability”
Why it carries no grade: Unlike the SUIG and Anthropic grids, this grid carries no horizon at all. Grading it would require the audit to invent both a window and a threshold. Recorded as a construction finding in Flags.
The call, as published: “Scenario 1: Pressure is absorbed Probability: ~60–65%”
Why it carries no grade: UNSETTLED for the reason printed: no window and no observable threshold in the call as published.
The call, as published: “Scenario 2: Pressure builds Probability: ~35–40%”
Why it carries no grade: UNSETTLED: where a grid states no window and no observable threshold, grading would require inventing both, per the binding rules and the C14-C16 precedent. This is a construction finding about the call as published, not a judgment on Marvell.
The call, as published: “The repricing will not be gradual decay. It will be discontinuous, a step-function across categories. ... Entire SaaS verticals reprice in quarters, not years. ... Timing in this system is not a date. It is a state.”
Window, as published: None published, and expressly refused: 'Timing in this system is not a date. It is a state' (Part II). 'In quarters, not years' describes the discharge's pace once it starts, not a window inside which it must start.
Why it carries no grade: No grade. No multiple level, index, basket of vendors, or retention figure is named at which the repricing would count as having occurred; Part II's three confirmation signals (deal language in earnings calls, churn and NRR 'weakening sharply,' the valuation gap 'widening') carry no level. A definite outcome staked in committed language, with the date declined in the article's own words; the desk's gauge scores (ECS/LSI/ST) are its internal instrument, not a published settling condition. Same disposition as C238. No outcome evidence attached; the grade rests on the published text's absence of terms.
The call, as published: “Within the next 2 to 3 years, companies that rely on subscriptions start shifting part of their pricing to usage. It won't replace subscriptions right away. It sits next to them at first. Per call, per query, per action.”
Window, as published: 2 to 3 years (the one term the cluster publishes).
Why it carries no grade: No grade. A window alone does not settle a call whose condition has no observable boundary: no basket of companies is named, no count or share that must shift is stated, 'part of their pricing' has no floor, and the fork test names no comparison set, revenue measure, or source. As published the claim cannot fail on any observable; a single vendor adding a per-call tier inside the window satisfies its letter, and that pattern already existed at publication (the cluster's own companion coverage lists per-action pricing at HubSpot and Salesforce). Same disposition as C238, with the difference recorded: C238 published no window at all; C248 publishes a window and nothing else.
The call, as published: “Meta is weaponizing its overbuilt hardware pipeline to run a predatory compute-dumping campaign, a move that will permanently collapse raw GPU margins. For specialized neoclouds like CoreWeave and Nebius, this is a major disruption. Their entire valuations depend on hardware scarcity. When a price-insensitive giant dumps unlimited compute into the market, rental margins collapse to near-zero. Leveraged middlemen holding massive debt will face terminal margin compression. Clear out all exposure to pure-play compute capacity resellers, highly leveraged GPU-as-a-service providers, and non-differentiated data center rollouts. Their business models may not survive against a giant that gives compute away at cost.”
Window, as published: None stated in the article (no date, window, or deadline; 'permanently' is unbounded)
Why it carries no grade: No grade on the outcome: the call publishes no settling window, no numeric threshold, and no baseline, so no finite outcome can settle it on the audit's terms. Deciding rule: the audit's standing method (addendum and gap closure) that a call with no window, threshold, or baseline is UNSETTLED with the reason printed; AUDIT-SPEC.md Pass 1 requires the settling date or window and Pass 3 defines UNSETTLED as no settling condition ever matured. Not OPEN, because the addendum defines OPEN calls as in settleable form but not yet settled, and C238 as published is not in settleable form. No window is invented; the chain's later articles supply none for this call (the July 10, 2026 restatement is likewise unbounded, and the October 27, 2026 follow-up's dated watch items test Musk's claim and individual financings, not the July call). Same disposition as C236 and C237.
The call, as published: “Platform reinforcement (Bull case): 45% AI becomes available across supported Apple products and developer tools while the company's overall economics remain strong.”
Why it carries no grade: No grade: this grid leg states no settling window and no observable threshold or baseline (precedents C14-C16 in the free-corpus ledger). Any grade would require the audit to invent both the test and the date. Recorded as a construction finding in the notes.
The call, as published: “Defensive parity (Base case): 35% Apple closes major capability gaps and keeps its ecosystem competitive, but the evidence never establishes clear incremental economics or a lasting technical advantage.”
Why it carries no grade: No grade: a scenario whose condition is that evidence 'never establishes' a result, with no stated window, can never mature into a settling event (precedents C14-C16 in the free-corpus ledger). Recorded as a construction finding in the notes.
The call, as published: “Execution drag (Bear case): 20% Problems with quality, compatibility, access, privacy, quotas, infrastructure costs, or developer friction limit adoption or increase costs faster than Apple can comfortably absorb them.”
Why it carries no grade: No grade: this grid leg states no settling window and no observable threshold or baseline (precedents C14-C16 in the free-corpus ledger). Any grade would require the audit to invent both the test and the date. Recorded as a construction finding in the notes.
The call, as published: “Once dark pool liquidity bids finish digesting the remaining sell orders above $68,000, public exchanges will experience an absolute physical supply failure. The push past $70,000 will be driven by direct asset illiquidity.”
Why it carries no grade: No grade: the settling condition requires the push past $70,000 to be driven by spot supply scarcity / dark pool absorption rather than retail derivatives leverage. That causal attribution is not observable from public price, flow, or open-interest data at the standard this audit requires, and the call states no window in which the driver could be isolated. The price occurrence is recorded; the grade is UNSETTLED on the driver leg, not on price. No figure from the article's Aug 19, 2026 BTC market-cap claim is used (extraction-flagged disputed figure).
The call, as published: “Accumulation Zone: Scale into spot positions between $8.00 and $10.50 using recurring weekly orders while the token builds a multi-year base.”
Why it carries no grade: No grade: the call as extracted is a buy-map instruction (scale into spot between $8.00 and $10.50 while LINK builds a base) with no settling window and no stated outcome that would settle it as right or wrong; price never entered the zone, so the map never activated. Grading it would require inventing a success criterion. The article's $18 and macro targets are not used: the Aug 26, 2026 LINK target was flagged in extraction as an internal conflict (disputed figure rule).
The call, as published: “Call 3, the quiet day: if the print lands in line, SPY closes within plus or minus 1.0% and the 10Y within plus or minus 8bp.”
Window, as published: Wednesday, September 30, 2026 (print day)
Why it carries no grade: No grade: a conditional scenario call whose stated trigger (an in-line print) did not occur cannot be graded TRUE or FALSE on its consequent (SPY within plus or minus 1.0%, 10Y within plus or minus 8bp); the quiet-day reaction was never tested. Recorded as UNSETTLED with the reason printed, following the scorecard's own NOT ACTIVATED disposition.
The call, as published: “Call 4, hot: if the print lands hot, SPY closes down and the 10Y closes up.”
Window, as published: Wednesday, September 30, 2026 (print day)
Why it carries no grade: No grade: a conditional scenario call whose stated trigger (a hot print) did not occur cannot be graded TRUE or FALSE on its consequent (SPY down, 10Y up); the market reaction to a hot print was never tested. Recorded as UNSETTLED with the reason printed, following the scorecard's own NOT ACTIVATED disposition.
The call, as published: “This piece assembles that portfolio from the companies' own filings, shows what each position costs the people who already own the shares, and hands you the rule for reading the next announcement the day it prints. There will be a next one.”
Window, as published: None stated in the article
Why it carries no grade: No grade: the claim stakes a future event (a next government-position announcement) but publishes no window inside which it must occur, no threshold, and no baseline; an announcement next week and one in five years both satisfy it as written, so it cannot be settled on the audit's terms. Same disposition as the ledger's term-less predictive claims (compare C216).
The call, as published: “The bill also runs forward. The next time one of these companies raises private money, the state's seat is already at the table: senior where it lent, beside the board where it owns, holding a floor where it insured a price. Private money prices that presence into the next term sheet, in the rate, in the covenants, or in the discount, and the holder pays that price too, in a filing he has not seen yet.”
Window, as published: None stated in the article (the next raise, whenever it occurs)
Why it carries no grade: No grade: no window is stated, and decisively no baseline is stated; the claimed effect (private money pricing the state's presence into the next term sheet) is not observable separately from the raising company's condition, the market, and the instrument chosen, at the standard this audit requires. Same disposition as C216's driver leg.
The call, as published: “Trading never stops, but America sleeps, and the price is set offshore during our night, in the Asian morning. The next morning here opens at a price the night already chose. If the onshore build succeeds, that night center should move, slowly, toward American venues and American hours.”
Window, as published: None stated in the article (no date, window, or deadline; 'slowly' is unbounded)
Why it carries no grade: Extracted on the corrected extraction standard of the C238 correction (a committed directional claim is numbered and graded on its published terms rather than dropped), and UNSETTLED under the audit's standing rule: a call with no window, threshold, or baseline is UNSETTLED with the reason printed (AUDIT-SPEC.md Pass 3). Not OPEN: it is not in settleable form, unlike the same article's Foresight grid legs C239-C244.