{
  "schema": "OTR-SIGNALS-CATEGORY-EDITION-1",
  "release_id": "OTR-SIGNALS-20261009-052420Z-FORCE-1",
  "parent_edition_release_id": "OTR-2026-10-08-0100-SGT-R1",
  "parent_full_edition": {
    "path": "/data/edition/current.json",
    "release_id": "OTR-2026-10-08-0100-SGT-R1",
    "sha256": "eb7aab0069a60a77d139a5eeb0de2b7f0e46d7146f87503116f44a050e3e2e81"
  },
  "status": "PREPARED_FOR_PUBLICATION",
  "publication_timestamp": "2026-10-09T05:24:20Z",
  "research_cutoff_utc": "2026-10-09T05:24:20Z",
  "window_start_utc": "2026-10-08T05:24:20Z",
  "research_window": {
    "start_utc": "2026-10-08T05:24:20Z",
    "end_utc": "2026-10-09T05:24:20Z",
    "duration_hours": 24
  },
  "items": [
    {
      "schema": "OTR-SIGNALS-CATEGORY-CARD-1",
      "id": "INV-20261009-FAST-RETAILING-EARNINGS-RESET-168H",
      "publication_status": "READY",
      "status": "REVIEWED_EDITORIAL_CARD",
      "primary_category": "investments",
      "categories": [
        "investments"
      ],
      "title": "Fast Retailing’s post-results reversal tests the cost of optimism",
      "summary": "Fast Retailing’s first post-results session has reversed an opening gain after a sharp pre-results rise. We lean bearish for 168 hours because investors may keep reducing the price they pay for the next year’s earnings while Japan’s cost pressure and slower group profit growth are reassessed. Overseas growth and an already-large fall make a rebound a serious risk.",
      "signal_claim": "Fast Retailing’s first post-results session has reversed an opening gain after a sharp pre-results rise. We lean bearish for 168 hours because investors may keep reducing the price they pay for the next year’s earnings while Japan’s cost pressure and slower group profit growth are reassessed. Overseas growth and an already-large fall make a rebound a serious risk.",
      "thesis": "Fast Retailing’s first post-results session has reversed an opening gain after a sharp pre-results rise. We lean bearish for 168 hours because investors may keep reducing the price they pay for the next year’s earnings while Japan’s cost pressure and slower group profit growth are reassessed. Overseas growth and an already-large fall make a rebound a serious risk.",
      "key_points": [
        "The Tokyo share reversed an opening gain after a 10.24% pre-results rise.",
        "Japan cost pressure matters, but overseas operating growth remains the strongest countercase.",
        "Seven-day bearish judgement with 29/52/19 subjective, uncalibrated scenarios and a separate sign-only score."
      ],
      "bottom_line": "BEARISH over 168 elapsed calendar hours, from 2026-10-09T05:20:29.009Z to 2026-10-16T05:20:29.009Z, referenced to ¥72,030.0. The scenario split is 29% bullish, 52% bearish and 19% neutral around an inclusive ±1% return band. These estimates are subjective and UNCALIBRATED. This is a weak-to-moderate research judgement. The window includes the 12 October Tokyo holiday and expires in a normally open afternoon session. A lower comparable endpoint is a directional HIT; flat or higher is a MISS, regardless of the scenario band. No profit after fees, taxes, financing, borrow costs or currency conversion is promised.",
      "named_assets": [
        {
          "name": "Fast Retailing ordinary shares",
          "ticker": "9983.T",
          "symbol": "9983.T",
          "direction": "BEARISH",
          "currency": "JPY",
          "venue": "Tokyo Stock Exchange Prime"
        }
      ],
      "directional_takeaway": "BEARISH, 168H",
      "prediction_activation": true,
      "scoring_eligible": true,
      "entry_status": "FROZEN_REAL_TIME_LAST_PRICE_MINUTE_CLOCK_REFERENCE",
      "forecast_prepared_at_utc": "2026-10-09T05:20:29.009Z",
      "publication_timestamp": null,
      "native_publication_time_utc": null,
      "check_time_utc": "2026-10-16T05:20:29.009Z",
      "check_time_label": "168-hour check",
      "source_labels": [
        "OTR Database Data"
      ],
      "sources": [
        {
          "source_id": "FAST-1",
          "title": "FY2026 results summary",
          "url": "https://www.fastretailing.com/eng/ir/news/2610081800.html",
          "publisher": "Fast Retailing",
          "source_clock": {
            "original": "2026-10-08",
            "published_at_utc": null,
            "precision": "date"
          },
          "retrieved_at_utc": "2026-10-09T04:58:23Z",
          "retrieval_time_precision": "approximate_tool_interval",
          "review_method": "Full text. FY2027 business profit +15.5%; net profit +3.2%; Japan flat business profit and weaker yen procurement costs; international double-digit growth."
        },
        {
          "source_id": "FAST-2",
          "title": "CFO FY2026 results and FY2027 estimates",
          "url": "https://www.fastretailing.com/eng/ir/library/pdf/20261008_results_en.pdf",
          "publisher": "Fast Retailing",
          "source_clock": {
            "original": "2026-10-08",
            "published_at_utc": null,
            "precision": "date"
          },
          "retrieved_at_utc": "2026-10-09T05:01:20Z",
          "retrieval_time_precision": "approximate_tool_interval",
          "review_method": "Pages3-10,20-25 inspected in bounded text. Business profit excludes other income/expenses. Page22: FY26 business718.4bn, other24.6bn, operating743.1bn, net finance59.3bn, pretax802.5bn, attributable542.5bn; forecast830bn business and operating,50bn finance,880bn pretax,560bn attributable. No forecast FX gain assumed. Missing FY27 tax/noncontrolling-interest bridge is explicit, not guessed."
        },
        {
          "source_id": "FAST-3",
          "title": "Consolidated annual results announcement",
          "url": "https://www.fastretailing.com/eng/ir/library/pdf/tanshin202608_4q_eng.pdf",
          "publisher": "Fast Retailing",
          "source_clock": {
            "original": "2026-10-08",
            "published_at_utc": null,
            "precision": "date"
          },
          "retrieved_at_utc": "2026-10-09T05:05:00Z",
          "retrieval_time_precision": "approximate_tool_interval",
          "review_method": "Pages1-3,11,18-20 inspected. FY27 projected basic EPS1825.06JPY. FY26 operating transaction FXgain15.306bn, finance FXgain7.168bn; these are separate lines. Does not prove all other income is one-off."
        },
        {
          "source_id": "FAST-4",
          "title": "FY2026 third-quarter prior earnings release",
          "url": "https://www.fastretailing.com/eng/ir/news/2607091800.html",
          "publisher": "Fast Retailing",
          "source_clock": {
            "original": "2026-07-09",
            "published_at_utc": null,
            "precision": "date"
          },
          "retrieved_at_utc": "2026-10-09T05:00:00Z",
          "retrieval_time_precision": "approximate_tool_interval",
          "review_method": "Prior estimate revenue3970bn, business710bn, operating730bn, net500bn. Current FY26 results beat the profit guidance but slightly missed revenue; not an analyst-consensus comparison."
        },
        {
          "source_id": "FAST-5",
          "title": "Kabutan TSE ordinary-share daily OHLCV",
          "url": "https://s.kabutan.jp/stocks/9983/historical_prices/daily/",
          "publisher": "Kabutan/Minkabu",
          "source_clock": {
            "original": "Dated source observations detailed in retained research receipt",
            "published_at_utc": null,
            "precision": "source-specific"
          },
          "retrieved_at_utc": "2026-10-09T05:02:50Z",
          "retrieval_time_precision": "approximate_tool_interval",
          "review_method": "3 visible pages;90 completed daily rowsMay29-Oct8. Current partialOct9 excluded. Current prices on this source explicitly15min delayed; never use its current quote for P0."
        },
        {
          "source_id": "FAST-6",
          "title": "Issuer linked TSE stock chart",
          "url": "https://www.fastretailing.com/eng/ir/stockinfo/stockchart.html",
          "publisher": "Fast Retailing",
          "source_clock": {
            "original": "Dated source observations detailed in retained research receipt",
            "published_at_utc": null,
            "precision": "source-specific"
          },
          "retrieved_at_utc": "2026-10-09T05:01:00Z",
          "retrieval_time_precision": "approximate_tool_interval",
          "review_method": "Identifies9983,TSEPrime,JPY; directly links Stockweather chart."
        },
        {
          "source_id": "FAST-7",
          "title": "Stockweather real-time TSE quote",
          "url": "https://parts.stockweather.co.jp/stocks/ir/contents/9983/chartV2.aspx?lang=en",
          "publisher": "StockWeather",
          "source_clock": {
            "original": "2026/10/09 14:20 JST",
            "published_at_utc": null,
            "observed_at_utc": "2026-10-09T05:20:00.000Z",
            "precision": "minute; lower-bound proxy with full interval retained"
          },
          "retrieved_at_utc": "2026-10-09T05:20:27.499Z",
          "retrieval_time_precision": "exact_tool_completion_clock",
          "review_method": "Read rendered DOM after reloading permitted issuer-linked live page; price real-time, volume delayed 15 minutes."
        },
        {
          "source_id": "FAST-8",
          "title": "JPX stock trading hours",
          "url": "https://www.jpx.co.jp/english/equities/trading/domestic/01.html",
          "publisher": "Japan Exchange Group",
          "source_clock": {
            "original": "Dated source observations detailed in retained research receipt",
            "published_at_utc": null,
            "precision": "source-specific"
          },
          "retrieved_at_utc": "2026-10-09T05:03:57Z",
          "retrieval_time_precision": "approximate_tool_interval",
          "review_method": "09:00-11:30 and12:30-15:30JST on trading days."
        },
        {
          "source_id": "FAST-9",
          "title": "JPX holidays",
          "url": "https://www.jpx.co.jp/english/corporate/about-jpx/calendar/",
          "publisher": "Japan Exchange Group",
          "source_clock": {
            "original": "Dated source observations detailed in retained research receipt",
            "published_at_utc": null,
            "precision": "source-specific"
          },
          "retrieved_at_utc": "2026-10-09T05:03:57Z",
          "retrieval_time_precision": "approximate_tool_interval",
          "review_method": "2026Oct12SportsDayclosed;Oct16notlistedholiday. Sep21-23holiday gap present in history and not filled."
        },
        {
          "source_id": "FAST-10",
          "title": "Issuer stock split record",
          "url": "https://www.fastretailing.com/eng/ir/stockinfo/trend.html",
          "publisher": "Fast Retailing",
          "source_clock": {
            "original": "Dated source observations detailed in retained research receipt",
            "published_at_utc": null,
            "precision": "source-specific"
          },
          "retrieved_at_utc": "2026-10-09T05:02:00Z",
          "retrieval_time_precision": "approximate_tool_interval",
          "review_method": "Last updatedJan8,2026 lists latest splitMar1,2023. No claim of independently exhaustive intrayear action feed; sample treated as displayed price series, not total return."
        },
        {
          "source_id": "FAST-MONTHLY-202609",
          "title": "September 2026 UNIQLO Japan same-store and online sales",
          "url": "https://www.fastretailing.com/eng/ir/monthly/",
          "publisher": "Fast Retailing",
          "source_clock": {
            "original": "Last Updated: 2026.10.02",
            "published_at_utc": null,
            "precision": "date"
          },
          "retrieved_at_utc": "2026-10-09T05:16:54.913Z",
          "retrieval_time_precision": "tool-completion bound",
          "review_method": "Read official monthly table and comment: net sales 110.8, customer numbers 99.5, purchase per customer 111.3 versus prior year 100; directly run Japan stores including online, excluding franchises."
        }
      ],
      "source_links": [
        "https://www.fastretailing.com/eng/ir/news/2610081800.html",
        "https://www.fastretailing.com/eng/ir/library/pdf/20261008_results_en.pdf",
        "https://www.fastretailing.com/eng/ir/library/pdf/tanshin202608_4q_eng.pdf",
        "https://www.fastretailing.com/eng/ir/news/2607091800.html",
        "https://s.kabutan.jp/stocks/9983/historical_prices/daily/",
        "https://www.fastretailing.com/eng/ir/stockinfo/stockchart.html",
        "https://parts.stockweather.co.jp/stocks/ir/contents/9983/chartV2.aspx?lang=en",
        "https://www.jpx.co.jp/english/equities/trading/domestic/01.html",
        "https://www.jpx.co.jp/english/corporate/about-jpx/calendar/",
        "https://www.fastretailing.com/eng/ir/stockinfo/trend.html",
        "https://www.fastretailing.com/eng/ir/monthly/"
      ],
      "source_confidence": {
        "verified": true,
        "label": "Primary issuer results and dated price observations; forecast remains subjective and uncalibrated."
      },
      "source_gaps": [
        "Only daily historical OHLCV were obtained; no 1m, 5m, 15m, 1h or 4h history or tick archive.",
        "No matched-event backtest, learned likelihoods, held-out calibration, or after-cost edge estimate.",
        "No verified analyst consensus, order flow, borrow cost, short interest or representative social sentiment.",
        "History is an as-displayed price series, not dividend-adjusted total return.",
        "StockWeather price time is minute-precision; trading volume is delayed 15 minutes.",
        "Forecast tax/minority-interest allocation not separately verified; do not attribute the whole profit-line difference to operations."
      ],
      "probability_model_version": "OTR-SUBJECTIVE-9983-EARNINGS-RESET-20261009-1",
      "probability_input": {
        "mode": "subjective",
        "label": "Subjective UNCALIBRATED scenario estimates; separate sign-only directional result",
        "bullishPercent": 29,
        "bearishPercent": 52,
        "neutralPercent": 19,
        "neutralBandPct": 1,
        "horizonHours": 168,
        "referencePrice": 72030,
        "currency": "JPY",
        "instrument": "Fast Retailing ordinary shares (9983)",
        "venue": "Tokyo Stock Exchange Prime",
        "referenceSession": "TSE Prime regular cash trading, afternoon session 12:30–15:30 JST. Entry is Friday 9 October. The 168-hour horizon includes the weekend and the 12 October Sports Day closure; expiry is in the normally open Friday 16 October afternoon session.",
        "preparedAtUTC": "2026-10-09T05:20:29.009Z",
        "deadlineUTC": "2026-10-16T05:20:29.009Z",
        "issueUTC": "2026-10-09T05:20:29.009Z",
        "expiryUTC": "2026-10-16T05:20:29.009Z",
        "entryQuoteMaximumAgeSeconds": 120,
        "bayesian": "We assign 52% to a fall greater than 1%, 29% to a rise greater than 1%, and 19% to a return in the inclusive ±1% band over 168 hours. The reversal after a 10.24% pre-results run-up, the wider daily range and the earlier post-earnings continuation favour the bearish scenario. Robust international growth, positive September sales and the bounce from the day low favour the bullish scenario; digestion of the initial move supports neutral. These are source-grounded subjective beliefs. No fitted likelihood ratios, calibrated posterior or statistical confidence interval is claimed, and the past ledger accuracy is not an input.",
        "deFinetti": "The 80 rolling weekly windows overlap heavily. Even the 18 non-overlapping intervals are not a set of independent earnings shocks, and their daily-close starts differ from this intraday reference. July is a single comparator with different expectations and seasonality. Issuer documents share an origin; Kabutan history and StockWeather live prices describe the same TSE instrument and cannot be counted as independent market opinions. We retain one distribution rather than multiplying these dependent observations into false precision.",
        "kolmogorov": "29+52+19=100. Bullish means R>+1%; bearish means R<−1%; neutral means −1%≤R≤+1%, where R=(P1/P0−1)×100. These events are disjoint and exhaustive for a valid endpoint. Separately, the BEARISH directional call is a HIT whenever P1<P0; flat or higher is a MISS. A small negative return can be both a neutral scenario and a directional HIT. Missing or non-comparable endpoint evidence is UNVERIFIABLE, never neutral. Coherence is not calibration.",
        "rationale": "We assign 52% to a fall greater than 1%, 29% to a rise greater than 1%, and 19% to a return in the inclusive ±1% band over 168 hours. The reversal after a 10.24% pre-results run-up, the wider daily range and the earlier post-earnings continuation favour the bearish scenario. Robust international growth, positive September sales and the bounce from the day low favour the bullish scenario; digestion of the initial move supports neutral. These are source-grounded subjective beliefs. No fitted likelihood ratios, calibrated posterior or statistical confidence interval is claimed, and the past ledger accuracy is not an input.",
        "againstThisView": "The company still forecasts strong operating growth overseas and higher group business profit margins. September UNIQLO Japan same-store sales including online rose 10.8%, which argues against treating summer weakness as permanent. Customer numbers fell 0.5% while average purchase per customer rose 11.3%, so the rebound should not be called a broad traffic recovery. Higher dividends and cash reserves can attract buyers. At the research snapshot the shares had already bounced 0.9495% from the day low and remained 0.7385% above the 2 October close. Much of the reset may already be priced. Business profit, net profit and currency gains are not interchangeable; the complete forecast tax and minority-interest bridge was not separately verified. [CFO operating outlook](https://www.fastretailing.com/eng/ir/library/pdf/20261008_results_en.pdf#page=23) [September monthly sales](https://www.fastretailing.com/eng/ir/monthly/)",
        "whatChangesIt": "A sustained recovery through the 8 October closing area of ¥74,800, backed by revised profit expectations or evidence that stronger overseas demand absorbs the cost pressure, would weaken this bearish thesis. A failure to extend below the 9 October morning low of ¥71,620 would also challenge follow-through, but is not itself a trade trigger. These are review conditions. They never move the frozen reference, deadline, percentage split or eventual sign-only score.",
        "resolutionRule": "Frozen P0 is ¥72,030.0 per ordinary share. Research issue 2026-10-09T05:20:29.009Z; exact deadline 2026-10-16T05:20:29.009Z, 168 elapsed calendar hours later. Resolve against the nearest legitimate dated last-price observation for Fast Retailing ordinary shares (9983), TSE Prime, JPY, within the 16 October 2026 afternoon regular session, 12:30–15:30 JST (03:30–06:30 UTC), containing the exact 168-hour deadline. Do not drift to a different session. Use the issuer-linked StockWeather last-price display when available; another permitted provider is eligible only if it identifies the same Tokyo ordinary share, a genuine dated regular-session last price, and its timestamp precision. Do not substitute an OHLC minute close, BID, ASK, midpoint, Hong Kong receipt, ADR, CFD, current late quote or carried closed-session value. Among eligible observations select the one whose disclosed observation clock is nearest the exact deadline; earlier observation wins an equal-distance tie. A displayed minute is minute-precision, not proof of an exact minute-start trade. For a minute-only clock, use its minute start as the declared timestamp proxy, retain the full one-minute uncertainty interval and report the signed proxy-minus-deadline offset and corresponding offset interval. For a finer verified clock, retain its actual precision and signed observation-minus-deadline offset. No arbitrary 15-minute hard-fail window is added. Never move the original expiry. Return=(P1/P0−1)×100. BEARISH is a HIT if P1<P0; flat or higher is a MISS. The inclusive ±1% neutral scenario band never sets the HIT threshold. If no legitimate comparable dated endpoint exists in the specified session, mark UNVERIFIABLE. If an unexpected closure, suspension or corporate action prevents a like-for-like raw share-price comparison, disclose it; do not invent a price or silently change product, session or deadline.",
        "priceBasis": "Fast Retailing ordinary shares (9983), TSE Prime, JPY per share. StockWeather displays real-time last price ¥72,030.0 at 2026/10/09 14:20 JST, a minute-precision source clock covering [2026-10-09T05:20:00.000Z, 2026-10-09T05:21:00.000Z). The minute start is a timestamp proxy, not a claim of an exact trade at second zero. Retrieved 2026-10-09T05:20:27.499Z; actual research issue 2026-10-09T05:20:29.009Z; conservative maximum observation age at issue 29.009 seconds. The signed minute-proxy-minus-issue offset is -29.009 seconds. Trading volume alone is labelled 15 minutes delayed. This is an observed market-data reference, not an executed trade or guaranteed fill.",
        "sources": [
          "OTR Database Data",
          "https://www.fastretailing.com/eng/ir/news/2610081800.html",
          "https://www.fastretailing.com/eng/ir/library/pdf/20261008_results_en.pdf",
          "https://www.fastretailing.com/eng/ir/library/pdf/tanshin202608_4q_eng.pdf",
          "https://www.fastretailing.com/eng/ir/news/2607091800.html",
          "https://s.kabutan.jp/stocks/9983/historical_prices/daily/",
          "https://www.fastretailing.com/eng/ir/stockinfo/stockchart.html",
          "https://parts.stockweather.co.jp/stocks/ir/contents/9983/chartV2.aspx?lang=en",
          "https://www.jpx.co.jp/english/equities/trading/domestic/01.html",
          "https://www.jpx.co.jp/english/corporate/about-jpx/calendar/",
          "https://www.fastretailing.com/eng/ir/stockinfo/trend.html",
          "https://www.fastretailing.com/eng/ir/monthly/"
        ],
        "calibration_note": "Subjective, not trained or backfilled onto prior calls.",
        "priceUnit": "JPY per ordinary share",
        "quoteTimeUTC": "2026-10-09T05:20:00.000Z",
        "quoteRetrievedAtUTC": "2026-10-09T05:20:27.499Z",
        "quoteAgeAtIssueSeconds": 29.009218,
        "resolutionObservationPolicy": "nearest_legitimate_same_instrument_TSE_last_price_in_expiry_afternoon_session",
        "resolutionTimestampBasis": "verified_source_clock_with_precision_disclosed;minute_only_uses_minute_start_proxy_and_full_minute_uncertainty",
        "resolutionTieBreak": "earlier",
        "resolutionMaximumOffsetSeconds": null,
        "resolutionOffsetDisclosureRequired": true,
        "outcomeDefinitions": {
          "bullish": "Return>+1%",
          "bearish": "Return<−1%",
          "neutral": "Inclusive −1% through +1%"
        },
        "sourceCutoffUTC": "2026-10-09T05:20:29.009Z",
        "resolutionEligibleSession": {
          "date_jst": "2026-10-16",
          "session": "afternoon regular TSE cash session",
          "start_utc": "2026-10-16T03:30:00Z",
          "end_utc": "2026-10-16T06:30:00Z"
        },
        "quoteAgeIsConservativeUpperBound": true,
        "quoteTimePrecisionSeconds": 60,
        "quoteObservationIntervalUTC": {
          "start_inclusive": "2026-10-09T05:20:00.000Z",
          "end_exclusive": "2026-10-09T05:21:00.000Z"
        },
        "signedSourceProxyMinusIssueSeconds": -29.009218
      },
      "analysis": {
        "mechanism": "Fast Retailing’s first post-results session has reversed an opening gain after a sharp pre-results rise. We lean bearish for 168 hours because investors may keep reducing the price they pay for the next year’s earnings while Japan’s cost pressure and slower group profit growth are reassessed. Overseas growth and an already-large fall make a rebound a serious risk.",
        "impact": "We assign 52% to a fall greater than 1%, 29% to a rise greater than 1%, and 19% to a return in the inclusive ±1% band over 168 hours. The reversal after a 10.24% pre-results run-up, the wider daily range and the earlier post-earnings continuation favour the bearish scenario. Robust international growth, positive September sales and the bounce from the day low favour the bullish scenario; digestion of the initial move supports neutral. These are source-grounded subjective beliefs. No fitted likelihood ratios, calibrated posterior or statistical confidence interval is claimed, and the past ledger accuracy is not an input.",
        "key_points": [
          "The 8 October company update forecasts FY2027 business profit growth of 15.5%, operating profit growth of 11.7%, and profit attributable to owners growth of 3.2%. These are different accounting lines. The finance-income forecast is lower and last year’s other net income is not carried into the forecast, so 3.2% is not evidence that core operations have stopped growing. Japan’s business profit is expected to be flat as weaker hedged yen rates raise buying costs. International profit is still expected to grow at double-digit rates. [Official summary](https://www.fastretailing.com/eng/ir/news/2610081800.html) [Profit bridge, page 22](https://www.fastretailing.com/eng/ir/library/pdf/20261008_results_en.pdf#page=22)",
          "The retained numerical history contains 90 completed TSE daily OHLCV rows from 29 May to 8 October. From the 28 September close to 8 October, the share price rose 10.2432%. At the separate 9 October 14:02 JST research observation, it was ¥72,300, down 3.3422% from the prior close and 4.2384% from its ¥75,500 opening. The ¥3,980 intraday range was 2.2395 times the previous 14-session average true range of ¥1,777.14. This reversal provides the price evidence for our cautious bearish view; it does not identify who sold or why. The research snapshot is not the final entry reference. [Daily table](https://s.kabutan.jp/stocks/9983/historical_prices/daily/) [Real-time price page](https://parts.stockweather.co.jp/stocks/ir/contents/9983/chartV2.aspx?lang=en)",
          "The company still forecasts strong operating growth overseas and higher group business profit margins. September UNIQLO Japan same-store sales including online rose 10.8%, which argues against treating summer weakness as permanent. Customer numbers fell 0.5% while average purchase per customer rose 11.3%, so the rebound should not be called a broad traffic recovery. Higher dividends and cash reserves can attract buyers. At the research snapshot the shares had already bounced 0.9495% from the day low and remained 0.7385% above the 2 October close. Much of the reset may already be priced. Business profit, net profit and currency gains are not interchangeable; the complete forecast tax and minority-interest bridge was not separately verified. [CFO operating outlook](https://www.fastretailing.com/eng/ir/library/pdf/20261008_results_en.pdf#page=23) [September monthly sales](https://www.fastretailing.com/eng/ir/monthly/)"
        ],
        "invalidation": "A sustained recovery through the 8 October closing area of ¥74,800, backed by revised profit expectations or evidence that stronger overseas demand absorbs the cost pressure, would weaken this bearish thesis. A failure to extend below the 9 October morning low of ¥71,620 would also challenge follow-through, but is not itself a trade trigger. These are review conditions. They never move the frozen reference, deadline, percentage split or eventual sign-only score.",
        "directional_takeaway": "BEARISH, 168H",
        "named_assets": [
          {
            "name": "Fast Retailing ordinary shares",
            "ticker": "9983.T",
            "symbol": "9983.T",
            "direction": "BEARISH",
            "currency": "JPY",
            "venue": "Tokyo Stock Exchange Prime"
          }
        ]
      },
      "expanded_sections": [
        {
          "title": "What changed?",
          "text": "The 8 October company update forecasts FY2027 business profit growth of 15.5%, operating profit growth of 11.7%, and profit attributable to owners growth of 3.2%. These are different accounting lines. The finance-income forecast is lower and last year’s other net income is not carried into the forecast, so 3.2% is not evidence that core operations have stopped growing. Japan’s business profit is expected to be flat as weaker hedged yen rates raise buying costs. International profit is still expected to grow at double-digit rates. [Official summary](https://www.fastretailing.com/eng/ir/news/2610081800.html) [Profit bridge, page 22](https://www.fastretailing.com/eng/ir/library/pdf/20261008_results_en.pdf#page=22)"
        },
        {
          "title": "Behavioural fingerprint",
          "text": "The retained numerical history contains 90 completed TSE daily OHLCV rows from 29 May to 8 October. From the 28 September close to 8 October, the share price rose 10.2432%. At the separate 9 October 14:02 JST research observation, it was ¥72,300, down 3.3422% from the prior close and 4.2384% from its ¥75,500 opening. The ¥3,980 intraday range was 2.2395 times the previous 14-session average true range of ¥1,777.14. This reversal provides the price evidence for our cautious bearish view; it does not identify who sold or why. The research snapshot is not the final entry reference. [Daily table](https://s.kabutan.jp/stocks/9983/historical_prices/daily/) [Real-time price page](https://parts.stockweather.co.jp/stocks/ir/contents/9983/chartV2.aspx?lang=en)"
        },
        {
          "title": "Historical comparables",
          "text": "After the company’s 9 July results, the next day’s closing price fell 3.5928%, from ¥85,170 to ¥82,110. From that 10 July close to the 17 July close, it fell a further 3.9825%. This is one prior earnings episode, not a measured success rate. Across the full 90-row sample, 80 overlapping exact seven-calendar-day close-to-close windows produced 29 returns above +1%, 39 below −1%, and 12 inside the inclusive ±1% band. A chronological non-overlapping selection leaves 18 intervals: 8 bullish, 9 bearish, 1 neutral. They start at daily closes, span different regimes and may share boundary prices; they do not calibrate this intraday-start forecast. [Prior results](https://www.fastretailing.com/eng/ir/news/2607091800.html) [Price history](https://s.kabutan.jp/stocks/9983/historical_prices/daily/)"
        },
        {
          "title": "Evidence graph",
          "text": "OTR Database Data supplied the research lead. We checked the company’s summary, detailed accounts and CFO presentation as one issuer evidence cluster, rather than three independent votes. The separate price cluster links the same Tokyo ordinary share to the post-release reversal and earlier earnings episode. The mechanism is a possible repricing of earnings expectations after the run-up, with procurement costs limiting Japan’s contribution. The inference remains unproven: we have no verified consensus forecast, order-flow record or short-interest series, so we do not claim an analyst-guidance miss or a demonstrated cause of the sell-off."
        },
        {
          "title": "Opposing evidence",
          "text": "The company still forecasts strong operating growth overseas and higher group business profit margins. September UNIQLO Japan same-store sales including online rose 10.8%, which argues against treating summer weakness as permanent. Customer numbers fell 0.5% while average purchase per customer rose 11.3%, so the rebound should not be called a broad traffic recovery. Higher dividends and cash reserves can attract buyers. At the research snapshot the shares had already bounced 0.9495% from the day low and remained 0.7385% above the 2 October close. Much of the reset may already be priced. Business profit, net profit and currency gains are not interchangeable; the complete forecast tax and minority-interest bridge was not separately verified. [CFO operating outlook](https://www.fastretailing.com/eng/ir/library/pdf/20261008_results_en.pdf#page=23) [September monthly sales](https://www.fastretailing.com/eng/ir/monthly/)"
        },
        {
          "title": "Invalidation",
          "text": "A sustained recovery through the 8 October closing area of ¥74,800, backed by revised profit expectations or evidence that stronger overseas demand absorbs the cost pressure, would weaken this bearish thesis. A failure to extend below the 9 October morning low of ¥71,620 would also challenge follow-through, but is not itself a trade trigger. These are review conditions. They never move the frozen reference, deadline, percentage split or eventual sign-only score."
        },
        {
          "title": "Bottom line",
          "text": "BEARISH over 168 elapsed calendar hours, from 2026-10-09T05:20:29.009Z to 2026-10-16T05:20:29.009Z, referenced to ¥72,030.0. The scenario split is 29% bullish, 52% bearish and 19% neutral around an inclusive ±1% return band. These estimates are subjective and UNCALIBRATED. This is a weak-to-moderate research judgement. The window includes the 12 October Tokyo holiday and expires in a normally open afternoon session. A lower comparable endpoint is a directional HIT; flat or higher is a MISS, regardless of the scenario band. No profit after fees, taxes, financing, borrow costs or currency conversion is promised."
        }
      ],
      "accordion_sections": [
        {
          "title": "How likely is this call? · Three frameworks",
          "text": "29% bullish / 52% bearish / 19% neutral; subjective UNCALIBRATED; inclusive ±1% band; 168 hours.",
          "nested_sections": [
            {
              "title": "Bayesian · what changed the estimate?",
              "text": "We assign 52% to a fall greater than 1%, 29% to a rise greater than 1%, and 19% to a return in the inclusive ±1% band over 168 hours. The reversal after a 10.24% pre-results run-up, the wider daily range and the earlier post-earnings continuation favour the bearish scenario. Robust international growth, positive September sales and the bounce from the day low favour the bullish scenario; digestion of the initial move supports neutral. These are source-grounded subjective beliefs. No fitted likelihood ratios, calibrated posterior or statistical confidence interval is claimed, and the past ledger accuracy is not an input."
            },
            {
              "title": "de Finetti · are the comparisons fair?",
              "text": "The 80 rolling weekly windows overlap heavily. Even the 18 non-overlapping intervals are not a set of independent earnings shocks, and their daily-close starts differ from this intraday reference. July is a single comparator with different expectations and seasonality. Issuer documents share an origin; Kabutan history and StockWeather live prices describe the same TSE instrument and cannot be counted as independent market opinions. We retain one distribution rather than multiplying these dependent observations into false precision."
            },
            {
              "title": "Kolmogorov · do the numbers agree?",
              "text": "29+52+19=100. Bullish means R>+1%; bearish means R<−1%; neutral means −1%≤R≤+1%, where R=(P1/P0−1)×100. These events are disjoint and exhaustive for a valid endpoint. Separately, the BEARISH directional call is a HIT whenever P1<P0; flat or higher is a MISS. A small negative return can be both a neutral scenario and a directional HIT. Missing or non-comparable endpoint evidence is UNVERIFIABLE, never neutral. Coherence is not calibration."
            }
          ]
        },
        {
          "title": "Model audit",
          "text": "One 168-hour hypothesis; no calibrated model. Descriptive calculations are reproducible from 90 retained daily rows. Alternative bullish and neutral scenarios remain material. No unsupported net-profit-to-share-price causal claim."
        },
        {
          "title": "Raw data provenance",
          "text": "Three permitted Kabutan pages provided 90 completed TSE daily OHLCV rows, 29 May–8 October. No chart pixels, interpolation or current-day close was invented. StockWeather provides a separate real-time price with a minute clock and 15-minute-delayed volume. The final quote is independently retained with its displayed clock, retrieval clock and exact issue age. Internal lead: OTR Database Data. Public raw third-party series is not redistributed."
        },
        {
          "title": "Resolution ledger",
          "text": "Frozen P0 is ¥72,030.0 per ordinary share. Research issue 2026-10-09T05:20:29.009Z; exact deadline 2026-10-16T05:20:29.009Z, 168 elapsed calendar hours later. Resolve against the nearest legitimate dated last-price observation for Fast Retailing ordinary shares (9983), TSE Prime, JPY, within the 16 October 2026 afternoon regular session, 12:30–15:30 JST (03:30–06:30 UTC), containing the exact 168-hour deadline. Do not drift to a different session. Use the issuer-linked StockWeather last-price display when available; another permitted provider is eligible only if it identifies the same Tokyo ordinary share, a genuine dated regular-session last price, and its timestamp precision. Do not substitute an OHLC minute close, BID, ASK, midpoint, Hong Kong receipt, ADR, CFD, current late quote or carried closed-session value. Among eligible observations select the one whose disclosed observation clock is nearest the exact deadline; earlier observation wins an equal-distance tie. A displayed minute is minute-precision, not proof of an exact minute-start trade. For a minute-only clock, use its minute start as the declared timestamp proxy, retain the full one-minute uncertainty interval and report the signed proxy-minus-deadline offset and corresponding offset interval. For a finer verified clock, retain its actual precision and signed observation-minus-deadline offset. No arbitrary 15-minute hard-fail window is added. Never move the original expiry. Return=(P1/P0−1)×100. BEARISH is a HIT if P1<P0; flat or higher is a MISS. The inclusive ±1% neutral scenario band never sets the HIT threshold. If no legitimate comparable dated endpoint exists in the specified session, mark UNVERIFIABLE. If an unexpected closure, suspension or corporate action prevents a like-for-like raw share-price comparison, disclose it; do not invent a price or silently change product, session or deadline."
        }
      ],
      "resolution_rule": "Frozen P0 is ¥72,030.0 per ordinary share. Research issue 2026-10-09T05:20:29.009Z; exact deadline 2026-10-16T05:20:29.009Z, 168 elapsed calendar hours later. Resolve against the nearest legitimate dated last-price observation for Fast Retailing ordinary shares (9983), TSE Prime, JPY, within the 16 October 2026 afternoon regular session, 12:30–15:30 JST (03:30–06:30 UTC), containing the exact 168-hour deadline. Do not drift to a different session. Use the issuer-linked StockWeather last-price display when available; another permitted provider is eligible only if it identifies the same Tokyo ordinary share, a genuine dated regular-session last price, and its timestamp precision. Do not substitute an OHLC minute close, BID, ASK, midpoint, Hong Kong receipt, ADR, CFD, current late quote or carried closed-session value. Among eligible observations select the one whose disclosed observation clock is nearest the exact deadline; earlier observation wins an equal-distance tie. A displayed minute is minute-precision, not proof of an exact minute-start trade. For a minute-only clock, use its minute start as the declared timestamp proxy, retain the full one-minute uncertainty interval and report the signed proxy-minus-deadline offset and corresponding offset interval. For a finer verified clock, retain its actual precision and signed observation-minus-deadline offset. No arbitrary 15-minute hard-fail window is added. Never move the original expiry. Return=(P1/P0−1)×100. BEARISH is a HIT if P1<P0; flat or higher is a MISS. The inclusive ±1% neutral scenario band never sets the HIT threshold. If no legitimate comparable dated endpoint exists in the specified session, mark UNVERIFIABLE. If an unexpected closure, suspension or corporate action prevents a like-for-like raw share-price comparison, disclose it; do not invent a price or silently change product, session or deadline.",
      "resolution_ledger": {
        "status": "PENDING",
        "result": null,
        "issue_utc": "2026-10-09T05:20:29.009Z",
        "expiry_utc": "2026-10-16T05:20:29.009Z",
        "price1": 72030,
        "price1_source_clock_utc": "2026-10-09T05:20:00.000Z",
        "price2": null,
        "price_basis": "Fast Retailing ordinary shares (9983), TSE Prime, JPY per share. StockWeather displays real-time last price ¥72,030.0 at 2026/10/09 14:20 JST, a minute-precision source clock covering [2026-10-09T05:20:00.000Z, 2026-10-09T05:21:00.000Z). The minute start is a timestamp proxy, not a claim of an exact trade at second zero. Retrieved 2026-10-09T05:20:27.499Z; actual research issue 2026-10-09T05:20:29.009Z; conservative maximum observation age at issue 29.009 seconds. The signed minute-proxy-minus-issue offset is -29.009 seconds. Trading volume alone is labelled 15 minutes delayed. This is an observed market-data reference, not an executed trade or guaranteed fill.",
        "resolution_rule": "Frozen P0 is ¥72,030.0 per ordinary share. Research issue 2026-10-09T05:20:29.009Z; exact deadline 2026-10-16T05:20:29.009Z, 168 elapsed calendar hours later. Resolve against the nearest legitimate dated last-price observation for Fast Retailing ordinary shares (9983), TSE Prime, JPY, within the 16 October 2026 afternoon regular session, 12:30–15:30 JST (03:30–06:30 UTC), containing the exact 168-hour deadline. Do not drift to a different session. Use the issuer-linked StockWeather last-price display when available; another permitted provider is eligible only if it identifies the same Tokyo ordinary share, a genuine dated regular-session last price, and its timestamp precision. Do not substitute an OHLC minute close, BID, ASK, midpoint, Hong Kong receipt, ADR, CFD, current late quote or carried closed-session value. Among eligible observations select the one whose disclosed observation clock is nearest the exact deadline; earlier observation wins an equal-distance tie. A displayed minute is minute-precision, not proof of an exact minute-start trade. For a minute-only clock, use its minute start as the declared timestamp proxy, retain the full one-minute uncertainty interval and report the signed proxy-minus-deadline offset and corresponding offset interval. For a finer verified clock, retain its actual precision and signed observation-minus-deadline offset. No arbitrary 15-minute hard-fail window is added. Never move the original expiry. Return=(P1/P0−1)×100. BEARISH is a HIT if P1<P0; flat or higher is a MISS. The inclusive ±1% neutral scenario band never sets the HIT threshold. If no legitimate comparable dated endpoint exists in the specified session, mark UNVERIFIABLE. If an unexpected closure, suspension or corporate action prevents a like-for-like raw share-price comparison, disclose it; do not invent a price or silently change product, session or deadline.",
        "price2_observed_at_utc": null,
        "endpoint_signed_offset_seconds": null
      },
      "supplied_reference_quote": {
        "display": "¥72,030.0 per ordinary share, TSE last price",
        "price": 72030,
        "currency": "JPY",
        "unit": "JPY per ordinary share",
        "venue": "Tokyo Stock Exchange Prime",
        "instrument": "Fast Retailing ordinary shares (9983)",
        "symbol": "9983.T",
        "session": "TSE Prime regular cash trading, afternoon session 12:30–15:30 JST. Entry is Friday 9 October. The 168-hour horizon includes the weekend and the 12 October Sports Day closure; expiry is in the normally open Friday 16 October afternoon session.",
        "as_of_utc": "2026-10-09T05:20:00.000Z",
        "as_of_display": "2026/10/09 14:20 JST",
        "source_url": "https://parts.stockweather.co.jp/stocks/ir/contents/9983/chartV2.aspx?lang=en",
        "retrieved_at_utc": "2026-10-09T05:20:27.499Z",
        "verification_status": "VERIFIED_PROVIDER_REAL_TIME_LAST_PRICE_WITH_MINUTE_CLOCK",
        "observation_time_verified": true,
        "observation_clock_basis": "Displayed StockWeather last-price minute clock in JST; minute-start proxy used conservatively, not an exact trade timestamp.",
        "observation_time_precision_seconds": 60,
        "observation_interval_utc": {
          "start_inclusive": "2026-10-09T05:20:00.000Z",
          "end_exclusive": "2026-10-09T05:21:00.000Z"
        },
        "quote_age_at_issue_seconds": 29.009218,
        "quote_age_is_conservative_upper_bound": true,
        "signed_source_proxy_minus_issue_seconds": -29.009218,
        "executed_trade_verified": false,
        "price_type": "LAST",
        "volume_delay_minutes": 15,
        "source_receipt_sha256": "bb1864158046b6142a235779ea87f986b13b2761aa9ce3c445066a5c1fe67764",
        "session_fields": {
          "Open": 75500,
          "High": 75600,
          "Low": 71620,
          "Volume": 1651900,
          "Previous": 74800
        }
      },
      "current_price_display": "¥72,030.0 per ordinary share, TSE last price",
      "change_24h_display": "",
      "blank_change_24h": true,
      "supplied_intelligence_layers": {
        "evidenceClusters": [
          "OTR Database Data supplied the research lead. We checked the company’s summary, detailed accounts and CFO presentation as one issuer evidence cluster, rather than three independent votes. The separate price cluster links the same Tokyo ordinary share to the post-release reversal and earlier earnings episode. The mechanism is a possible repricing of earnings expectations after the run-up, with procurement costs limiting Japan’s contribution. The inference remains unproven: we have no verified consensus forecast, order-flow record or short-interest series, so we do not claim an analyst-guidance miss or a demonstrated cause of the sell-off."
        ],
        "behaviouralMemory": [
          "The retained numerical history contains 90 completed TSE daily OHLCV rows from 29 May to 8 October. From the 28 September close to 8 October, the share price rose 10.2432%. At the separate 9 October 14:02 JST research observation, it was ¥72,300, down 3.3422% from the prior close and 4.2384% from its ¥75,500 opening. The ¥3,980 intraday range was 2.2395 times the previous 14-session average true range of ¥1,777.14. This reversal provides the price evidence for our cautious bearish view; it does not identify who sold or why. The research snapshot is not the final entry reference. [Daily table](https://s.kabutan.jp/stocks/9983/historical_prices/daily/) [Real-time price page](https://parts.stockweather.co.jp/stocks/ir/contents/9983/chartV2.aspx?lang=en)",
          "After the company’s 9 July results, the next day’s closing price fell 3.5928%, from ¥85,170 to ¥82,110. From that 10 July close to the 17 July close, it fell a further 3.9825%. This is one prior earnings episode, not a measured success rate. Across the full 90-row sample, 80 overlapping exact seven-calendar-day close-to-close windows produced 29 returns above +1%, 39 below −1%, and 12 inside the inclusive ±1% band. A chronological non-overlapping selection leaves 18 intervals: 8 bullish, 9 bearish, 1 neutral. They start at daily closes, span different regimes and may share boundary prices; they do not calibrate this intraday-start forecast. [Prior results](https://www.fastretailing.com/eng/ir/news/2607091800.html) [Price history](https://s.kabutan.jp/stocks/9983/historical_prices/daily/)"
        ],
        "counterfactualAudit": [
          "The company still forecasts strong operating growth overseas and higher group business profit margins. September UNIQLO Japan same-store sales including online rose 10.8%, which argues against treating summer weakness as permanent. Customer numbers fell 0.5% while average purchase per customer rose 11.3%, so the rebound should not be called a broad traffic recovery. Higher dividends and cash reserves can attract buyers. At the research snapshot the shares had already bounced 0.9495% from the day low and remained 0.7385% above the 2 October close. Much of the reset may already be priced. Business profit, net profit and currency gains are not interchangeable; the complete forecast tax and minority-interest bridge was not separately verified. [CFO operating outlook](https://www.fastretailing.com/eng/ir/library/pdf/20261008_results_en.pdf#page=23) [September monthly sales](https://www.fastretailing.com/eng/ir/monthly/)"
        ],
        "signalReversalTracker": [
          "New instrument-specific first post-FY2026-results synthesis. No earlier Fast Retailing call was found in the named-asset/title inventory. All older calls remain frozen."
        ],
        "socialRealityCheck": [
          "No representative social sample. Headline optimism is not a sentiment statistic; company outlook and observed prices are the evidence."
        ],
        "predictionCalibration": [
          "No resolved same-instrument 168-hour OTR forecast sample is available. Current ledger results are not used as probabilities."
        ]
      },
      "novelty_review": {
        "status": "NEW_INSTRUMENT_EVENT_SYNTHESIS",
        "basis": "No Fast Retailing instrument/title match in current call inventory. Raw9983substring in a software commit hash is not an asset match. The new thesis combinesOct8 company outlook withOct9 postrelease reversal, not a reissue of Brent/gold/BTC/ETH."
      },
      "review_status": "OPPOSING_REVIEW_PASSED_FRESH_REFERENCE_FROZEN",
      "source_batch": "FORCED-20261009-0454Z",
      "card_scope": "current_editorial_signal",
      "research_cutoff_utc": "2026-10-09T05:20:29.009Z",
      "scope_note": "The forecast clock is the actual research issue, with a genuinely fresh provider minute-clock last price. Website publication occurs separately and must retain its own actual timestamp. No previous forecast is reset.",
      "public_expanded_text": "What changed?\nThe 8 October company update forecasts FY2027 business profit growth of 15.5%, operating profit growth of 11.7%, and profit attributable to owners growth of 3.2%. These are different accounting lines. The finance-income forecast is lower and last year’s other net income is not carried into the forecast, so 3.2% is not evidence that core operations have stopped growing. Japan’s business profit is expected to be flat as weaker hedged yen rates raise buying costs. International profit is still expected to grow at double-digit rates. [Official summary](https://www.fastretailing.com/eng/ir/news/2610081800.html) [Profit bridge, page 22](https://www.fastretailing.com/eng/ir/library/pdf/20261008_results_en.pdf#page=22)\n\nBehavioural fingerprint\nThe retained numerical history contains 90 completed TSE daily OHLCV rows from 29 May to 8 October. From the 28 September close to 8 October, the share price rose 10.2432%. At the separate 9 October 14:02 JST research observation, it was ¥72,300, down 3.3422% from the prior close and 4.2384% from its ¥75,500 opening. The ¥3,980 intraday range was 2.2395 times the previous 14-session average true range of ¥1,777.14. This reversal provides the price evidence for our cautious bearish view; it does not identify who sold or why. The research snapshot is not the final entry reference. [Daily table](https://s.kabutan.jp/stocks/9983/historical_prices/daily/) [Real-time price page](https://parts.stockweather.co.jp/stocks/ir/contents/9983/chartV2.aspx?lang=en)\n\nHistorical comparables\nAfter the company’s 9 July results, the next day’s closing price fell 3.5928%, from ¥85,170 to ¥82,110. From that 10 July close to the 17 July close, it fell a further 3.9825%. This is one prior earnings episode, not a measured success rate. Across the full 90-row sample, 80 overlapping exact seven-calendar-day close-to-close windows produced 29 returns above +1%, 39 below −1%, and 12 inside the inclusive ±1% band. A chronological non-overlapping selection leaves 18 intervals: 8 bullish, 9 bearish, 1 neutral. They start at daily closes, span different regimes and may share boundary prices; they do not calibrate this intraday-start forecast. [Prior results](https://www.fastretailing.com/eng/ir/news/2607091800.html) [Price history](https://s.kabutan.jp/stocks/9983/historical_prices/daily/)\n\nEvidence graph\nOTR Database Data supplied the research lead. We checked the company’s summary, detailed accounts and CFO presentation as one issuer evidence cluster, rather than three independent votes. The separate price cluster links the same Tokyo ordinary share to the post-release reversal and earlier earnings episode. The mechanism is a possible repricing of earnings expectations after the run-up, with procurement costs limiting Japan’s contribution. The inference remains unproven: we have no verified consensus forecast, order-flow record or short-interest series, so we do not claim an analyst-guidance miss or a demonstrated cause of the sell-off.\n\nOpposing evidence\nThe company still forecasts strong operating growth overseas and higher group business profit margins. September UNIQLO Japan same-store sales including online rose 10.8%, which argues against treating summer weakness as permanent. Customer numbers fell 0.5% while average purchase per customer rose 11.3%, so the rebound should not be called a broad traffic recovery. Higher dividends and cash reserves can attract buyers. At the research snapshot the shares had already bounced 0.9495% from the day low and remained 0.7385% above the 2 October close. Much of the reset may already be priced. Business profit, net profit and currency gains are not interchangeable; the complete forecast tax and minority-interest bridge was not separately verified. [CFO operating outlook](https://www.fastretailing.com/eng/ir/library/pdf/20261008_results_en.pdf#page=23) [September monthly sales](https://www.fastretailing.com/eng/ir/monthly/)\n\nInvalidation\nA sustained recovery through the 8 October closing area of ¥74,800, backed by revised profit expectations or evidence that stronger overseas demand absorbs the cost pressure, would weaken this bearish thesis. A failure to extend below the 9 October morning low of ¥71,620 would also challenge follow-through, but is not itself a trade trigger. These are review conditions. They never move the frozen reference, deadline, percentage split or eventual sign-only score.\n\nBottom line\nBEARISH over 168 elapsed calendar hours, from 2026-10-09T05:20:29.009Z to 2026-10-16T05:20:29.009Z, referenced to ¥72,030.0. The scenario split is 29% bullish, 52% bearish and 19% neutral around an inclusive ±1% return band. These estimates are subjective and UNCALIBRATED. This is a weak-to-moderate research judgement. The window includes the 12 October Tokyo holiday and expires in a normally open afternoon session. A lower comparable endpoint is a directional HIT; flat or higher is a MISS, regardless of the scenario band. No profit after fees, taxes, financing, borrow costs or currency conversion is promised.",
      "history_coverage": {
        "completed_daily_rows": 90,
        "from": "2026-05-29",
        "through": "2026-10-08",
        "intraday_rows_excluded_from_closed_sample": true,
        "source_pages": 3,
        "source": "Kabutan visible numerical table",
        "timeframes_obtained": [
          "daily OHLCV"
        ],
        "missing": [
          "1m",
          "5m",
          "15m",
          "1h",
          "4h",
          "intraday matched volume baseline",
          "tick history"
        ],
        "adjustment": "As-displayed raw price return; no dividend adjustment or total-return claim; issuer split page lists last split2023-03-01, no split inferred during sample",
        "no_imputation": true
      },
      "review": {
        "status": "OPPOSING_REVIEW_PASSED_WITH_LIMITS",
        "facts_and_prices_fully_verified": false,
        "notes": "Independent reviewer replayed all retained daily calculations and challenged net-profit-line attribution, international-growth counterevidence, already-priced effects and the endpoint convention. The accounting bridge was added, no consensus claim was made, and historical minute-close substitution was removed. The endpoint is restricted to the expiry afternoon regular session with clock precision and signed offsets disclosed. Entry remains unissued until a genuinely fresh quote is frozen. Reviewer’s final citation correction was applied to the exact monthly-sales page and the online-sales scope was made explicit.",
        "reviewer": "review_fresh_signal_evidence",
        "reviewed_at_utc": "2026-10-09T05:13:21.073Z",
        "reference_quote_verified_with_limits": true,
        "reference_quote_reviewed_at_utc": "2026-10-09T05:20:29.009Z"
      },
      "formation_chain": [
        {
          "step": "Observed change",
          "text": "The retained numerical history contains 90 completed TSE daily OHLCV rows from 29 May to 8 October. From the 28 September close to 8 October, the share price rose 10.2432%. At the separate 9 October 14:02 JST research observation, it was ¥72,300, down 3.3422% from the prior close and 4.2384% from its ¥75,500 opening. The ¥3,980 intraday range was 2.2395 times the previous 14-session average true range of ¥1,777.14. This reversal provides the price evidence for our cautious bearish view; it does not identify who sold or why. The research snapshot is not the final entry reference. [Daily table](https://s.kabutan.jp/stocks/9983/historical_prices/daily/) [Real-time price page](https://parts.stockweather.co.jp/stocks/ir/contents/9983/chartV2.aspx?lang=en)"
        },
        {
          "step": "Transmission",
          "text": "OTR Database Data supplied the research lead. We checked the company’s summary, detailed accounts and CFO presentation as one issuer evidence cluster, rather than three independent votes. The separate price cluster links the same Tokyo ordinary share to the post-release reversal and earlier earnings episode. The mechanism is a possible repricing of earnings expectations after the run-up, with procurement costs limiting Japan’s contribution. The inference remains unproven: we have no verified consensus forecast, order-flow record or short-interest series, so we do not claim an analyst-guidance miss or a demonstrated cause of the sell-off."
        },
        {
          "step": "Already reflected",
          "text": "The research quote already includes a 3.34% one-day fall; no past fall counts as this forecast’s success."
        },
        {
          "step": "Opposition",
          "text": "The company still forecasts strong operating growth overseas and higher group business profit margins. September UNIQLO Japan same-store sales including online rose 10.8%, which argues against treating summer weakness as permanent. Customer numbers fell 0.5% while average purchase per customer rose 11.3%, so the rebound should not be called a broad traffic recovery. Higher dividends and cash reserves can attract buyers. At the research snapshot the shares had already bounced 0.9495% from the day low and remained 0.7385% above the 2 October close. Much of the reset may already be priced. Business profit, net profit and currency gains are not interchangeable; the complete forecast tax and minority-interest bridge was not separately verified. [CFO operating outlook](https://www.fastretailing.com/eng/ir/library/pdf/20261008_results_en.pdf#page=23) [September monthly sales](https://www.fastretailing.com/eng/ir/monthly/)"
        },
        {
          "step": "Timeboxed judgment",
          "text": "BEARISH over 168 elapsed calendar hours, from 2026-10-09T05:20:29.009Z to 2026-10-16T05:20:29.009Z, referenced to ¥72,030.0. The scenario split is 29% bullish, 52% bearish and 19% neutral around an inclusive ±1% return band. These estimates are subjective and UNCALIBRATED. This is a weak-to-moderate research judgement. The window includes the 12 October Tokyo holiday and expires in a normally open afternoon session. A lower comparable endpoint is a directional HIT; flat or higher is a MISS, regardless of the scenario band. No profit after fees, taxes, financing, borrow costs or currency conversion is promised."
        }
      ],
      "forecast_clock_basis": "FORECAST_PREPARED_RESEARCH_CLOCK_NOT_NATIVE_DEPLOYMENT",
      "forecast_clock_label": "Forecast prepared",
      "evidence_cutoff_utc": "2026-10-09T05:20:29.009Z",
      "card_evidence_cutoff_utc": "2026-10-09T05:20:29.009Z",
      "release_id": "OTR-SIGNALS-20261009-052420Z-FORCE-1",
      "fact_review_state": "OPPOSING_REVIEW_PASSED_FRESH_REFERENCE_FROZEN"
    },
    {
      "schema": "OTR-SIGNALS-CATEGORY-CARD-1",
      "id": "SG-20261009-MYREPUBLIC-BRAND-NETWORK-OFFERS",
      "primary_category": "singapore",
      "categories": [
        "singapore"
      ],
      "title": "MyRepublic’s planned sale adds a check before switching mobile brands",
      "summary": "We connect StarHub’s planned purchase of MyRepublic Mobile with the earlier network migration and the offers customers can actually use. The MyRepublic brand is set to remain, while selected advertised port-in offers exclude StarHub and its virtual-network customers. Our practical signal is to check the network behind the current line and the exact offer rules before assuming a change of brand qualifies for a switching deal.",
      "signal_claim": "We connect StarHub’s planned purchase of MyRepublic Mobile with the earlier network migration and the offers customers can actually use. The MyRepublic brand is set to remain, while selected advertised port-in offers exclude StarHub and its virtual-network customers. Our practical signal is to check the network behind the current line and the exact offer rules before assuming a change of brand qualifies for a switching deal.",
      "thesis": "We connect StarHub’s planned purchase of MyRepublic Mobile with the earlier network migration and the offers customers can actually use. The MyRepublic brand is set to remain, while selected advertised port-in offers exclude StarHub and its virtual-network customers. Our practical signal is to check the network behind the current line and the exact offer rules before assuming a change of brand qualifies for a switching deal.",
      "publication_status": "READY",
      "status": "REVIEWED_EDITORIAL_CARD",
      "key_points": [
        "We would confirm which network hosts the current line and ask whether the exact advertised offer accepts it.",
        "We would compare the full ongoing plan and its conditions after confirming eligibility.",
        "We keep existing-customer continuity, a new-customer offer and completion of the business purchase as different questions."
      ],
      "bottom_line": "We would check the actual switching conditions before choosing a new mobile brand. This is a consumer comparison signal, with no claim that the deal raises prices, improves coverage or proves that every migration has finished.",
      "analysis": {
        "mechanism": "StarHub’s 8 October statement says it plans to buy MyRepublic’s Singapore mobile business, subject to conditions being met. It says the brand and existing services will continue. These are company commitments, not a completed acquisition or independently tested service results. [Issuer statement](https://www.marketscreener.com/news/starhub-to-acquire-myrepublic-mobile-business-expanding-choice-and-strengthening-connectivity-ce785dded089f620)\n\nThe network move started as a separate agreement. On 6 August, the companies announced plans to move MyRepublic’s 4G customers onto StarHub’s network, alongside their earlier 5G wholesale relationship. The October statement still describes migration as progressive. [Earlier network agreement](https://corporate.starhub.com/about-us/newsroom/2026/August/starhub-moves-all-myrepublic-mobile-subscribers-onto-its-network.html)\n\nA separate customer-facing page makes that connection useful. At our 9 October check, MyRepublic’s 650GB and 500GB offers displayed a port-in exclusion for StarHub and its mobile virtual network operators, or MVNOs. We treat this as the condition shown for those offers, not a general ban on moving a phone number. [Advertised offer conditions](https://myrepublic.net/sg/mobile-promotions/)\n\nOur inference is that a brand comparison alone can miss an important switching condition. Ownership, the host network and qualification for an offer need separate checks. The page gives no start date for the exclusion, so we do not attribute it to the proposed purchase.",
        "impact": "We would check the actual switching conditions before choosing a new mobile brand. This is a consumer comparison signal, with no claim that the deal raises prices, improves coverage or proves that every migration has finished.",
        "uncertainties": [
          "Other offers or sign-up routes may have different conditions. Separate brands can still offer useful differences in support, allowances or service. We have not tested a checkout, ported a number or measured customer outcomes. The planned purchase may proceed without changing these offers, and the offers may change without the purchase completing.",
          "Exact earliest issuer publication time, full transaction terms and customer-specific offer acceptance were not verified."
        ],
        "countercase": "Other offers or sign-up routes may have different conditions. Separate brands can still offer useful differences in support, allowances or service. We have not tested a checkout, ported a number or measured customer outcomes. The planned purchase may proceed without changing these offers, and the offers may change without the purchase completing.",
        "next_check": "Next useful check: the exact offer terms before a customer applies, plus a dated company update confirming acquisition completion or network migration progress. No market expiry or automatic monitor is claimed.",
        "named_assets": [],
        "directional_takeaway": "Not applicable"
      },
      "named_assets": [],
      "named_actors": [
        "StarHub",
        "MyRepublic"
      ],
      "directional_takeaway": "N/A",
      "uncertainty": "Other offers or sign-up routes may have different conditions. Separate brands can still offer useful differences in support, allowances or service. We have not tested a checkout, ported a number or measured customer outcomes. The planned purchase may proceed without changing these offers, and the offers may change without the purchase completing.",
      "next_check": "Next useful check: the exact offer terms before a customer applies, plus a dated company update confirming acquisition completion or network migration progress. No market expiry or automatic monitor is claimed.",
      "check_time_utc": null,
      "check_time_label": "Next evidence check",
      "check_time_display": "Next useful check: the exact offer terms before a customer applies, plus a dated company update confirming acquisition completion or network migration progress. No market expiry or automatic monitor is claimed.",
      "source_confidence": {
        "verified": false,
        "label": "Issuer plans and advertised conditions checked; completion, checkout acceptance and customer results unverified",
        "reason": "The evidence establishes the stated plan and displayed offer condition. It does not independently establish outcomes."
      },
      "source_labels": [
        "OTR Database Data"
      ],
      "sources": [
        {
          "source_id": "SG-SH-ACQUISITION-20261008",
          "url": "https://www.starhub.com/about-us/newsroom/2026/October/starhub-to-acquire-myrepublic-mobile-business-expanding-choice-and-strengthening-connectivity.html",
          "title": "StarHub to acquire MyRepublic Mobile business",
          "publisher": "StarHub",
          "source_clock": {
            "published_at_utc": null,
            "normalized_utc": null,
            "original": "8 October 2026",
            "precision": "date",
            "time_note": "Original media page gives no exact issue clock; source text checked in indexed original and unedited issuer mirror."
          },
          "origin_cluster": "STARHUB_MYREPUBLIC_ACQUISITION_20261008",
          "review_method": "Substantive original issuer text through web search; direct webpage open returned redirect loop. Full unedited issuer mirror body read.",
          "limits": "Planned transaction and provider promises; no completed transfer or measured consumer results."
        },
        {
          "source_id": "SG-SH-ACQUISITION-MIRROR",
          "url": "https://www.marketscreener.com/news/starhub-to-acquire-myrepublic-mobile-business-expanding-choice-and-strengthening-connectivity-ce785dded089f620",
          "title": "Unedited StarHub acquisition statement via Public Technologies",
          "publisher": "StarHub via Public Technologies / MarketScreener",
          "source_clock": {
            "published_at_utc": null,
            "normalized_utc": null,
            "original": "Issuer date: 8 October 2026; distributed 8 October 2026 at 09:39 UTC; MarketScreener display 05:40 EDT",
            "precision": "Issuer date only; redistribution minute verified",
            "distribution_at_utc": "2026-10-08T09:39:00Z",
            "mirror_display_at_utc": "2026-10-08T09:40:00Z",
            "time_note": "Distribution and mirror display clocks are not substituted for earliest issuer publication."
          },
          "origin_cluster": "STARHUB_MYREPUBLIC_ACQUISITION_20261008",
          "review_method": "Full substantive issuer statement and distribution disclaimer read through web reader.",
          "limits": "Issuer mirror, not independent corroboration.",
          "observed_at_utc": "2026-10-09T05:04:34Z",
          "observation_precision": "Execution clock immediately after completed batch web-reader retrieval; batch began after 05:04:11 UTC."
        },
        {
          "source_id": "SG-SH-IR-NOTICE",
          "url": "https://ir.starhub.com/news.html/id/2629618",
          "title": "Acquisition of the Mobile Business of MyRepublic Limited: filing notice",
          "publisher": "StarHub investor relations",
          "source_clock": {
            "published_at_utc": null,
            "normalized_utc": null,
            "original": "Oct 8, 2026 17:23",
            "precision": "minute; displayed timezone absent",
            "time_note": "Public HTML labels this Date & Time of Broadcast. No timezone inferred."
          },
          "retrieved_at_utc": "2026-10-09T05:01:35.852117Z",
          "origin_cluster": "STARHUB_MYREPUBLIC_ACQUISITION_20261008",
          "review_method": "Official public HTML read and retained with announcement reference SG261008OTHRWDJP.",
          "limits": "HTML wrapper only; attached transaction terms excluded from this card."
        },
        {
          "source_id": "SG-SH-MIGRATION-20260806",
          "url": "https://corporate.starhub.com/about-us/newsroom/2026/August/starhub-moves-all-myrepublic-mobile-subscribers-onto-its-network.html",
          "title": "StarHub moves all MyRepublic Mobile subscribers onto its network",
          "publisher": "StarHub and MyRepublic",
          "source_clock": {
            "published_at_utc": null,
            "normalized_utc": null,
            "original": "6 August 2026",
            "precision": "date"
          },
          "origin_cluster": "STARHUB_MYREPUBLIC_NETWORK_AGREEMENT_20260806",
          "review_method": "Full substantive original HTML body read.",
          "limits": "Older plan; title does not prove every customer completed migration.",
          "observed_at_utc": "2026-10-09T05:04:34Z",
          "observation_precision": "Execution clock immediately after completed batch web-reader retrieval; batch began after 05:04:11 UTC."
        },
        {
          "source_id": "SG-MR-CUSTOMER-20261008",
          "url": "https://myrepublic.net/sg/blog/mobile/a-new-chapter-for-myrepublicmobile/",
          "title": "New Chapter, Same Commitment to You",
          "publisher": "MyRepublic",
          "source_clock": {
            "published_at_utc": null,
            "normalized_utc": null,
            "original": "8 October 2026",
            "precision": "date"
          },
          "origin_cluster": "STARHUB_MYREPUBLIC_ACQUISITION_20261008",
          "review_method": "Original customer statement, paragraphs below heading read in web reader.",
          "limits": "Transaction-party reassurance, not independent performance evidence or immutable future terms.",
          "observed_at_utc": "2026-10-09T05:04:34Z",
          "observation_precision": "Execution clock immediately after completed batch web-reader retrieval; batch began after 05:04:11 UTC."
        },
        {
          "source_id": "SG-MR-OFFER-SNAPSHOT-20261009",
          "url": "https://myrepublic.net/sg/mobile-promotions/",
          "title": "MyRepublic Mobile advertised offers and port-in exclusions",
          "publisher": "MyRepublic",
          "source_clock": {
            "published_at_utc": null,
            "normalized_utc": null,
            "original": null,
            "precision": "undated current webpage snapshot",
            "time_note": "Retrieval is not the start date of the offer restriction."
          },
          "observed_at_utc": "2026-10-09T05:05:25Z",
          "observation_precision": "Execution clock immediately after completed web-reader retrieval; substantive 650GB and 500GB offer blocks read.",
          "origin_cluster": "MYREPUBLIC_ADVERTISED_OFFERS_SNAPSHOT_20261009",
          "review_method": "Original HTML offer blocks and exclusions read; repeated responsive-layout blocks deduplicated.",
          "limits": "No checkout or customer-specific eligibility test; no universal number-portability conclusion. Inconsistent price text elsewhere on page is excluded."
        }
      ],
      "source_links": [
        "https://www.starhub.com/about-us/newsroom/2026/October/starhub-to-acquire-myrepublic-mobile-business-expanding-choice-and-strengthening-connectivity.html",
        "https://www.marketscreener.com/news/starhub-to-acquire-myrepublic-mobile-business-expanding-choice-and-strengthening-connectivity-ce785dded089f620",
        "https://ir.starhub.com/news.html/id/2629618",
        "https://corporate.starhub.com/about-us/newsroom/2026/August/starhub-moves-all-myrepublic-mobile-subscribers-onto-its-network.html",
        "https://myrepublic.net/sg/blog/mobile/a-new-chapter-for-myrepublicmobile/",
        "https://myrepublic.net/sg/mobile-promotions/"
      ],
      "supplied_intelligence_layers": {
        "evidenceClusters": "We screened OTR Database Data, then compared the October acquisition statement, August network agreement and current customer pages. These sources answer different questions: business ownership, network hosting and offer access. StarHub and MyRepublic are the parties to the same transaction; their statements are not independent evidence of customer benefit. The unedited press-release mirror is the same issuer source. [Filing notice](https://ir.starhub.com/news.html/id/2629618)",
        "behaviouralMemory": "Market-price behaviour is not the test here. The useful history is the order of the public announcements: network cooperation came before the planned ownership change. We would compare future evidence for the same customer group and service stage. We have no measured before-and-after series of bills, failed transfers or customer retention.",
        "contradictionEngine": "Other offers or sign-up routes may have different conditions. Separate brands can still offer useful differences in support, allowances or service. We have not tested a checkout, ported a number or measured customer outcomes. The planned purchase may proceed without changing these offers, and the offers may change without the purchase completing. MyRepublic’s 8 October customer message says customers can continue using the service as before. That is relevant reassurance from the provider, but it does not establish permanent future terms. [Customer message](https://myrepublic.net/sg/blog/mobile/a-new-chapter-for-myrepublicmobile/)",
        "signalReversalTracker": "No investment direction changes. Our new connection is between a retained brand, an existing host-network relationship and a specific offer condition. The purchase remains planned. We do not describe the older migration agreement or the undated offer restriction as newly created by this announcement.",
        "socialRealityCheck": "We did not collect a representative customer survey or a current discussion sample. Provider marketing does not measure satisfaction, migration failures or support quality. To test the consumer effect, we would need documented acceptance or rejection for the exact offer and source network, with personal information removed.",
        "predictionCalibration": "We found no earlier StarHub or MyRepublic signal in the 375 public card records screened. We have no matched set of resolved forecasts on this switching question. We therefore publish no success percentage, HIT/MISS claim or forecast of how many people will be affected."
      },
      "probability_framework": "This is a noninvestment consumer signal. Market-direction percentages do not apply. Bayesian · what changed the estimate? The ownership proposal adds a new business event. The offer page adds a concrete reason to check switching conditions. Neither tells us how often applicants are rejected. A successful checkout for an excluded source network, or revised terms, would require us to reassess the relevant claim. No numerical prior, likelihood or posterior was fitted. de Finetti · are the comparisons fair? A migrating 4G customer, an existing 5G customer and a new-number applicant are different cases. We cannot pool them into one success rate. Repeated versions of the same company announcement do not create independent trials, and an older broadband purchase is not a matched mobile-switching outcome. Kolmogorov · do the numbers agree? We keep being eligible, applying and completing a transfer as separate stages. They are not probabilities that can be added together. A statement that one offer excludes a group does not quantify that group or all switching routes. Asset prices, bullish/bearish percentages and a trading horizon are not applicable.",
      "probability_framework_details": [
        {
          "title": "Bayesian · what changed the estimate?",
          "text": "The ownership proposal adds a new business event. The offer page adds a concrete reason to check switching conditions. Neither tells us how often applicants are rejected. A successful checkout for an excluded source network, or revised terms, would require us to reassess the relevant claim. No numerical prior, likelihood or posterior was fitted."
        },
        {
          "title": "de Finetti · are the comparisons fair?",
          "text": "A migrating 4G customer, an existing 5G customer and a new-number applicant are different cases. We cannot pool them into one success rate. Repeated versions of the same company announcement do not create independent trials, and an older broadband purchase is not a matched mobile-switching outcome."
        },
        {
          "title": "Kolmogorov · do the numbers agree?",
          "text": "We keep being eligible, applying and completing a transfer as separate stages. They are not probabilities that can be added together. A statement that one offer excludes a group does not quantify that group or all switching routes. Asset prices, bullish/bearish percentages and a trading horizon are not applicable."
        }
      ],
      "probability_framework_sections": [
        {
          "title": "Bayesian · what changed the estimate?",
          "text": "The ownership proposal adds a new business event. The offer page adds a concrete reason to check switching conditions. Neither tells us how often applicants are rejected. A successful checkout for an excluded source network, or revised terms, would require us to reassess the relevant claim. No numerical prior, likelihood or posterior was fitted."
        },
        {
          "title": "de Finetti · are the comparisons fair?",
          "text": "A migrating 4G customer, an existing 5G customer and a new-number applicant are different cases. We cannot pool them into one success rate. Repeated versions of the same company announcement do not create independent trials, and an older broadband purchase is not a matched mobile-switching outcome."
        },
        {
          "title": "Kolmogorov · do the numbers agree?",
          "text": "We keep being eligible, applying and completing a transfer as separate stages. They are not probabilities that can be added together. A statement that one offer excludes a group does not quantify that group or all switching routes. Asset prices, bullish/bearish percentages and a trading horizon are not applicable."
        }
      ],
      "accordion_sections": [
        {
          "title": "How likely is this call? · Three frameworks",
          "text": "This is a noninvestment consumer signal. Market-direction percentages do not apply. Bayesian · what changed the estimate? The ownership proposal adds a new business event. The offer page adds a concrete reason to check switching conditions. Neither tells us how often applicants are rejected. A successful checkout for an excluded source network, or revised terms, would require us to reassess the relevant claim. No numerical prior, likelihood or posterior was fitted. de Finetti · are the comparisons fair? A migrating 4G customer, an existing 5G customer and a new-number applicant are different cases. We cannot pool them into one success rate. Repeated versions of the same company announcement do not create independent trials, and an older broadband purchase is not a matched mobile-switching outcome. Kolmogorov · do the numbers agree? We keep being eligible, applying and completing a transfer as separate stages. They are not probabilities that can be added together. A statement that one offer excludes a group does not quantify that group or all switching routes. Asset prices, bullish/bearish percentages and a trading horizon are not applicable.",
          "nested_sections": [
            {
              "title": "Bayesian · what changed the estimate?",
              "text": "The ownership proposal adds a new business event. The offer page adds a concrete reason to check switching conditions. Neither tells us how often applicants are rejected. A successful checkout for an excluded source network, or revised terms, would require us to reassess the relevant claim. No numerical prior, likelihood or posterior was fitted."
            },
            {
              "title": "de Finetti · are the comparisons fair?",
              "text": "A migrating 4G customer, an existing 5G customer and a new-number applicant are different cases. We cannot pool them into one success rate. Repeated versions of the same company announcement do not create independent trials, and an older broadband purchase is not a matched mobile-switching outcome."
            },
            {
              "title": "Kolmogorov · do the numbers agree?",
              "text": "We keep being eligible, applying and completing a transfer as separate stages. They are not probabilities that can be added together. A statement that one offer excludes a group does not quantify that group or all switching routes. Asset prices, bullish/bearish percentages and a trading horizon are not applicable."
            }
          ]
        },
        {
          "title": "Evidence behind this view",
          "text": "We screened OTR Database Data, then compared the October acquisition statement, August network agreement and current customer pages. These sources answer different questions: business ownership, network hosting and offer access. StarHub and MyRepublic are the parties to the same transaction; their statements are not independent evidence of customer benefit. The unedited press-release mirror is the same issuer source. [Filing notice](https://ir.starhub.com/news.html/id/2629618)"
        },
        {
          "title": "What past price moves show",
          "text": "Market-price behaviour is not the test here. The useful history is the order of the public announcements: network cooperation came before the planned ownership change. We would compare future evidence for the same customer group and service stage. We have no measured before-and-after series of bills, failed transfers or customer retention."
        },
        {
          "title": "Evidence against this view",
          "text": "Other offers or sign-up routes may have different conditions. Separate brands can still offer useful differences in support, allowances or service. We have not tested a checkout, ported a number or measured customer outcomes. The planned purchase may proceed without changing these offers, and the offers may change without the purchase completing. MyRepublic’s 8 October customer message says customers can continue using the service as before. That is relevant reassurance from the provider, but it does not establish permanent future terms. [Customer message](https://myrepublic.net/sg/blog/mobile/a-new-chapter-for-myrepublicmobile/)"
        },
        {
          "title": "Why the direction changed",
          "text": "No investment direction changes. Our new connection is between a retained brand, an existing host-network relationship and a specific offer condition. The purchase remains planned. We do not describe the older migration agreement or the undated offer restriction as newly created by this announcement."
        },
        {
          "title": "What people say vs the facts",
          "text": "We did not collect a representative customer survey or a current discussion sample. Provider marketing does not measure satisfaction, migration failures or support quality. To test the consumer effect, we would need documented acceptance or rejection for the exact offer and source network, with personal information removed."
        },
        {
          "title": "How past forecasts performed",
          "text": "We found no earlier StarHub or MyRepublic signal in the 375 public card records screened. We have no matched set of resolved forecasts on this switching question. We therefore publish no success percentage, HIT/MISS claim or forecast of how many people will be affected."
        }
      ],
      "expanded_sections": [
        {
          "title": "What’s changing?",
          "text": "StarHub’s 8 October statement says it plans to buy MyRepublic’s Singapore mobile business, subject to conditions being met. It says the brand and existing services will continue. These are company commitments, not a completed acquisition or independently tested service results. [Issuer statement](https://www.marketscreener.com/news/starhub-to-acquire-myrepublic-mobile-business-expanding-choice-and-strengthening-connectivity-ce785dded089f620)\n\nThe network move started as a separate agreement. On 6 August, the companies announced plans to move MyRepublic’s 4G customers onto StarHub’s network, alongside their earlier 5G wholesale relationship. The October statement still describes migration as progressive. [Earlier network agreement](https://corporate.starhub.com/about-us/newsroom/2026/August/starhub-moves-all-myrepublic-mobile-subscribers-onto-its-network.html)\n\nA separate customer-facing page makes that connection useful. At our 9 October check, MyRepublic’s 650GB and 500GB offers displayed a port-in exclusion for StarHub and its mobile virtual network operators, or MVNOs. We treat this as the condition shown for those offers, not a general ban on moving a phone number. [Advertised offer conditions](https://myrepublic.net/sg/mobile-promotions/)\n\nOur inference is that a brand comparison alone can miss an important switching condition. Ownership, the host network and qualification for an offer need separate checks. The page gives no start date for the exclusion, so we do not attribute it to the proposed purchase."
        },
        {
          "title": "Key points",
          "items": [
            "We would confirm which network hosts the current line and ask whether the exact advertised offer accepts it.",
            "We would compare the full ongoing plan and its conditions after confirming eligibility.",
            "We keep existing-customer continuity, a new-customer offer and completion of the business purchase as different questions."
          ]
        },
        {
          "title": "What could change this view?",
          "text": "Other offers or sign-up routes may have different conditions. Separate brands can still offer useful differences in support, allowances or service. We have not tested a checkout, ported a number or measured customer outcomes. The planned purchase may proceed without changing these offers, and the offers may change without the purchase completing."
        },
        {
          "title": "Bottom line",
          "text": "We would check the actual switching conditions before choosing a new mobile brand. This is a consumer comparison signal, with no claim that the deal raises prices, improves coverage or proves that every migration has finished."
        }
      ],
      "supplied_reference_quote": {
        "display": "Not applicable",
        "price": null,
        "currency": "Not applicable",
        "venue": "Not applicable",
        "instrument": "Not applicable",
        "session": "Not applicable",
        "as_of_utc": null,
        "as_of_display": "Not applicable: no market-price call",
        "verification_status": "NOT_APPLICABLE",
        "observation_time_verified": false,
        "change_24h_percent": null
      },
      "current_price_display": "Not applicable",
      "change_24h_display": "",
      "blank_change_24h": true,
      "prediction_activation": false,
      "scoring_eligible": false,
      "entry_status": "NOT_APPLICABLE",
      "report_authored_at_utc": "2026-10-09T05:07:26.762772Z",
      "forecast_prepared_at_utc": "2026-10-09T05:07:26.762772Z",
      "native_publication_time_utc": null,
      "publication_timestamp": null,
      "clock_label": "Research prepared",
      "clock_note": "Actual publication must be added by the publisher after verified deployment. Research retrieval does not refresh a source date.",
      "fact_review_state": "CLAIMS_REVIEWED_WITH_DISCLOSED_LIMITS",
      "review_status": "PEER_REVIEW_PASSED",
      "review": {
        "facts_and_prices_fully_verified": false,
        "status": "PASS_WITH_DISCLOSED_LIMITS",
        "reviewed_at_utc": "2026-10-09T05:12:46.119117Z",
        "reviewers": [
          "General research peer",
          "Technology research peer",
          "Cross-desk evidence reviewer",
          "Edition coordinator"
        ],
        "scope": "Full public prose reviewed by two independent desk peers and coordinator; key offer terms independently reopened. No checkout or empirical outcome verification.",
        "price_review": "Not applicable; noninvestment card, no prices or trading call."
      },
      "source_batch": "otr-force-20261009-0454",
      "card_scope": "noninvestment_research",
      "research_cutoff_utc": "2026-10-09T05:24:20Z",
      "public_expanded_text": "MyRepublic’s planned sale adds a check before switching mobile brands\n\nWe connect StarHub’s planned purchase of MyRepublic Mobile with the earlier network migration and the offers customers can actually use. The MyRepublic brand is set to remain, while selected advertised port-in offers exclude StarHub and its virtual-network customers. Our practical signal is to check the network behind the current line and the exact offer rules before assuming a change of brand qualifies for a switching deal.\n\nWhat’s changing?\nStarHub’s 8 October statement says it plans to buy MyRepublic’s Singapore mobile business, subject to conditions being met. It says the brand and existing services will continue. These are company commitments, not a completed acquisition or independently tested service results. [Issuer statement](https://www.marketscreener.com/news/starhub-to-acquire-myrepublic-mobile-business-expanding-choice-and-strengthening-connectivity-ce785dded089f620)\n\nThe network move started as a separate agreement. On 6 August, the companies announced plans to move MyRepublic’s 4G customers onto StarHub’s network, alongside their earlier 5G wholesale relationship. The October statement still describes migration as progressive. [Earlier network agreement](https://corporate.starhub.com/about-us/newsroom/2026/August/starhub-moves-all-myrepublic-mobile-subscribers-onto-its-network.html)\n\nA separate customer-facing page makes that connection useful. At our 9 October check, MyRepublic’s 650GB and 500GB offers displayed a port-in exclusion for StarHub and its mobile virtual network operators, or MVNOs. We treat this as the condition shown for those offers, not a general ban on moving a phone number. [Advertised offer conditions](https://myrepublic.net/sg/mobile-promotions/)\n\nOur inference is that a brand comparison alone can miss an important switching condition. Ownership, the host network and qualification for an offer need separate checks. The page gives no start date for the exclusion, so we do not attribute it to the proposed purchase.\n\nKey points\nWe would confirm which network hosts the current line and ask whether the exact advertised offer accepts it.\nWe would compare the full ongoing plan and its conditions after confirming eligibility.\nWe keep existing-customer continuity, a new-customer offer and completion of the business purchase as different questions.\n\nWhat could change this view?\nOther offers or sign-up routes may have different conditions. Separate brands can still offer useful differences in support, allowances or service. We have not tested a checkout, ported a number or measured customer outcomes. The planned purchase may proceed without changing these offers, and the offers may change without the purchase completing.\n\nBottom line\nWe would check the actual switching conditions before choosing a new mobile brand. This is a consumer comparison signal, with no claim that the deal raises prices, improves coverage or proves that every migration has finished.\n\nHow likely is this call? · Three frameworks\nThis is a noninvestment consumer signal. Market-direction percentages do not apply. Bayesian · what changed the estimate? The ownership proposal adds a new business event. The offer page adds a concrete reason to check switching conditions. Neither tells us how often applicants are rejected. A successful checkout for an excluded source network, or revised terms, would require us to reassess the relevant claim. No numerical prior, likelihood or posterior was fitted. de Finetti · are the comparisons fair? A migrating 4G customer, an existing 5G customer and a new-number applicant are different cases. We cannot pool them into one success rate. Repeated versions of the same company announcement do not create independent trials, and an older broadband purchase is not a matched mobile-switching outcome. Kolmogorov · do the numbers agree? We keep being eligible, applying and completing a transfer as separate stages. They are not probabilities that can be added together. A statement that one offer excludes a group does not quantify that group or all switching routes. Asset prices, bullish/bearish percentages and a trading horizon are not applicable.\n\nEvidence behind this view\nWe screened OTR Database Data, then compared the October acquisition statement, August network agreement and current customer pages. These sources answer different questions: business ownership, network hosting and offer access. StarHub and MyRepublic are the parties to the same transaction; their statements are not independent evidence of customer benefit. The unedited press-release mirror is the same issuer source. [Filing notice](https://ir.starhub.com/news.html/id/2629618)\n\nWhat past price moves show\nMarket-price behaviour is not the test here. The useful history is the order of the public announcements: network cooperation came before the planned ownership change. We would compare future evidence for the same customer group and service stage. We have no measured before-and-after series of bills, failed transfers or customer retention.\n\nEvidence against this view\nOther offers or sign-up routes may have different conditions. Separate brands can still offer useful differences in support, allowances or service. We have not tested a checkout, ported a number or measured customer outcomes. The planned purchase may proceed without changing these offers, and the offers may change without the purchase completing. MyRepublic’s 8 October customer message says customers can continue using the service as before. That is relevant reassurance from the provider, but it does not establish permanent future terms. [Customer message](https://myrepublic.net/sg/blog/mobile/a-new-chapter-for-myrepublicmobile/)\n\nWhy the direction changed\nNo investment direction changes. Our new connection is between a retained brand, an existing host-network relationship and a specific offer condition. The purchase remains planned. We do not describe the older migration agreement or the undated offer restriction as newly created by this announcement.\n\nWhat people say vs the facts\nWe did not collect a representative customer survey or a current discussion sample. Provider marketing does not measure satisfaction, migration failures or support quality. To test the consumer effect, we would need documented acceptance or rejection for the exact offer and source network, with personal information removed.\n\nHow past forecasts performed\nWe found no earlier StarHub or MyRepublic signal in the 375 public card records screened. We have no matched set of resolved forecasts on this switching question. We therefore publish no success percentage, HIT/MISS claim or forecast of how many people will be affected.",
      "novelty_review": {
        "corpus_cards_screened": 375,
        "release_files_screened": 32,
        "entity_matches": {
          "StarHub": 0,
          "MyRepublic": 0
        },
        "same_source_url_matches": 0,
        "method": "All indexed card titles, summaries, thesis/mechanism and source records computationally compared, then relevant earlier cards read.",
        "scope_limit": "Does not prove universal novelty across every OTR artifact, private archive, non-Signals page or the public internet. No claim every source or card was manually read.",
        "distinct_connection": "Planned retail-business ownership plus earlier host-network migration plus offer-specific source-network exclusion."
      },
      "source_review": {
        "status": "PASS_WITH_DISCLOSED_LIMITS",
        "source_independence": "Issuer statement, mirror, IR wrapper and seller reassurance are related transaction communications; repeated offer blocks deduplicated.",
        "freshness": "New dated acquisition event with verified in-window redistribution; earliest original publication hour unverified. Offer restriction is an undated current snapshot.",
        "unread_material": "Attached transaction PDF terms excluded after denied authorized retry."
      },
      "release_id": "OTR-SIGNALS-20261009-052420Z-FORCE-1"
    },
    {
      "schema": "OTR-SIGNALS-CATEGORY-CARD-1",
      "primary_category": "technology",
      "categories": [
        "technology"
      ],
      "id": "TECH-20261009-CONNECTION-BALANCE-HEALTH-CHECK",
      "title": "AI front-end gains need a separate health-check test",
      "summary": "We see a new release-test risk in a freshly merged vLLM change. Spreading incoming connections more evenly puts idle API workers to work, but the author also reports slower health checks in a separate mixed-load test. We would check useful work and health responses together. A separate Codex change shows why routing new work and keeping an existing session on its host need different rules.",
      "signal_claim": "We see a new release-test risk in a freshly merged vLLM change. Spreading incoming connections more evenly puts idle API workers to work, but the author also reports slower health checks in a separate mixed-load test. We would check useful work and health responses together. A separate Codex change shows why routing new work and keeping an existing session on its host need different rules.",
      "thesis": "We see a new release-test risk in a freshly merged vLLM change. Spreading incoming connections more evenly puts idle API workers to work, but the author also reports slower health checks in a separate mixed-load test. We would check useful work and health responses together. A separate Codex change shows why routing new work and keeping an existing session on its host need different rules.",
      "publication_status": "READY",
      "status": "REVIEWED_EDITORIAL_CARD",
      "key_points": [
        "We would record each API worker’s connection count and completed requests separately. A long-lived connection stays on one worker; equal socket counts do not ensure equal CPU time, response size or GPU demand.",
        "In the author’s CPU stub test, eight workers receive 500 arrivals over five seconds with 50-millisecond response rendering and 100 health probes per second. The reported 99th-percentile /health response time (p99) rises to about 50–100 milliseconds, versus under one millisecond on the baseline. This is a specific synthetic test, not a measured production outage.",
        "We read the vLLM regression cases for keep-alive traffic, failed TLS handshakes, a less-busy peer that never accepts, and shutdown. The four-worker distribution test uses 400 connections and is skipped on machines with fewer than eight CPU cores. We did not run it.",
        "We read the Codex test that routes parent and child sessions to different hosts on one shared provider. It checks ordinary unavailability, explicit route loss and preservation of the unaffected session. It does not prove transparent session migration or safe replay of every failed operation."
      ],
      "bottom_line": "We would accept a front-end throughput improvement only after checking connection distribution, completed responses and health-check latency together on the intended traffic mix. For stateful agents, also test which host owns each session and what happens after an ordinary error versus confirmed route loss. Confirm the containing software build before testing. These are bounded acceptance checks, not a reason to change production settings from a benchmark headline.",
      "analysis": {
        "mechanism": "vLLM’s development source now tries to share new connections among API workers according to each worker’s open and still-connecting sockets. Previously, the first worker to wake could accept most of a burst. The new code lets busier workers briefly defer to less busy peers, then accepts anyway after five one-millisecond checks so a blocked peer does not stop progress. This is best-effort connection balancing, not a promise of equal request cost or GPU work. [Merged source](https://github.com/vllm-project/vllm/commit/fa312090cb1d972aa96f6b0ea174b7a32b4b0548)\n\nThe author’s separate tests reveal the useful trade-off. Short-request model-serving tests report higher throughput. A CPU-only mixed test reports slower /health responses when every worker is doing useful rendering work, instead of leaving idle workers available for probes. We infer that a throughput upgrade needs a health-response test under the same planned traffic. The source does not show a failed production probe or a restart. [Workloads and limits](https://github.com/vllm-project/vllm/pull/60723)\n\nA separate Codex change supplies a boundary for routing, not a second measurement of that speed gain. Several code-execution sessions may share a network connection while their state lives on different hosts. Codex now retains a route token for each session and sends it on later calls. A normal unavailable response preserves the session; an explicit route-lost response can retire it. A failed execution is not automatically replayed. We would therefore test new connection distribution separately from the continuity of work already in progress. [Session-routing source](https://github.com/openai/codex/commit/5b3c1522f85316063e43b97fa7e13751d55bccdb)\n\nThe vLLM change merged at 04:40:13 UTC on 9 October. We found it in current main, but the inspected v0.31.0 release, published on 5 October, still has the earlier launcher. This is a development-source signal. We have not verified a containing stable package, nightly build or production rollout.",
        "impact": "We would accept a front-end throughput improvement only after checking connection distribution, completed responses and health-check latency together on the intended traffic mix. For stateful agents, also test which host owns each session and what happens after an ordinary error versus confirmed route loss. Confirm the containing software build before testing. These are bounded acceptance checks, not a reason to change production settings from a benchmark headline.",
        "key_points": [
          "We would record each API worker’s connection count and completed requests separately. A long-lived connection stays on one worker; equal socket counts do not ensure equal CPU time, response size or GPU demand.",
          "In the author’s CPU stub test, eight workers receive 500 arrivals over five seconds with 50-millisecond response rendering and 100 health probes per second. The reported 99th-percentile /health response time (p99) rises to about 50–100 milliseconds, versus under one millisecond on the baseline. This is a specific synthetic test, not a measured production outage.",
          "We read the vLLM regression cases for keep-alive traffic, failed TLS handshakes, a less-busy peer that never accepts, and shutdown. The four-worker distribution test uses 400 connections and is skipped on machines with fewer than eight CPU cores. We did not run it.",
          "We read the Codex test that routes parent and child sessions to different hosts on one shared provider. It checks ordinary unavailability, explicit route loss and preservation of the unaffected session. It does not prove transparent session migration or safe replay of every failed operation."
        ],
        "countercase": "We would narrow the throughput case for a single API worker, a GPU-bound workload, gradually opened client connections or an upstream balancer that already spreads its pool. The vLLM author explicitly expects a smaller gain in some of those connection patterns. A health-response delay is not itself a health-check failure: Kubernetes defaults to a one-second probe timeout, and the actual timeout, failure threshold and observed outcomes must be checked. The reported 50–100-millisecond p99 alone does not establish a timeout. [Probe specification](https://kubernetes.io/docs/reference/kubernetes-api/core/pod-v1/#Probe)\n\nThe two projects address different layers. Codex’s session routing does not corroborate vLLM’s benchmark result. We have no independent reproduction, production incident rate or broad adoption count. If a representative mixed workload shows no meaningful probe delay and no connection skew, this particular operational priority becomes weaker.",
        "uncertainties": [
          "We would narrow the throughput case for a single API worker, a GPU-bound workload, gradually opened client connections or an upstream balancer that already spreads its pool. The vLLM author explicitly expects a smaller gain in some of those connection patterns. A health-response delay is not itself a health-check failure: Kubernetes defaults to a one-second probe timeout, and the actual timeout, failure threshold and observed outcomes must be checked. The reported 50–100-millisecond p99 alone does not establish a timeout. [Probe specification](https://kubernetes.io/docs/reference/kubernetes-api/core/pod-v1/#Probe)\n\nThe two projects address different layers. Codex’s session routing does not corroborate vLLM’s benchmark result. We have no independent reproduction, production incident rate or broad adoption count. If a representative mixed workload shows no meaningful probe delay and no connection skew, this particular operational priority becomes weaker.",
          "We read source code, test definitions and author-reported measurements. We did not execute either project, reproduce benchmarks, inspect a production deployment or verify a containing stable release. The latest vLLM stable tag inspected was v0.31.0 and its launcher lacked the new acceptance loop. Current-main inspection was bounded to launcher lines 30–150. The health-check test and the GPU-serving tests use different workloads and cannot be pooled."
        ],
        "named_assets": [],
        "directional_takeaway": "Not applicable: no investment call",
        "next_check": "Confirm the containing release, then compare connection distribution, health-check responses and session continuity under the intended workload. No timed market expiry."
      },
      "named_assets": [],
      "directional_takeaway": "N/A",
      "direction_display": "N/A",
      "uncertainty": "We would narrow the throughput case for a single API worker, a GPU-bound workload, gradually opened client connections or an upstream balancer that already spreads its pool. The vLLM author explicitly expects a smaller gain in some of those connection patterns. A health-response delay is not itself a health-check failure: Kubernetes defaults to a one-second probe timeout, and the actual timeout, failure threshold and observed outcomes must be checked. The reported 50–100-millisecond p99 alone does not establish a timeout. [Probe specification](https://kubernetes.io/docs/reference/kubernetes-api/core/pod-v1/#Probe)\n\nThe two projects address different layers. Codex’s session routing does not corroborate vLLM’s benchmark result. We have no independent reproduction, production incident rate or broad adoption count. If a representative mixed workload shows no meaningful probe delay and no connection skew, this particular operational priority becomes weaker.",
      "next_check": "Confirm the containing release, then compare connection distribution, health-check responses and session continuity under the intended workload. No timed market expiry.",
      "check_time_utc": null,
      "check_time_label": "Next useful check",
      "next_check_reason": "Implementation and measurement check, not a frozen market deadline.",
      "source_confidence": {
        "verified": true,
        "label": "Source verified; benchmark effects remain author reports",
        "reason": "We read source code, test definitions and author-reported measurements. We did not execute either project, reproduce benchmarks, inspect a production deployment or verify a containing stable release. The latest vLLM stable tag inspected was v0.31.0 and its launcher lacked the new acceptance loop. Current-main inspection was bounded to launcher lines 30–150. The health-check test and the GPU-serving tests use different workloads and cannot be pooled."
      },
      "source_labels": [
        "OTR Database Data"
      ],
      "sources": [
        {
          "source_id": "VLLM-BALANCED-ACCEPT:COMMIT",
          "url": "https://github.com/vllm-project/vllm/commit/fa312090cb1d972aa96f6b0ea174b7a32b4b0548",
          "title": "Connection-count-based API worker acceptance",
          "publisher": "vllm-project/vllm",
          "source_clock": {
            "published_at_utc": "2026-10-09T04:40:13Z",
            "normalized_utc": "2026-10-09T04:40:13Z",
            "event_at_utc": "2026-10-09T04:40:13Z",
            "publication_basis": "Merge/commit clock; proposal first opened 2026-10-08T22:00:57Z. Benchmark measurement time was not provided.",
            "precision": "second",
            "timezone": "UTC"
          },
          "retrieved_at_utc": "2026-10-09T05:01:08.545Z",
          "evidence_role": "Fresh merged implementation",
          "review_method": "All four changed-file patches read, including the new test file. Main launcher and stable-tag launcher compared. No execution.",
          "origin_cluster": "vllm-project/vllm"
        },
        {
          "source_id": "VLLM-BALANCED-ACCEPT:PR",
          "url": "https://github.com/vllm-project/vllm/pull/60723",
          "title": "Benchmark workloads, trade-offs and review",
          "publisher": "vllm-project/vllm",
          "source_clock": {
            "published_at_utc": "2026-10-08T22:00:57Z",
            "normalized_utc": "2026-10-08T22:00:57Z",
            "event_at_utc": "2026-10-09T04:40:13Z",
            "updated_at_utc": "2026-10-09T04:40:14Z",
            "precision": "second",
            "publication_basis": "Proposal creation and merge are separate clocks; benchmark-run timestamps unknown."
          },
          "retrieved_at_utc": "2026-10-09T05:01:08.545Z",
          "evidence_role": "Author measurements and opposing evidence",
          "review_method": "Full PR body and all returned review comments read. Performance values remain author reports.",
          "origin_cluster": "vllm-project/vllm"
        },
        {
          "source_id": "CODEX-SESSION-ROUTE:COMMIT",
          "url": "https://github.com/openai/codex/commit/5b3c1522f85316063e43b97fa7e13751d55bccdb",
          "title": "Per-session routes on a shared transport",
          "publisher": "openai/codex",
          "source_clock": {
            "published_at_utc": "2026-10-09T02:51:03Z",
            "normalized_utc": "2026-10-09T02:51:03Z",
            "event_at_utc": "2026-10-09T02:51:14Z",
            "commit_author_at_utc": "2026-10-09T02:41:55Z",
            "commit_committer_at_utc": "2026-10-09T02:50:59Z",
            "publication_basis": "Public pull request created at 02:51:03Z and merged at 02:51:14Z; commit clocks kept separately.",
            "precision": "second",
            "timezone": "UTC"
          },
          "retrieved_at_utc": "2026-10-09T05:01:12.837Z",
          "evidence_role": "Fresh separate design contrast",
          "review_method": "Commit metadata, session routing implementation, deadline logic and admission/recovery tests read; no code execution.",
          "origin_cluster": "openai/codex"
        },
        {
          "source_id": "VLLM-RELEASE:V0310",
          "url": "https://github.com/vllm-project/vllm/releases/tag/v0.31.0",
          "title": "Latest stable release metadata at inspection",
          "publisher": "vllm-project/vllm",
          "source_clock": {
            "published_at_utc": "2026-10-05T06:44:55Z",
            "normalized_utc": "2026-10-05T06:44:55Z",
            "precision": "second",
            "publication_basis": "Release publication; older availability context."
          },
          "retrieved_at_utc": "2026-10-09T05:00:13Z",
          "evidence_role": "Availability limit",
          "review_method": "Latest-release metadata and tagged launcher lines 1–140 read.",
          "origin_cluster": "vllm-project/vllm",
          "retrieval_clock_precision": "Approximate tool completion second, recorded from run reminders."
        },
        {
          "source_id": "VLLM-MAIN:LAUNCHER",
          "url": "https://github.com/vllm-project/vllm/blob/main/vllm/entrypoints/launchers/launcher.py",
          "title": "Current development launcher",
          "publisher": "vllm-project/vllm",
          "source_clock": {
            "published_at_utc": null,
            "normalized_utc": null,
            "precision": "unknown",
            "publication_basis": "Mutable main-source read; not an independently timestamped new publication."
          },
          "retrieved_at_utc": "2026-10-09T05:00:28Z",
          "evidence_role": "Main-source inclusion",
          "review_method": "Lines 30–150 read; includes peer_loads and bounded acceptance loop.",
          "origin_cluster": "vllm-project/vllm",
          "retrieval_clock_precision": "Approximate tool completion second, recorded from run reminders."
        },
        {
          "source_id": "KUBERNETES-PROBE-CONTRACT",
          "url": "https://kubernetes.io/docs/reference/kubernetes-api/core/pod-v1/#Probe",
          "title": "Probe timeout and failure-threshold fields",
          "publisher": "Kubernetes",
          "source_clock": {
            "published_at_utc": null,
            "normalized_utc": null,
            "precision": "unknown",
            "publication_basis": "Undated background specification; not fresh event evidence."
          },
          "retrieved_at_utc": "2026-10-09T05:07:33.412Z",
          "evidence_role": "Counterevidence and definitions",
          "review_method": "Probe fields read: default timeout one second, default consecutive failure threshold three. No deployment configuration read.",
          "origin_cluster": "kubernetes.io"
        }
      ],
      "source_links": [
        "https://github.com/vllm-project/vllm/commit/fa312090cb1d972aa96f6b0ea174b7a32b4b0548",
        "https://github.com/vllm-project/vllm/pull/60723",
        "https://github.com/openai/codex/commit/5b3c1522f85316063e43b97fa7e13751d55bccdb",
        "https://github.com/vllm-project/vllm/releases/tag/v0.31.0",
        "https://github.com/vllm-project/vllm/blob/main/vllm/entrypoints/launchers/launcher.py",
        "https://kubernetes.io/docs/reference/kubernetes-api/core/pod-v1/#Probe"
      ],
      "supplied_intelligence_layers": {
        "evidenceClusters": "We started with OTR Database Data, reading a recent Technology findings file and a newer research brief, then reopened the original project evidence. The earlier findings identified Codex session routing; the new vLLM merge supplies the fresh connection-balancing and probe-latency question. vLLM’s commit, pull request, review comments and benchmarks are one project-origin cluster. Codex is a separate design contrast, not independent replication. Kubernetes documentation supplies the probe contract only. The research brief supplies context, not another test result. [vLLM evidence](https://github.com/vllm-project/vllm/pull/60723) [Codex evidence](https://github.com/openai/codex/pull/52381)",
        "behaviouralMemory": "This is operational history, not price history. Earlier OTR cards examined stalled workers, multimodal packing, test-process reuse and restart-state completeness. This card asks whether spreading connections removes idle capacity that had kept health checks quick, while existing stateful sessions still need their own host identity. The vLLM proposal opened on 8 October at 22:00:57 UTC, received a request for ordinary short-request tests, and merged on 9 October at 04:40:13 UTC. The fresh event is the merge, not first disclosure of every benchmark.",
        "contradictionEngine": "We would narrow the throughput case for a single API worker, a GPU-bound workload, gradually opened client connections or an upstream balancer that already spreads its pool. The vLLM author explicitly expects a smaller gain in some of those connection patterns. A health-response delay is not itself a health-check failure: Kubernetes defaults to a one-second probe timeout, and the actual timeout, failure threshold and observed outcomes must be checked. The reported 50–100-millisecond p99 alone does not establish a timeout. [Probe specification](https://kubernetes.io/docs/reference/kubernetes-api/core/pod-v1/#Probe)\n\nThe two projects address different layers. Codex’s session routing does not corroborate vLLM’s benchmark result. We have no independent reproduction, production incident rate or broad adoption count. If a representative mixed workload shows no meaningful probe delay and no connection skew, this particular operational priority becomes weaker.",
        "signalReversalTracker": "No investment direction or locked forecast is changed. We move from a simple “more evenly used workers” benefit to a two-sided operational view: better use of workers can coexist with slower control responses. The source’s bounded wait also means balance is a preference, not a hard rule. We retain the earlier memory-allocation and worker-stall cards unchanged; neither establishes this connection/probe trade-off.",
        "socialRealityCheck": "We inspected one vLLM developer review. A reviewer asked for ordinary short-request serving results instead of relying only on an abort test. The author then reported those results and cautioned that gradual connections or a load balancer’s own pool could reduce the gain. Startup and shutdown concerns raised in review are addressed in the merged patch we read. This is a bounded technical exchange, not a survey of users or proof of market adoption. [Author’s bounded comparison](https://github.com/vllm-project/vllm/pull/60723#issuecomment-6071969036)",
        "predictionCalibration": "We found no matched resolved OTR forecast on this connection-balancing and probe-response outcome. The author’s repeated benchmark runs measure software in specified settings; they are not resolved OTR predictions. Different request sizes, concurrency levels and probe patterns are not exchangeable trials of one success rate. We assign no probability of a production speed gain, timeout or restart."
      },
      "probability_framework": "This is a noninvestment Technology signal. Bayesian · what changed the estimate? The merged implementation makes connection-skew reduction more concrete than a proposal. The author’s health-response trade-off reduces support for the broader claim that every request becomes faster. We would update this qualitative view with a before-and-after test using the intended client pool and probe settings. No fitted prior, likelihood ratio or calibrated numerical posterior is available. de Finetti · are the comparisons fair? The CPU health-probe test, short-output GPU-serving tests and Codex session-routing tests answer different questions. They cannot be pooled as repeated examples of one outcome. Even within vLLM, burst-opened keep-alive pools and gradual connections may behave differently. The commit and its pull request are the same origin, not two independent confirmations. Kolmogorov · do the numbers agree? Connections, requests per second, response-tail latency and session failures have different denominators. Equal connection shares do not imply equal work, and a slower p99 does not state how many configured health checks failed. We keep those measurements separate. No market outcome partition, reference price, investment horizon or bullish/bearish/neutral percentage applies. Read the shared method: https://new.ontherice.org/how-otr-works/#probability-framework",
      "probability_framework_sections": [
        {
          "title": "Bayesian · what changed the estimate?",
          "text": "The merged implementation makes connection-skew reduction more concrete than a proposal. The author’s health-response trade-off reduces support for the broader claim that every request becomes faster. We would update this qualitative view with a before-and-after test using the intended client pool and probe settings. No fitted prior, likelihood ratio or calibrated numerical posterior is available."
        },
        {
          "title": "de Finetti · are the comparisons fair?",
          "text": "The CPU health-probe test, short-output GPU-serving tests and Codex session-routing tests answer different questions. They cannot be pooled as repeated examples of one outcome. Even within vLLM, burst-opened keep-alive pools and gradual connections may behave differently. The commit and its pull request are the same origin, not two independent confirmations."
        },
        {
          "title": "Kolmogorov · do the numbers agree?",
          "text": "Connections, requests per second, response-tail latency and session failures have different denominators. Equal connection shares do not imply equal work, and a slower p99 does not state how many configured health checks failed. We keep those measurements separate. No market outcome partition, reference price, investment horizon or bullish/bearish/neutral percentage applies."
        }
      ],
      "probability_framework_details": [
        {
          "title": "Bayesian · what changed the estimate?",
          "text": "The merged implementation makes connection-skew reduction more concrete than a proposal. The author’s health-response trade-off reduces support for the broader claim that every request becomes faster. We would update this qualitative view with a before-and-after test using the intended client pool and probe settings. No fitted prior, likelihood ratio or calibrated numerical posterior is available."
        },
        {
          "title": "de Finetti · are the comparisons fair?",
          "text": "The CPU health-probe test, short-output GPU-serving tests and Codex session-routing tests answer different questions. They cannot be pooled as repeated examples of one outcome. Even within vLLM, burst-opened keep-alive pools and gradual connections may behave differently. The commit and its pull request are the same origin, not two independent confirmations."
        },
        {
          "title": "Kolmogorov · do the numbers agree?",
          "text": "Connections, requests per second, response-tail latency and session failures have different denominators. Equal connection shares do not imply equal work, and a slower p99 does not state how many configured health checks failed. We keep those measurements separate. No market outcome partition, reference price, investment horizon or bullish/bearish/neutral percentage applies."
        }
      ],
      "accordion_sections": [
        {
          "title": "How likely is this call? · Three frameworks",
          "text": "This is a noninvestment Technology signal. Bayesian · what changed the estimate? The merged implementation makes connection-skew reduction more concrete than a proposal. The author’s health-response trade-off reduces support for the broader claim that every request becomes faster. We would update this qualitative view with a before-and-after test using the intended client pool and probe settings. No fitted prior, likelihood ratio or calibrated numerical posterior is available. de Finetti · are the comparisons fair? The CPU health-probe test, short-output GPU-serving tests and Codex session-routing tests answer different questions. They cannot be pooled as repeated examples of one outcome. Even within vLLM, burst-opened keep-alive pools and gradual connections may behave differently. The commit and its pull request are the same origin, not two independent confirmations. Kolmogorov · do the numbers agree? Connections, requests per second, response-tail latency and session failures have different denominators. Equal connection shares do not imply equal work, and a slower p99 does not state how many configured health checks failed. We keep those measurements separate. No market outcome partition, reference price, investment horizon or bullish/bearish/neutral percentage applies. Read the shared method: https://new.ontherice.org/how-otr-works/#probability-framework"
        },
        {
          "title": "Evidence behind this view",
          "text": "We started with OTR Database Data, reading a recent Technology findings file and a newer research brief, then reopened the original project evidence. The earlier findings identified Codex session routing; the new vLLM merge supplies the fresh connection-balancing and probe-latency question. vLLM’s commit, pull request, review comments and benchmarks are one project-origin cluster. Codex is a separate design contrast, not independent replication. Kubernetes documentation supplies the probe contract only. The research brief supplies context, not another test result. [vLLM evidence](https://github.com/vllm-project/vllm/pull/60723) [Codex evidence](https://github.com/openai/codex/pull/52381)"
        },
        {
          "title": "What past price moves show",
          "text": "This is operational history, not price history. Earlier OTR cards examined stalled workers, multimodal packing, test-process reuse and restart-state completeness. This card asks whether spreading connections removes idle capacity that had kept health checks quick, while existing stateful sessions still need their own host identity. The vLLM proposal opened on 8 October at 22:00:57 UTC, received a request for ordinary short-request tests, and merged on 9 October at 04:40:13 UTC. The fresh event is the merge, not first disclosure of every benchmark."
        },
        {
          "title": "Evidence against this view",
          "text": "We would narrow the throughput case for a single API worker, a GPU-bound workload, gradually opened client connections or an upstream balancer that already spreads its pool. The vLLM author explicitly expects a smaller gain in some of those connection patterns. A health-response delay is not itself a health-check failure: Kubernetes defaults to a one-second probe timeout, and the actual timeout, failure threshold and observed outcomes must be checked. The reported 50–100-millisecond p99 alone does not establish a timeout. [Probe specification](https://kubernetes.io/docs/reference/kubernetes-api/core/pod-v1/#Probe)\n\nThe two projects address different layers. Codex’s session routing does not corroborate vLLM’s benchmark result. We have no independent reproduction, production incident rate or broad adoption count. If a representative mixed workload shows no meaningful probe delay and no connection skew, this particular operational priority becomes weaker."
        },
        {
          "title": "Why the direction changed",
          "text": "No investment direction or locked forecast is changed. We move from a simple “more evenly used workers” benefit to a two-sided operational view: better use of workers can coexist with slower control responses. The source’s bounded wait also means balance is a preference, not a hard rule. We retain the earlier memory-allocation and worker-stall cards unchanged; neither establishes this connection/probe trade-off."
        },
        {
          "title": "What people say vs the facts",
          "text": "We inspected one vLLM developer review. A reviewer asked for ordinary short-request serving results instead of relying only on an abort test. The author then reported those results and cautioned that gradual connections or a load balancer’s own pool could reduce the gain. Startup and shutdown concerns raised in review are addressed in the merged patch we read. This is a bounded technical exchange, not a survey of users or proof of market adoption. [Author’s bounded comparison](https://github.com/vllm-project/vllm/pull/60723#issuecomment-6071969036)"
        },
        {
          "title": "How past forecasts performed",
          "text": "We found no matched resolved OTR forecast on this connection-balancing and probe-response outcome. The author’s repeated benchmark runs measure software in specified settings; they are not resolved OTR predictions. Different request sizes, concurrency levels and probe patterns are not exchangeable trials of one success rate. We assign no probability of a production speed gain, timeout or restart."
        }
      ],
      "expanded_sections": [
        {
          "title": "What’s changing?",
          "text": "vLLM’s development source now tries to share new connections among API workers according to each worker’s open and still-connecting sockets. Previously, the first worker to wake could accept most of a burst. The new code lets busier workers briefly defer to less busy peers, then accepts anyway after five one-millisecond checks so a blocked peer does not stop progress. This is best-effort connection balancing, not a promise of equal request cost or GPU work. [Merged source](https://github.com/vllm-project/vllm/commit/fa312090cb1d972aa96f6b0ea174b7a32b4b0548)\n\nThe author’s separate tests reveal the useful trade-off. Short-request model-serving tests report higher throughput. A CPU-only mixed test reports slower /health responses when every worker is doing useful rendering work, instead of leaving idle workers available for probes. We infer that a throughput upgrade needs a health-response test under the same planned traffic. The source does not show a failed production probe or a restart. [Workloads and limits](https://github.com/vllm-project/vllm/pull/60723)\n\nA separate Codex change supplies a boundary for routing, not a second measurement of that speed gain. Several code-execution sessions may share a network connection while their state lives on different hosts. Codex now retains a route token for each session and sends it on later calls. A normal unavailable response preserves the session; an explicit route-lost response can retire it. A failed execution is not automatically replayed. We would therefore test new connection distribution separately from the continuity of work already in progress. [Session-routing source](https://github.com/openai/codex/commit/5b3c1522f85316063e43b97fa7e13751d55bccdb)\n\nThe vLLM change merged at 04:40:13 UTC on 9 October. We found it in current main, but the inspected v0.31.0 release, published on 5 October, still has the earlier launcher. This is a development-source signal. We have not verified a containing stable package, nightly build or production rollout."
        },
        {
          "title": "Key points",
          "items": [
            "We would record each API worker’s connection count and completed requests separately. A long-lived connection stays on one worker; equal socket counts do not ensure equal CPU time, response size or GPU demand.",
            "In the author’s CPU stub test, eight workers receive 500 arrivals over five seconds with 50-millisecond response rendering and 100 health probes per second. The reported 99th-percentile /health response time (p99) rises to about 50–100 milliseconds, versus under one millisecond on the baseline. This is a specific synthetic test, not a measured production outage.",
            "We read the vLLM regression cases for keep-alive traffic, failed TLS handshakes, a less-busy peer that never accepts, and shutdown. The four-worker distribution test uses 400 connections and is skipped on machines with fewer than eight CPU cores. We did not run it.",
            "We read the Codex test that routes parent and child sessions to different hosts on one shared provider. It checks ordinary unavailability, explicit route loss and preservation of the unaffected session. It does not prove transparent session migration or safe replay of every failed operation."
          ]
        },
        {
          "title": "What could change this view?",
          "text": "We would narrow the throughput case for a single API worker, a GPU-bound workload, gradually opened client connections or an upstream balancer that already spreads its pool. The vLLM author explicitly expects a smaller gain in some of those connection patterns. A health-response delay is not itself a health-check failure: Kubernetes defaults to a one-second probe timeout, and the actual timeout, failure threshold and observed outcomes must be checked. The reported 50–100-millisecond p99 alone does not establish a timeout. [Probe specification](https://kubernetes.io/docs/reference/kubernetes-api/core/pod-v1/#Probe)\n\nThe two projects address different layers. Codex’s session routing does not corroborate vLLM’s benchmark result. We have no independent reproduction, production incident rate or broad adoption count. If a representative mixed workload shows no meaningful probe delay and no connection skew, this particular operational priority becomes weaker."
        },
        {
          "title": "Bottom line",
          "text": "We would accept a front-end throughput improvement only after checking connection distribution, completed responses and health-check latency together on the intended traffic mix. For stateful agents, also test which host owns each session and what happens after an ordinary error versus confirmed route loss. Confirm the containing software build before testing. These are bounded acceptance checks, not a reason to change production settings from a benchmark headline."
        }
      ],
      "probability_details": {
        "Bullish": "Not applicable",
        "Bearish": "Not applicable",
        "Neutral": "Not applicable",
        "neutral_band": "Not applicable: no market call",
        "method": "Qualitative source-linked analysis, without a numerical posterior",
        "horizon": "Not applicable",
        "exact_deadline": "Not applicable",
        "Price basis": "Not applicable",
        "Research gaps": "We read source code, test definitions and author-reported measurements. We did not execute either project, reproduce benchmarks, inspect a production deployment or verify a containing stable release. The latest vLLM stable tag inspected was v0.31.0 and its launcher lacked the new acceptance loop. Current-main inspection was bounded to launcher lines 30–150. The health-check test and the GPU-serving tests use different workloads and cannot be pooled.",
        "Sources": [
          "https://github.com/vllm-project/vllm/commit/fa312090cb1d972aa96f6b0ea174b7a32b4b0548",
          "https://github.com/vllm-project/vllm/pull/60723",
          "https://github.com/openai/codex/commit/5b3c1522f85316063e43b97fa7e13751d55bccdb",
          "https://github.com/vllm-project/vllm/releases/tag/v0.31.0",
          "https://github.com/vllm-project/vllm/blob/main/vllm/entrypoints/launchers/launcher.py",
          "https://kubernetes.io/docs/reference/kubernetes-api/core/pod-v1/#Probe"
        ],
        "Read the shared method": "https://new.ontherice.org/how-otr-works/#probability-framework"
      },
      "supplied_reference_quote": null,
      "current_price_display": "Not applicable",
      "change_24h_display": "",
      "blank_change_24h": true,
      "prediction_activation": false,
      "scoring_eligible": false,
      "entry_status": "NOT_APPLICABLE",
      "horizon": "N/A",
      "horizon_hours": null,
      "expiry_utc": null,
      "resolves_at_utc": null,
      "report_authored_at_utc": "2026-10-09T05:03:52.071808Z",
      "forecast_prepared_at_utc": "2026-10-09T05:03:52.071808Z",
      "native_publication_time_utc": null,
      "publication_timestamp": null,
      "clock_label": "Research prepared",
      "clock_note": "Preparation and source clocks are separate. First public publication remains unset until deployment is verified.",
      "fact_review_state": "PRIMARY_SOURCE_AND_PEER_REVIEW_PASSED",
      "review_status": "PASSED",
      "source_batch": "OTR Database Data",
      "card_scope": "Noninvestment operational thesis",
      "sources_review": "We read source code, test definitions and author-reported measurements. We did not execute either project, reproduce benchmarks, inspect a production deployment or verify a containing stable release. The latest vLLM stable tag inspected was v0.31.0 and its launcher lacked the new acceptance loop. Current-main inspection was bounded to launcher lines 30–150. The health-check test and the GPU-serving tests use different workloads and cannot be pooled.",
      "source_gaps": [
        "We read source code, test definitions and author-reported measurements. We did not execute either project, reproduce benchmarks, inspect a production deployment or verify a containing stable release. The latest vLLM stable tag inspected was v0.31.0 and its launcher lacked the new acceptance loop. Current-main inspection was bounded to launcher lines 30–150. The health-check test and the GPU-serving tests use different workloads and cannot be pooled."
      ],
      "research_cutoff_utc": "2026-10-09T05:07:35.330861Z",
      "target_research_cutoff_utc": "2026-10-09T05:24:20Z",
      "selection_status": "READY_NONINVESTMENT",
      "research_finalized_at_utc": "2026-10-09T05:07:35.330861Z",
      "evidence_eligibility_cutoff_utc": "2026-10-09T05:03:52.071808Z",
      "novelty_review": {
        "titles_checked": 375,
        "exact_source_commit_already_published": false,
        "difference": "New connection-acceptance skew and health-response trade-off; prior GPU allocation, worker stalls, test isolation and state-restoration cards are different mechanisms."
      },
      "observations": [
        {
          "fact": "vLLM PR 60723 merged at 04:40:13 UTC and its launcher balances using open plus connecting socket counts with bounded deferral.",
          "source_ids": [
            "VLLM-BALANCED-ACCEPT:COMMIT"
          ],
          "observation_time": "2026-10-09T04:40:13Z"
        },
        {
          "fact": "The vLLM author reports slower /health p99 in a synthetic mixed CPU-render workload; this is distinct from the short-request GPU-serving benchmark.",
          "source_ids": [
            "VLLM-BALANCED-ACCEPT:PR"
          ],
          "observation_time": null,
          "clock_note": "Benchmark execution clock not supplied."
        },
        {
          "fact": "Codex retains separate session routes on shared transport and explicitly avoids replaying the failed execution in route-loss recovery tests.",
          "source_ids": [
            "CODEX-SESSION-ROUTE:COMMIT"
          ],
          "observation_time": "2026-10-09T02:51:14Z"
        }
      ],
      "check_time_display": "Confirm the containing release, then compare connection distribution, health-check responses and session continuity under the intended workload. No timed market expiry.",
      "review": {
        "status": "PASSED",
        "scope": "Evidence reviewer and Social peer reviewed source boundaries, novelty, clocks, seven sections and three probability frameworks.",
        "corrections_applied": [
          "Narrowed broad routing thesis to the health-check trade-off.",
          "Preserved distinct CPU-probe and GPU-serving benchmark settings.",
          "Aligned Codex normalized publication clock to PR creation; preserved merge and commit clocks separately."
        ],
        "facts_and_prices_fully_verified": false,
        "note": "No market price applies. Source-code and documented-contract facts checked; performance remains author-reported and production effects unverified."
      },
      "release_id": "OTR-SIGNALS-20261009-052420Z-FORCE-1"
    },
    {
      "schema": "OTR-SIGNALS-CATEGORY-CARD-1",
      "id": "SOC-20261009-THERANOS-PLAYFUL-PROMOTION-DISCLOSURE",
      "primary_category": "social",
      "categories": [
        "social"
      ],
      "title": "Theranos.world earns praise while ad disclosure remains contested",
      "summary": "We see fresh nostalgia and advertising pushback continuing around Theranos.world, a playful website promoted by people describing their work with Extend. Its Hacker News discussion has gained points and replies since our earlier capture. The useful lesson is to separate enjoying the experience, recognising the promotion and trusting the product behind it. This one discussion cannot tell us how the wider public feels.",
      "signal_claim": "We see fresh nostalgia and advertising pushback continuing around Theranos.world, a playful website promoted by people describing their work with Extend. Its Hacker News discussion has gained points and replies since our earlier capture. The useful lesson is to separate enjoying the experience, recognising the promotion and trusting the product behind it. This one discussion cannot tell us how the wider public feels.",
      "thesis": "We see fresh nostalgia and advertising pushback continuing around Theranos.world, a playful website promoted by people describing their work with Extend. Its Hacker News discussion has gained points and replies since our earlier capture. The useful lesson is to separate enjoying the experience, recognising the promotion and trusting the product behind it. This one discussion cannot tell us how the wider public feels.",
      "publication_status": "READY",
      "status": "REVIEWED_EDITORIAL_CARD",
      "key_points": [
        "We reviewed all 127 readable comment bodies in the 04:58:46 UTC capture and one additional body visible at 05:05:39 UTC. The later page also included one empty flagged record. This is a bounded view of one self-selected discussion, not a public-opinion sample.",
        "The advertising purpose is acknowledged by the submitter. Separately, an existing reply asks for clearer upfront disclosure; another praises the effort behind the experience. We can report both without deciding how common either view is.",
        "The newly checked replies add ad fatigue and affectionate interface nostalgia. They continue themes already present in the thread; they do not establish a reversal from support to opposition.",
        "Enjoyment, recognition of a promotion, document accuracy and paid product use need different evidence. A point or a comment does not establish all four."
      ],
      "bottom_line": "Our design inference is to keep the submitter’s stated promotional purpose easy to find and measure understanding separately from attention. We have not tested whether that would change visitor behaviour. The new evidence shows a live, mixed discussion about the experience. It gives designers a question to test, not a commercial verdict or a market-direction call.",
      "analysis": {
        "mechanism": "The Hacker News discussion is about Theranos.world, a website participants describe as a playful reconstruction of Elizabeth Holmes’s workspace. Our signal concerns discussion of this new website, not a new event at the historical company. The Hacker News submission was posted on 8 October at 17:51:49 UTC. The submitter, kbyatnal, says their team used Extend to parse documents for the experience and calls it content marketing. We treat those as the submitter’s statements, not an independent test of the documents or product. [Discussion](https://news.ycombinator.com/item?id=50009295) [Team’s explanation](https://news.ycombinator.com/item?id=50013534)\n\nThe conversation is still adding contrasting reactions. At 02:39:02 UTC on 9 October, a participant answered the call for fun advertising with a wish for ads to disappear. At 04:55:52 UTC, another participant warmly compared the experience with Microsoft Bob. The second comment was posted less than an hour before our latest source check. These are two individual responses, not a measured shift in the whole thread. [Advertising pushback](https://news.ycombinator.com/item?id=50015328) [Fresh nostalgia](https://news.ycombinator.com/item?id=50016145)\n\nOur native page showed 281 points and 115 displayed comments at 01:53:09 UTC, then 355 points and 128 displayed comments at 05:05:39 UTC. That is an observed increase of 74 points and 13 displayed comments across three hours, 12 minutes and 30 seconds. It shows continued activity in one forum. It does not prove wider virality, increased trust, or new customers.",
        "impact": "The case gives publishers and designers a concrete reason to test whether viewers understand a promotion as well as enjoy it. It does not measure a change in purchasing behaviour.",
        "uncertainties": [
          "One self-selected HN thread cannot establish broad social sentiment.",
          "Platform counters are not unique people, approval of each statement or purchases.",
          "X and LinkedIn access gaps prevent direct comparison across platforms.",
          "Document accuracy, product performance, intent beyond the submitter’s statements and commercial outcomes were not tested."
        ],
        "countercase": "Several participants recognise the promotion and still welcome the work. One praises the effort put into the experience, while a self-described critic of advertising makes an exception for this presentation. Their comments challenge a simple claim that promotional content always drives viewers away. [Appreciation of the work](https://news.ycombinator.com/item?id=50013399) [Qualified support](https://news.ycombinator.com/item?id=50011356)\n\nThe opposing evidence matters too. A participant asks for more upfront disclosure, and another says they initially thought the film-signup element was a joke. We cannot tell when the latter comment was edited, or whether other users had the same experience. The available record supports a question about clarity, not an allegation of deliberate deception. [Disclosure preference](https://news.ycombinator.com/item?id=50013674) [One participant’s edited account](https://news.ycombinator.com/item?id=50012325)\n\nNothing in our read measures the accuracy or completeness of the underlying document collection, Extend’s product performance, signups or sales. A broader audience sample, a direct usability test and verified conversion data could produce a different view.",
        "next_check": "A useful next check would compare whether visitors recognise the promotion before and after trying the site, using the same clearly defined sample. Any future product or sales claim would need separate evidence. No market deadline or recurring monitor is set.",
        "named_assets": [],
        "directional_takeaway": "Not applicable"
      },
      "named_assets": [],
      "named_actors": [
        "Hacker News participants",
        "Theranos.world",
        "Extend"
      ],
      "directional_takeaway": "N/A",
      "direction_display": "Not applicable",
      "uncertainty": "A bounded forum observation with attributed views and incomplete cross-platform access. No representative sentiment, causality, customer conversion or product-quality conclusion is established.",
      "next_check": "A useful next check would compare whether visitors recognise the promotion before and after trying the site, using the same clearly defined sample. Any future product or sales claim would need separate evidence. No market deadline or recurring monitor is set.",
      "check_time_utc": null,
      "check_time_label": "Check time",
      "check_time_display": "A useful next check would compare whether visitors recognise the promotion before and after trying the site, using the same clearly defined sample. Any future product or sales claim would need separate evidence. No market deadline or recurring monitor is set.",
      "source_confidence": {
        "verified": false,
        "label": "Strong for native clocks, text and recorded counters; limited for wider public behaviour and product claims",
        "reason": "Native HN captures and selected official API records retained. X and LinkedIn unavailable; no independent product or archival-content audit."
      },
      "source_labels": [
        "OTR Database Data"
      ],
      "sources": [
        {
          "source_id": "HN-50009295",
          "url": "https://news.ycombinator.com/item?id=50009295",
          "title": "Theranos.world discussion",
          "publisher": "Hacker News",
          "source_clock": {
            "published_at_utc": "2026-10-08T17:51:49+00:00",
            "precision": "Official API epoch, exact second"
          },
          "retrieved_at_utc": "2026-10-09T05:05:41.688812+00:00",
          "evidence_role": "One discussion and cumulative engagement counters",
          "origin_cluster": "THERANOS-WORLD-20261008",
          "engagement": {
            "points": 355,
            "api_descendants": 128
          },
          "review_method": "Native HTML and official API; all 128 readable native bodies across two captures reviewed",
          "engagement_observations": {
            "native_html_observations": [
              {
                "retrieved_at_utc": "2026-10-09T01:53:09.474905+00:00",
                "points": 281,
                "displayed_comments": 115,
                "parsed_rows": 116,
                "readable_bodies": 115,
                "sha256": "8c9828e405a4c18fe14fa90519af2aa0201aa9f4e831783de62a2a8c9aa764e5"
              },
              {
                "retrieved_at_utc": "2026-10-09T04:58:46.005059+00:00",
                "points": 352,
                "displayed_comments": 127,
                "parsed_rows": 128,
                "readable_bodies": 127,
                "sha256": "488a3cf7c95a03295ad81276b362410d84cd4bef4922062aa7e0c1acdc2cb514"
              },
              {
                "retrieved_at_utc": "2026-10-09T05:05:39.539337+00:00",
                "points": 355,
                "displayed_comments": 128,
                "parsed_rows": 129,
                "readable_bodies": 128,
                "sha256": "b2f4426996d50269a7ac5b2cc79e2c77248dbfec9828ca27ac009c22507d0850"
              }
            ],
            "prior_to_latest_change": {
              "elapsed_seconds": 11550.064432,
              "points": 74,
              "displayed_comments": 13
            },
            "run_local_change": {
              "elapsed_seconds": 413.534278,
              "points": 3,
              "displayed_comments": 1
            },
            "api_observations": [
              {
                "retrieved_at_utc": "2026-10-09T01:54:05.282130+00:00",
                "points": 281,
                "descendants": 115
              },
              {
                "retrieved_at_utc": "2026-10-09T04:58:43.562575+00:00",
                "points": 352,
                "descendants": 128
              },
              {
                "retrieved_at_utc": "2026-10-09T05:05:41.688812+00:00",
                "points": 355,
                "descendants": 128
              }
            ],
            "method": "Only same-route native HTML point/comment fields used in public deltas. API fields retained separately; no extrapolation or acceleration estimate."
          }
        },
        {
          "source_id": "HN-50011444",
          "url": "https://news.ycombinator.com/item?id=50011444",
          "title": "Attributed reply by kbyatnal",
          "publisher": "Hacker News",
          "source_clock": {
            "published_at_utc": "2026-10-08T20:11:11+00:00",
            "precision": "Official API epoch, exact second; edit time unavailable"
          },
          "retrieved_at_utc": "2026-10-09T05:00:59.252608+00:00",
          "evidence_role": "Participant statement, not independent product or historical verification",
          "origin_cluster": "THERANOS-WORLD-20261008",
          "review_method": "Whole native reply and official API record read"
        },
        {
          "source_id": "HN-50013534",
          "url": "https://news.ycombinator.com/item?id=50013534",
          "title": "Attributed reply by kbyatnal",
          "publisher": "Hacker News",
          "source_clock": {
            "published_at_utc": "2026-10-08T22:48:55+00:00",
            "precision": "Official API epoch, exact second; edit time unavailable"
          },
          "retrieved_at_utc": "2026-10-09T05:00:59.260115+00:00",
          "evidence_role": "Participant statement, not independent product or historical verification",
          "origin_cluster": "THERANOS-WORLD-20261008",
          "review_method": "Whole native reply and official API record read"
        },
        {
          "source_id": "HN-50013674",
          "url": "https://news.ycombinator.com/item?id=50013674",
          "title": "Attributed reply by Jtarii",
          "publisher": "Hacker News",
          "source_clock": {
            "published_at_utc": "2026-10-08T23:04:43+00:00",
            "precision": "Official API epoch, exact second; edit time unavailable"
          },
          "retrieved_at_utc": "2026-10-09T05:00:59.261092+00:00",
          "evidence_role": "Participant statement, not independent product or historical verification",
          "origin_cluster": "THERANOS-WORLD-20261008",
          "review_method": "Whole native reply and official API record read"
        },
        {
          "source_id": "HN-50012215",
          "url": "https://news.ycombinator.com/item?id=50012215",
          "title": "Attributed reply by next_xibalba",
          "publisher": "Hacker News",
          "source_clock": {
            "published_at_utc": "2026-10-08T21:02:12+00:00",
            "precision": "Official API epoch, exact second; edit time unavailable"
          },
          "retrieved_at_utc": "2026-10-09T05:00:59.260859+00:00",
          "evidence_role": "Participant statement, not independent product or historical verification",
          "origin_cluster": "THERANOS-WORLD-20261008",
          "review_method": "Whole native reply and official API record read"
        },
        {
          "source_id": "HN-50013399",
          "url": "https://news.ycombinator.com/item?id=50013399",
          "title": "Attributed reply by chaidhat",
          "publisher": "Hacker News",
          "source_clock": {
            "published_at_utc": "2026-10-08T22:36:19+00:00",
            "precision": "Official API epoch, exact second; edit time unavailable"
          },
          "retrieved_at_utc": "2026-10-09T05:01:07.319075+00:00",
          "evidence_role": "Participant statement, not independent product or historical verification",
          "origin_cluster": "THERANOS-WORLD-20261008",
          "review_method": "Whole native reply and official API record read"
        },
        {
          "source_id": "HN-50011356",
          "url": "https://news.ycombinator.com/item?id=50011356",
          "title": "Attributed reply by bbor",
          "publisher": "Hacker News",
          "source_clock": {
            "published_at_utc": "2026-10-08T20:06:39+00:00",
            "precision": "Official API epoch, exact second; edit time unavailable"
          },
          "retrieved_at_utc": "2026-10-09T05:01:07.258718+00:00",
          "evidence_role": "Participant statement, not independent product or historical verification",
          "origin_cluster": "THERANOS-WORLD-20261008",
          "review_method": "Whole native reply and official API record read"
        },
        {
          "source_id": "HN-50015328",
          "url": "https://news.ycombinator.com/item?id=50015328",
          "title": "Attributed reply by topaz0",
          "publisher": "Hacker News",
          "source_clock": {
            "published_at_utc": "2026-10-09T02:39:02+00:00",
            "precision": "Official API epoch, exact second; edit time unavailable"
          },
          "retrieved_at_utc": "2026-10-09T05:01:07.269069+00:00",
          "evidence_role": "Participant statement, not independent product or historical verification",
          "origin_cluster": "THERANOS-WORLD-20261008",
          "review_method": "Whole native reply and official API record read"
        },
        {
          "source_id": "HN-50016145",
          "url": "https://news.ycombinator.com/item?id=50016145",
          "title": "Attributed reply by 3RTB297",
          "publisher": "Hacker News",
          "source_clock": {
            "published_at_utc": "2026-10-09T04:55:52+00:00",
            "precision": "Official API epoch, exact second; edit time unavailable"
          },
          "retrieved_at_utc": "2026-10-09T05:01:07.258424+00:00",
          "evidence_role": "Participant statement, not independent product or historical verification",
          "origin_cluster": "THERANOS-WORLD-20261008",
          "review_method": "Whole native reply and official API record read"
        },
        {
          "source_id": "HN-50012325",
          "url": "https://news.ycombinator.com/item?id=50012325",
          "title": "Attributed reply by kogasa240p",
          "publisher": "Hacker News",
          "source_clock": {
            "published_at_utc": "2026-10-08T21:09:12+00:00",
            "precision": "Official API epoch, exact second; edit time unavailable"
          },
          "retrieved_at_utc": "2026-10-09T05:01:13.383677+00:00",
          "evidence_role": "Participant statement, not independent product or historical verification",
          "origin_cluster": "THERANOS-WORLD-20261008",
          "review_method": "Whole native reply and official API record read"
        },
        {
          "source_id": "HN-50011508",
          "url": "https://news.ycombinator.com/item?id=50011508",
          "title": "Attributed reply by sgustard",
          "publisher": "Hacker News",
          "source_clock": {
            "published_at_utc": "2026-10-08T20:15:31+00:00",
            "precision": "Official API epoch, exact second; edit time unavailable"
          },
          "retrieved_at_utc": "2026-10-09T05:01:13.487397+00:00",
          "evidence_role": "Participant statement, not independent product or historical verification",
          "origin_cluster": "THERANOS-WORLD-20261008",
          "review_method": "Whole native reply and official API record read"
        },
        {
          "source_id": "HN-50011459",
          "url": "https://news.ycombinator.com/item?id=50011459",
          "title": "Attributed reply by skrrtww",
          "publisher": "Hacker News",
          "source_clock": {
            "published_at_utc": "2026-10-08T20:11:52+00:00",
            "precision": "Official API epoch, exact second; edit time unavailable"
          },
          "retrieved_at_utc": "2026-10-09T05:01:13.486818+00:00",
          "evidence_role": "Participant statement, not independent product or historical verification",
          "origin_cluster": "THERANOS-WORLD-20261008",
          "review_method": "Whole native reply and official API record read"
        }
      ],
      "source_links": [
        "https://news.ycombinator.com/item?id=50009295",
        "https://news.ycombinator.com/item?id=50011444",
        "https://news.ycombinator.com/item?id=50013534",
        "https://news.ycombinator.com/item?id=50013674",
        "https://news.ycombinator.com/item?id=50012215",
        "https://news.ycombinator.com/item?id=50013399",
        "https://news.ycombinator.com/item?id=50011356",
        "https://news.ycombinator.com/item?id=50015328",
        "https://news.ycombinator.com/item?id=50016145",
        "https://news.ycombinator.com/item?id=50012325",
        "https://news.ycombinator.com/item?id=50011508",
        "https://news.ycombinator.com/item?id=50011459"
      ],
      "supplied_intelligence_layers": {
        "evidenceClusters": "We began with OTR Database Data, including the latest available social summary and recent research on attention measurement. The social summary’s new items were technical issue reports, so we did not use them as proof of social virality. We then retained the native Hacker News page and official API records. Eleven selected comment records give exact UTC publication clocks, including the submitter’s explanation, both sides of the promotion debate and the 04:55:52 reply. [Original discussion](https://news.ycombinator.com/item?id=50009295)\n\nAt 05:05:39 UTC, the page displayed 128 comments and contained 129 parsed rows, including one empty body. At 05:05:41 UTC, the official API reported 355 points and 128 descendants. We keep each field and clock separate. Across the two captures made during this research run, the page added three points and one displayed comment in six minutes and 54 seconds. The additional visible reply was stamped 04:58:14, before our first capture; visibility change is not an exact count of new publications. Differences between these fields do not prove that someone suppressed a comment.",
        "behaviouralMemory": "Market-price history does not apply. Our earlier capture was an unpublished research lead, and its clock remains 01:53:09 UTC. Comparing it with the new native capture gives a real short-window counter change. We do not turn that interval into a 24-hour rate or assume that votes measure approval of a sponsor. An earlier OTR archive-access card concerned downloads and preservation; this case concerns how people respond to a promotional experience. We found no Theranos.world or Extend case among the 375 published-card records checked for novelty.",
        "contradictionEngine": "Several participants recognise the promotion and still welcome the work. One praises the effort put into the experience, while a self-described critic of advertising makes an exception for this presentation. Their comments challenge a simple claim that promotional content always drives viewers away. [Appreciation of the work](https://news.ycombinator.com/item?id=50013399) [Qualified support](https://news.ycombinator.com/item?id=50011356)\n\nThe opposing evidence matters too. A participant asks for more upfront disclosure, and another says they initially thought the film-signup element was a joke. We cannot tell when the latter comment was edited, or whether other users had the same experience. The available record supports a question about clarity, not an allegation of deliberate deception. [Disclosure preference](https://news.ycombinator.com/item?id=50013674) [One participant’s edited account](https://news.ycombinator.com/item?id=50012325)\n\nNothing in our read measures the accuracy or completeness of the underlying document collection, Extend’s product performance, signups or sales. A broader audience sample, a direct usability test and verified conversion data could produce a different view.",
        "signalReversalTracker": "No investment direction is issued or reversed. The new material is a fresh count and newly published replies to an 8 October submission. The ad-fatigue reply at 02:39:02 UTC and the nostalgic comparison at 04:55:52 UTC add current evidence of contrasting reactions. Earlier criticism about disclosure remains earlier criticism. We do not reset the website’s earlier launch date or claim that sentiment has flipped.",
        "socialRealityCheck": "The same experience can be enjoyable and promotional. One participant values its craft; another would prefer to know its purpose before clicking. These positions can coexist, so we do not force each person into a positive or negative sentiment label. The submitter’s own explanation supports describing the project as a promotion, while saying nothing about whether its software performs well. [Stated purpose](https://news.ycombinator.com/item?id=50013534) [Disclosure objection](https://news.ycombinator.com/item?id=50013674)\n\nThe original creator’s X page returned an access denial, and the company’s LinkedIn page was also unavailable. We did not retrieve the linked video or its audience counters. Search snippets and copied reports do not fill those gaps. This leaves our social finding limited to the native HN record.",
        "predictionCalibration": "We have no earlier frozen OTR forecast for this project and no tested model connecting discussion counts with disclosure awareness, adoption or revenue. There is no HIT/MISS result, hit rate or validated virality probability. We would need comparable campaigns, consistent observation windows and separate outcomes for attention, understanding and use before estimating one."
      },
      "probability_framework": "This is a noninvestment social observation. We apply three checks to the evidence without inventing a probability of virality, sales or market direction.",
      "probability_framework_details": [
        {
          "title": "Bayesian · what changed the estimate?",
          "text": "The submitter’s explicit account gives us a firmer basis for identifying the promotional purpose. The newly checked replies show that nostalgia and ad fatigue remain live responses. They do not establish how common either is, and they do not update a measured rate of product adoption. We have no fitted prior or likelihood model, so we keep the conclusion qualitative."
        },
        {
          "title": "de Finetti · are the comparisons fair?",
          "text": "The thread, its replies and the team’s statements are linked to one website and one forum audience. Replies can influence later replies, and returning participants can write more than once. We cannot treat every comment as an independent campaign test or assume these users are interchangeable with all potential customers. The two native captures are observations of the same evolving thread."
        },
        {
          "title": "Kolmogorov · do the numbers agree?",
          "text": "Enjoying the site and recognising it as an advertisement can both be true for one person. They are not opposite outcomes whose percentages must sum to 100. Points, displayed comments and API descendants use different counting rules and cannot be added into an audience total. No asset, reference price, neutral band or investment-probability partition applies here."
        }
      ],
      "probability_framework_sections": [
        {
          "title": "Bayesian · what changed the estimate?",
          "text": "The submitter’s explicit account gives us a firmer basis for identifying the promotional purpose. The newly checked replies show that nostalgia and ad fatigue remain live responses. They do not establish how common either is, and they do not update a measured rate of product adoption. We have no fitted prior or likelihood model, so we keep the conclusion qualitative."
        },
        {
          "title": "de Finetti · are the comparisons fair?",
          "text": "The thread, its replies and the team’s statements are linked to one website and one forum audience. Replies can influence later replies, and returning participants can write more than once. We cannot treat every comment as an independent campaign test or assume these users are interchangeable with all potential customers. The two native captures are observations of the same evolving thread."
        },
        {
          "title": "Kolmogorov · do the numbers agree?",
          "text": "Enjoying the site and recognising it as an advertisement can both be true for one person. They are not opposite outcomes whose percentages must sum to 100. Points, displayed comments and API descendants use different counting rules and cannot be added into an audience total. No asset, reference price, neutral band or investment-probability partition applies here."
        }
      ],
      "accordion_sections": [
        {
          "title": "How likely is this call? · Three frameworks",
          "text": "This is a noninvestment social observation. We apply three checks to the evidence without inventing a probability of virality, sales or market direction.",
          "children": [
            {
              "title": "Bayesian · what changed the estimate?",
              "text": "The submitter’s explicit account gives us a firmer basis for identifying the promotional purpose. The newly checked replies show that nostalgia and ad fatigue remain live responses. They do not establish how common either is, and they do not update a measured rate of product adoption. We have no fitted prior or likelihood model, so we keep the conclusion qualitative."
            },
            {
              "title": "de Finetti · are the comparisons fair?",
              "text": "The thread, its replies and the team’s statements are linked to one website and one forum audience. Replies can influence later replies, and returning participants can write more than once. We cannot treat every comment as an independent campaign test or assume these users are interchangeable with all potential customers. The two native captures are observations of the same evolving thread."
            },
            {
              "title": "Kolmogorov · do the numbers agree?",
              "text": "Enjoying the site and recognising it as an advertisement can both be true for one person. They are not opposite outcomes whose percentages must sum to 100. Points, displayed comments and API descendants use different counting rules and cannot be added into an audience total. No asset, reference price, neutral band or investment-probability partition applies here."
            }
          ],
          "nested_sections": [
            {
              "title": "Bayesian · what changed the estimate?",
              "text": "The submitter’s explicit account gives us a firmer basis for identifying the promotional purpose. The newly checked replies show that nostalgia and ad fatigue remain live responses. They do not establish how common either is, and they do not update a measured rate of product adoption. We have no fitted prior or likelihood model, so we keep the conclusion qualitative."
            },
            {
              "title": "de Finetti · are the comparisons fair?",
              "text": "The thread, its replies and the team’s statements are linked to one website and one forum audience. Replies can influence later replies, and returning participants can write more than once. We cannot treat every comment as an independent campaign test or assume these users are interchangeable with all potential customers. The two native captures are observations of the same evolving thread."
            },
            {
              "title": "Kolmogorov · do the numbers agree?",
              "text": "Enjoying the site and recognising it as an advertisement can both be true for one person. They are not opposite outcomes whose percentages must sum to 100. Points, displayed comments and API descendants use different counting rules and cannot be added into an audience total. No asset, reference price, neutral band or investment-probability partition applies here."
            }
          ]
        },
        {
          "title": "Evidence behind this view",
          "text": "We began with OTR Database Data, including the latest available social summary and recent research on attention measurement. The social summary’s new items were technical issue reports, so we did not use them as proof of social virality. We then retained the native Hacker News page and official API records. Eleven selected comment records give exact UTC publication clocks, including the submitter’s explanation, both sides of the promotion debate and the 04:55:52 reply. [Original discussion](https://news.ycombinator.com/item?id=50009295)\n\nAt 05:05:39 UTC, the page displayed 128 comments and contained 129 parsed rows, including one empty body. At 05:05:41 UTC, the official API reported 355 points and 128 descendants. We keep each field and clock separate. Across the two captures made during this research run, the page added three points and one displayed comment in six minutes and 54 seconds. The additional visible reply was stamped 04:58:14, before our first capture; visibility change is not an exact count of new publications. Differences between these fields do not prove that someone suppressed a comment."
        },
        {
          "title": "What past price moves show",
          "text": "Market-price history does not apply. Our earlier capture was an unpublished research lead, and its clock remains 01:53:09 UTC. Comparing it with the new native capture gives a real short-window counter change. We do not turn that interval into a 24-hour rate or assume that votes measure approval of a sponsor. An earlier OTR archive-access card concerned downloads and preservation; this case concerns how people respond to a promotional experience. We found no Theranos.world or Extend case among the 375 published-card records checked for novelty."
        },
        {
          "title": "Evidence against this view",
          "text": "Several participants recognise the promotion and still welcome the work. One praises the effort put into the experience, while a self-described critic of advertising makes an exception for this presentation. Their comments challenge a simple claim that promotional content always drives viewers away. [Appreciation of the work](https://news.ycombinator.com/item?id=50013399) [Qualified support](https://news.ycombinator.com/item?id=50011356)\n\nThe opposing evidence matters too. A participant asks for more upfront disclosure, and another says they initially thought the film-signup element was a joke. We cannot tell when the latter comment was edited, or whether other users had the same experience. The available record supports a question about clarity, not an allegation of deliberate deception. [Disclosure preference](https://news.ycombinator.com/item?id=50013674) [One participant’s edited account](https://news.ycombinator.com/item?id=50012325)\n\nNothing in our read measures the accuracy or completeness of the underlying document collection, Extend’s product performance, signups or sales. A broader audience sample, a direct usability test and verified conversion data could produce a different view."
        },
        {
          "title": "Why the direction changed",
          "text": "No investment direction is issued or reversed. The new material is a fresh count and newly published replies to an 8 October submission. The ad-fatigue reply at 02:39:02 UTC and the nostalgic comparison at 04:55:52 UTC add current evidence of contrasting reactions. Earlier criticism about disclosure remains earlier criticism. We do not reset the website’s earlier launch date or claim that sentiment has flipped."
        },
        {
          "title": "What people say vs the facts",
          "text": "The same experience can be enjoyable and promotional. One participant values its craft; another would prefer to know its purpose before clicking. These positions can coexist, so we do not force each person into a positive or negative sentiment label. The submitter’s own explanation supports describing the project as a promotion, while saying nothing about whether its software performs well. [Stated purpose](https://news.ycombinator.com/item?id=50013534) [Disclosure objection](https://news.ycombinator.com/item?id=50013674)\n\nThe original creator’s X page returned an access denial, and the company’s LinkedIn page was also unavailable. We did not retrieve the linked video or its audience counters. Search snippets and copied reports do not fill those gaps. This leaves our social finding limited to the native HN record."
        },
        {
          "title": "How past forecasts performed",
          "text": "We have no earlier frozen OTR forecast for this project and no tested model connecting discussion counts with disclosure awareness, adoption or revenue. There is no HIT/MISS result, hit rate or validated virality probability. We would need comparable campaigns, consistent observation windows and separate outcomes for attention, understanding and use before estimating one."
        }
      ],
      "expanded_sections": [
        {
          "title": "What’s changing?",
          "text": "The Hacker News discussion is about Theranos.world, a website participants describe as a playful reconstruction of Elizabeth Holmes’s workspace. Our signal concerns discussion of this new website, not a new event at the historical company. The Hacker News submission was posted on 8 October at 17:51:49 UTC. The submitter, kbyatnal, says their team used Extend to parse documents for the experience and calls it content marketing. We treat those as the submitter’s statements, not an independent test of the documents or product. [Discussion](https://news.ycombinator.com/item?id=50009295) [Team’s explanation](https://news.ycombinator.com/item?id=50013534)\n\nThe conversation is still adding contrasting reactions. At 02:39:02 UTC on 9 October, a participant answered the call for fun advertising with a wish for ads to disappear. At 04:55:52 UTC, another participant warmly compared the experience with Microsoft Bob. The second comment was posted less than an hour before our latest source check. These are two individual responses, not a measured shift in the whole thread. [Advertising pushback](https://news.ycombinator.com/item?id=50015328) [Fresh nostalgia](https://news.ycombinator.com/item?id=50016145)\n\nOur native page showed 281 points and 115 displayed comments at 01:53:09 UTC, then 355 points and 128 displayed comments at 05:05:39 UTC. That is an observed increase of 74 points and 13 displayed comments across three hours, 12 minutes and 30 seconds. It shows continued activity in one forum. It does not prove wider virality, increased trust, or new customers."
        },
        {
          "title": "Key points",
          "items": [
            "We reviewed all 127 readable comment bodies in the 04:58:46 UTC capture and one additional body visible at 05:05:39 UTC. The later page also included one empty flagged record. This is a bounded view of one self-selected discussion, not a public-opinion sample.",
            "The advertising purpose is acknowledged by the submitter. Separately, an existing reply asks for clearer upfront disclosure; another praises the effort behind the experience. We can report both without deciding how common either view is.",
            "The newly checked replies add ad fatigue and affectionate interface nostalgia. They continue themes already present in the thread; they do not establish a reversal from support to opposition.",
            "Enjoyment, recognition of a promotion, document accuracy and paid product use need different evidence. A point or a comment does not establish all four."
          ]
        },
        {
          "title": "What could change this view?",
          "text": "Several participants recognise the promotion and still welcome the work. One praises the effort put into the experience, while a self-described critic of advertising makes an exception for this presentation. Their comments challenge a simple claim that promotional content always drives viewers away. [Appreciation of the work](https://news.ycombinator.com/item?id=50013399) [Qualified support](https://news.ycombinator.com/item?id=50011356)\n\nThe opposing evidence matters too. A participant asks for more upfront disclosure, and another says they initially thought the film-signup element was a joke. We cannot tell when the latter comment was edited, or whether other users had the same experience. The available record supports a question about clarity, not an allegation of deliberate deception. [Disclosure preference](https://news.ycombinator.com/item?id=50013674) [One participant’s edited account](https://news.ycombinator.com/item?id=50012325)\n\nNothing in our read measures the accuracy or completeness of the underlying document collection, Extend’s product performance, signups or sales. A broader audience sample, a direct usability test and verified conversion data could produce a different view."
        },
        {
          "title": "Bottom line",
          "text": "Our design inference is to keep the submitter’s stated promotional purpose easy to find and measure understanding separately from attention. We have not tested whether that would change visitor behaviour. The new evidence shows a live, mixed discussion about the experience. It gives designers a question to test, not a commercial verdict or a market-direction call."
        }
      ],
      "supplied_reference_quote": {
        "display": "Not applicable",
        "price": null,
        "currency": "Not applicable",
        "venue": "Not applicable",
        "instrument": "Not applicable",
        "price_basis": "Not applicable",
        "as_of_utc": null,
        "as_of_display": "Not applicable: no market-price call",
        "verification_status": "NOT_APPLICABLE",
        "observation_time_verified": false,
        "change_24h_percent": null,
        "session": "Not applicable"
      },
      "current_price_display": "Not applicable",
      "change_24h_display": "",
      "blank_change_24h": true,
      "prediction_activation": false,
      "scoring_eligible": false,
      "entry_status": "Not applicable",
      "horizon": "Not applicable",
      "horizon_hours": null,
      "expiry_utc": null,
      "resolves_at_utc": null,
      "report_authored_at_utc": "2026-10-09T05:08:05.846456Z",
      "forecast_prepared_at_utc": "2026-10-09T05:08:05.846456Z",
      "initial_draft_prepared_at_utc": "2026-10-09T05:03:33.683939Z",
      "native_publication_time_utc": null,
      "publication_timestamp": null,
      "clock_label": "Research prepared",
      "clock_note": "Website publication has not occurred in this research lane. Source post and comment clocks remain separate from retrieval and preparation.",
      "fact_review_state": "SOURCE_RESEARCH_WITH_DISCLOSED_LIMITS",
      "review_status": "PEER_REVIEWED_WITH_DISCLOSED_LIMITS",
      "review": {
        "peer_review_status": "PASS_WITH_DISCLOSED_LIMITS: Technology, General and independent evidence review completed",
        "final_observation_status": "COMPLETE: native HTML observed at 05:05:39.539337 UTC and official API at 05:05:41.688812 UTC",
        "review_receipt": "peer_revisions.json"
      },
      "source_batch": "OTR Database Data and native public HN evidence",
      "card_scope": "noninvestment_research",
      "research_cutoff_utc": "2026-10-09T05:05:41.688812Z",
      "research_finalized_at_utc": "2026-10-09T05:08:05.846456Z",
      "target_research_cutoff_utc": "2026-10-09T05:24:20Z",
      "data_observation_cutoff_utc": "2026-10-09T05:05:41.688812Z",
      "selection_status": "SELECTED_SOURCE_VERIFIED_NONINVESTMENT",
      "observations": [
        {
          "fact": "HN original submission on 8 October 17:51:49 UTC. Native HTML counters rose from 281/115 at 01:53:09 to 355/128 at 05:05:39 on 9 October; API counters kept separate.",
          "source_ids": [
            "HN-50009295"
          ]
        },
        {
          "fact": "New anti-ad reply at 02:39:02 and positive Microsoft Bob comparison at 04:55:52 UTC. Existing disclosure objection dates 8 October 23:04:43 UTC.",
          "source_ids": [
            "HN-50015328",
            "HN-50016145",
            "HN-50013674"
          ]
        }
      ],
      "source_gaps": [
        "X original creator page denied with HTTP 403; not retried",
        "LinkedIn company page denied with HTTP 999; not retried",
        "No native video viewed or video audience counters retrieved",
        "No representative social sample, paid conversion analytics or measured product/archival accuracy"
      ],
      "sources_review": {
        "Original published text": "Unpublished candidate; parent must freeze approved public text at actual publication.",
        "Publication time and per-investible results": "Not published; no investible call or result.",
        "Frozen preparation time": "2026-10-09T05:08:05.846456Z",
        "Actual public time": "Not yet published",
        "Exact deadline": "Not applicable",
        "Price 1 / Price 2": "Not applicable",
        "Call and evidence": "Bounded observed discussion with native posts, comment clocks and short-window engagement change.",
        "Signal evolution": "No investment direction is issued or reversed. The new material is a fresh count and newly published replies to an 8 October submission. The ad-fatigue reply at 02:39:02 UTC and the nostalgic comparison at 04:55:52 UTC add current evidence of contrasting reactions. Earlier criticism about disclosure remains earlier criticism. We do not reset the website’s earlier launch date or claim that sentiment has flipped.",
        "Named assets or actors": "Hacker News participants, Theranos.world and Extend. Historical Theranos and its medical claims are outside this signal.",
        "Directional takeaway": "Not applicable",
        "OTR reasoning": "We see fresh nostalgia and advertising pushback continuing around Theranos.world, a playful website promoted by people describing their work with Extend. Its Hacker News discussion has gained points and replies since our earlier capture. The useful lesson is to separate enjoying the experience, recognising the promotion and trusting the product behind it. This one discussion cannot tell us how the wider public feels.",
        "Counterpoint": "Several participants recognise the promotion and still welcome the work. One praises the effort put into the experience, while a self-described critic of advertising makes an exception for this presentation. Their comments challenge a simple claim that promotional content always drives viewers away. [Appreciation of the work](https://news.ycombinator.com/item?id=50013399) [Qualified support](https://news.ycombinator.com/item?id=50011356)\n\nThe opposing evidence matters too. A participant asks for more upfront disclosure, and another says they initially thought the film-signup element was a joke. We cannot tell when the latter comment was edited, or whether other users had the same experience. The available record supports a question about clarity, not an allegation of deliberate deception. [Disclosure preference](https://news.ycombinator.com/item?id=50013674) [One participant’s edited account](https://news.ycombinator.com/item?id=50012325)\n\nNothing in our read measures the accuracy or completeness of the underlying document collection, Extend’s product performance, signups or sales. A broader audience sample, a direct usability test and verified conversion data could produce a different view.",
        "Source trail": "OTR Database Data and listed native public sources.",
        "Review status": "Peer review complete; final source observation is 05:05:41.688812 UTC. Publication remains with the parent."
      },
      "public_expanded_text": "Theranos.world earns praise while ad disclosure remains contested\n\nWe see fresh nostalgia and advertising pushback continuing around Theranos.world, a playful website promoted by people describing their work with Extend. Its Hacker News discussion has gained points and replies since our earlier capture. The useful lesson is to separate enjoying the experience, recognising the promotion and trusting the product behind it. This one discussion cannot tell us how the wider public feels.\n\nWhat’s changing?\nThe Hacker News discussion is about Theranos.world, a website participants describe as a playful reconstruction of Elizabeth Holmes’s workspace. Our signal concerns discussion of this new website, not a new event at the historical company. The Hacker News submission was posted on 8 October at 17:51:49 UTC. The submitter, kbyatnal, says their team used Extend to parse documents for the experience and calls it content marketing. We treat those as the submitter’s statements, not an independent test of the documents or product. [Discussion](https://news.ycombinator.com/item?id=50009295) [Team’s explanation](https://news.ycombinator.com/item?id=50013534)\n\nThe conversation is still adding contrasting reactions. At 02:39:02 UTC on 9 October, a participant answered the call for fun advertising with a wish for ads to disappear. At 04:55:52 UTC, another participant warmly compared the experience with Microsoft Bob. The second comment was posted less than an hour before our latest source check. These are two individual responses, not a measured shift in the whole thread. [Advertising pushback](https://news.ycombinator.com/item?id=50015328) [Fresh nostalgia](https://news.ycombinator.com/item?id=50016145)\n\nOur native page showed 281 points and 115 displayed comments at 01:53:09 UTC, then 355 points and 128 displayed comments at 05:05:39 UTC. That is an observed increase of 74 points and 13 displayed comments across three hours, 12 minutes and 30 seconds. It shows continued activity in one forum. It does not prove wider virality, increased trust, or new customers.\n\nKey points\n- We reviewed all 127 readable comment bodies in the 04:58:46 UTC capture and one additional body visible at 05:05:39 UTC. The later page also included one empty flagged record. This is a bounded view of one self-selected discussion, not a public-opinion sample.\n- The advertising purpose is acknowledged by the submitter. Separately, an existing reply asks for clearer upfront disclosure; another praises the effort behind the experience. We can report both without deciding how common either view is.\n- The newly checked replies add ad fatigue and affectionate interface nostalgia. They continue themes already present in the thread; they do not establish a reversal from support to opposition.\n- Enjoyment, recognition of a promotion, document accuracy and paid product use need different evidence. A point or a comment does not establish all four.\n\nWhat could change this view?\nSeveral participants recognise the promotion and still welcome the work. One praises the effort put into the experience, while a self-described critic of advertising makes an exception for this presentation. Their comments challenge a simple claim that promotional content always drives viewers away. [Appreciation of the work](https://news.ycombinator.com/item?id=50013399) [Qualified support](https://news.ycombinator.com/item?id=50011356)\n\nThe opposing evidence matters too. A participant asks for more upfront disclosure, and another says they initially thought the film-signup element was a joke. We cannot tell when the latter comment was edited, or whether other users had the same experience. The available record supports a question about clarity, not an allegation of deliberate deception. [Disclosure preference](https://news.ycombinator.com/item?id=50013674) [One participant’s edited account](https://news.ycombinator.com/item?id=50012325)\n\nNothing in our read measures the accuracy or completeness of the underlying document collection, Extend’s product performance, signups or sales. A broader audience sample, a direct usability test and verified conversion data could produce a different view.\n\nBottom line\nOur design inference is to keep the submitter’s stated promotional purpose easy to find and measure understanding separately from attention. We have not tested whether that would change visitor behaviour. The new evidence shows a live, mixed discussion about the experience. It gives designers a question to test, not a commercial verdict or a market-direction call.\n\nHow likely is this call? · Three frameworks\nThis is a noninvestment social observation. We apply three checks to the evidence without inventing a probability of virality, sales or market direction.\nBayesian · what changed the estimate?\nThe submitter’s explicit account gives us a firmer basis for identifying the promotional purpose. The newly checked replies show that nostalgia and ad fatigue remain live responses. They do not establish how common either is, and they do not update a measured rate of product adoption. We have no fitted prior or likelihood model, so we keep the conclusion qualitative.\nde Finetti · are the comparisons fair?\nThe thread, its replies and the team’s statements are linked to one website and one forum audience. Replies can influence later replies, and returning participants can write more than once. We cannot treat every comment as an independent campaign test or assume these users are interchangeable with all potential customers. The two native captures are observations of the same evolving thread.\nKolmogorov · do the numbers agree?\nEnjoying the site and recognising it as an advertisement can both be true for one person. They are not opposite outcomes whose percentages must sum to 100. Points, displayed comments and API descendants use different counting rules and cannot be added into an audience total. No asset, reference price, neutral band or investment-probability partition applies here.\n\nEvidence behind this view\nWe began with OTR Database Data, including the latest available social summary and recent research on attention measurement. The social summary’s new items were technical issue reports, so we did not use them as proof of social virality. We then retained the native Hacker News page and official API records. Eleven selected comment records give exact UTC publication clocks, including the submitter’s explanation, both sides of the promotion debate and the 04:55:52 reply. [Original discussion](https://news.ycombinator.com/item?id=50009295)\n\nAt 05:05:39 UTC, the page displayed 128 comments and contained 129 parsed rows, including one empty body. At 05:05:41 UTC, the official API reported 355 points and 128 descendants. We keep each field and clock separate. Across the two captures made during this research run, the page added three points and one displayed comment in six minutes and 54 seconds. The additional visible reply was stamped 04:58:14, before our first capture; visibility change is not an exact count of new publications. Differences between these fields do not prove that someone suppressed a comment.\n\nWhat past price moves show\nMarket-price history does not apply. Our earlier capture was an unpublished research lead, and its clock remains 01:53:09 UTC. Comparing it with the new native capture gives a real short-window counter change. We do not turn that interval into a 24-hour rate or assume that votes measure approval of a sponsor. An earlier OTR archive-access card concerned downloads and preservation; this case concerns how people respond to a promotional experience. We found no Theranos.world or Extend case among the 375 published-card records checked for novelty.\n\nEvidence against this view\nSeveral participants recognise the promotion and still welcome the work. One praises the effort put into the experience, while a self-described critic of advertising makes an exception for this presentation. Their comments challenge a simple claim that promotional content always drives viewers away. [Appreciation of the work](https://news.ycombinator.com/item?id=50013399) [Qualified support](https://news.ycombinator.com/item?id=50011356)\n\nThe opposing evidence matters too. A participant asks for more upfront disclosure, and another says they initially thought the film-signup element was a joke. We cannot tell when the latter comment was edited, or whether other users had the same experience. The available record supports a question about clarity, not an allegation of deliberate deception. [Disclosure preference](https://news.ycombinator.com/item?id=50013674) [One participant’s edited account](https://news.ycombinator.com/item?id=50012325)\n\nNothing in our read measures the accuracy or completeness of the underlying document collection, Extend’s product performance, signups or sales. A broader audience sample, a direct usability test and verified conversion data could produce a different view.\n\nWhy the direction changed\nNo investment direction is issued or reversed. The new material is a fresh count and newly published replies to an 8 October submission. The ad-fatigue reply at 02:39:02 UTC and the nostalgic comparison at 04:55:52 UTC add current evidence of contrasting reactions. Earlier criticism about disclosure remains earlier criticism. We do not reset the website’s earlier launch date or claim that sentiment has flipped.\n\nWhat people say vs the facts\nThe same experience can be enjoyable and promotional. One participant values its craft; another would prefer to know its purpose before clicking. These positions can coexist, so we do not force each person into a positive or negative sentiment label. The submitter’s own explanation supports describing the project as a promotion, while saying nothing about whether its software performs well. [Stated purpose](https://news.ycombinator.com/item?id=50013534) [Disclosure objection](https://news.ycombinator.com/item?id=50013674)\n\nThe original creator’s X page returned an access denial, and the company’s LinkedIn page was also unavailable. We did not retrieve the linked video or its audience counters. Search snippets and copied reports do not fill those gaps. This leaves our social finding limited to the native HN record.\n\nHow past forecasts performed\nWe have no earlier frozen OTR forecast for this project and no tested model connecting discussion counts with disclosure awareness, adoption or revenue. There is no HIT/MISS result, hit rate or validated virality probability. We would need comparable campaigns, consistent observation windows and separate outcomes for attention, understanding and use before estimating one.",
      "research_cutoff_basis": "Last actual source observation, not the later target edition cutoff. No continuous observation claim.",
      "release_id": "OTR-SIGNALS-20261009-052420Z-FORCE-1"
    },
    {
      "schema": "OTR-SIGNALS-CATEGORY-CARD-1",
      "primary_category": "general",
      "categories": [
        "general"
      ],
      "supplied_reference_quote": {
        "display": "Not applicable",
        "price": null,
        "currency": "Not applicable",
        "venue": "Not applicable",
        "instrument": "Not applicable",
        "session": "Not applicable",
        "as_of_utc": null,
        "as_of_display": "Not applicable: no market-price call",
        "verification_status": "NOT_APPLICABLE",
        "observation_time_verified": false,
        "change_24h_percent": null
      },
      "current_price_display": "Not applicable",
      "change_24h_display": "",
      "blank_change_24h": true,
      "prediction_activation": false,
      "scoring_eligible": false,
      "entry_status": "NOT_APPLICABLE",
      "card_scope": "noninvestment_research",
      "id": "GEN-20261009-ELNINO-LOCAL-HEAT-WATER",
      "title": "El Niño’s stronger outlook still needs local heat and water checks",
      "summary": "We see a local planning risk in the stronger El Niño outlook: treating the Pacific signal as a country-wide dry-weather forecast. Australia’s latest outlook extends a mixed rain pattern into November–January, alongside broadly warmer conditions. We would keep heat readiness and local water planning together, using each region’s forecast and conditions.",
      "signal_claim": "We see a local planning risk in the stronger El Niño outlook: treating the Pacific signal as a country-wide dry-weather forecast. Australia’s latest outlook extends a mixed rain pattern into November–January, alongside broadly warmer conditions. We would keep heat readiness and local water planning together, using each region’s forecast and conditions.",
      "thesis": "We see a local planning risk in the stronger El Niño outlook: treating the Pacific signal as a country-wide dry-weather forecast. Australia’s latest outlook extends a mixed rain pattern into November–January, alongside broadly warmer conditions. We would keep heat readiness and local water planning together, using each region’s forecast and conditions.",
      "publication_status": "READY",
      "status": "REVIEWED_EDITORIAL_CARD",
      "key_points": [
        "We use November–January when placing the Pacific outlook beside Australia’s regional outlook. A different season answers a different question.",
        "Heat readiness may still matter in an area whose rain outlook is wetter. Local soil moisture, rivers and short-range warnings are the next checks.",
        "We read new source products dated 8 October. Their exact release hours are unverified, so a strict last-24-hour publication claim remains uncertain. No qualifying last-hour publication was established."
      ],
      "bottom_line": "We would use the stronger Pacific signal to sharpen local checks. Heat, rainfall, soil moisture and river conditions need separate attention. This is a public-preparedness research signal; it carries no crop-price, currency or stock call.",
      "analysis": {
        "mechanism": "NOAA’s 8 October discussion reports a strengthening El Niño. It gives a 70% chance that the three-month Relative Oceanic Niño Index reaches at least +2.5°C in November 2026–January 2027. That is a Pacific climate-index forecast. [NOAA](https://www.cpc.ncep.noaa.gov/products/analysis_monitoring/enso_advisory/ensodisc.shtml)\n\nFor the same November–January season, the Bureau of Meteorology’s 8 October outlook favours wetter conditions across southern and central Western Australia and several inland areas farther east. Parts of the north and south-east lean drier, while many other areas there have roughly even chances. Warmer days and nights are broadly favoured. [Australian outlook](https://www.bom.gov.au/climate/ahead/outlooks/)\n\nThe Bureau also says warm seas around Australia can supply moisture and energy for rain systems. We infer that preparations based only on the El Niño label could miss a local mix of water and heat risks. We have not measured each driver’s contribution or shown that any operator has made that mistake. A forecast of wetter seasonal totals alone cannot establish flooding or damage.",
        "impact": "We would use the stronger Pacific signal to sharpen local checks. Heat, rainfall, soil moisture and river conditions need separate attention. This is a public-preparedness research signal; it carries no crop-price, currency or stock call.",
        "uncertainties": [
          "Exact NOAA and Bureau publication hours are unavailable.",
          "Seasonal forecasts describe chances, not observed local damages.",
          "No local impact, calibrated forecast-skill or historical-disaster model was fitted.",
          "WMO publication clocks conflict and it is retained only as context."
        ],
        "countercase": "The Australian rainfall split was already visible in the previous outlook, so this is not a newly discovered climate pattern. Local influences could weaken and later forecasts could move closer to the usual El Niño pattern. We would change the regional planning view if newer local forecasts and measurements no longer support it. Seasonal guidance also cannot settle the date or severity of a particular event.",
        "next_check": "Check the next Bureau regional forecast against local rainfall, soil moisture and streamflow for the same place and period. Use current official warnings for immediate decisions. NOAA lists 12 November for its next ENSO discussion; that is a source schedule, not an OTR monitoring promise.",
        "named_assets": [],
        "directional_takeaway": "Not applicable"
      },
      "named_assets": [],
      "named_actors": [
        "NOAA Climate Prediction Center",
        "Australian Bureau of Meteorology",
        "World Meteorological Organization"
      ],
      "directional_takeaway": "N/A",
      "uncertainty": "The Australian rainfall split was already visible in the previous outlook, so this is not a newly discovered climate pattern. Local influences could weaken and later forecasts could move closer to the usual El Niño pattern. We would change the regional planning view if newer local forecasts and measurements no longer support it. Seasonal guidance also cannot settle the date or severity of a particular event.",
      "next_check": "Check the next Bureau regional forecast against local rainfall, soil moisture and streamflow for the same place and period. Use current official warnings for immediate decisions. NOAA lists 12 November for its next ENSO discussion; that is a source schedule, not an OTR monitoring promise.",
      "check_time_utc": null,
      "check_time_label": "Next evidence check",
      "check_time_display": "Check the next Bureau regional forecast against local rainfall, soil moisture and streamflow for the same place and period. Use current official warnings for immediate decisions. NOAA lists 12 November for its next ENSO discussion; that is a source schedule, not an OTR monitoring promise.",
      "source_confidence": {
        "verified": false,
        "label": "Original agency forecasts checked; local outcomes and release hours remain unverified",
        "reason": "The source text is verified, but the future regional outcomes, exact issue hours and local forecast skill are not established."
      },
      "source_labels": [
        "OTR Database Data"
      ],
      "sources": [
        {
          "source_id": "GEN-NOAA-ENSO-20261008",
          "url": "https://www.cpc.ncep.noaa.gov/products/analysis_monitoring/enso_advisory/ensodisc.shtml",
          "title": "ENSO Diagnostic Discussion, 8 October 2026",
          "publisher": "NOAA CPC / NCEP / NWS",
          "source_clock": {
            "original": "Issued 8 October 2026; exact hour not shown",
            "normalized_utc": null,
            "precision": "date"
          },
          "event_clock": {
            "original": "September observations; SON, OND, NDJ and later forecast seasons",
            "precision": "month / season"
          },
          "retrieved_at_utc": "2026-10-09T04:59:31.313191+00:00",
          "review_method": "Original HTML and substantive text read; raw bytes and SHA-256 retained",
          "limits": "Date-only issue; exact publication hour unverified. Pacific RONI forecast is not a regional-impact probability."
        },
        {
          "source_id": "GEN-BOM-OUTLOOK-20261008",
          "url": "https://www.bom.gov.au/climate/ahead/outlooks/",
          "title": "Australian rainfall and temperature outlook, issued 8 October 2026",
          "publisher": "Australian Bureau of Meteorology",
          "source_clock": {
            "original": "Issued 8 October 2026; exact hour not shown",
            "normalized_utc": null,
            "precision": "date"
          },
          "event_clock": {
            "original": "November 2026–January 2027 seasonal forecast; local sea observations for week ending 4 October",
            "precision": "month / season"
          },
          "retrieved_at_utc": "2026-10-09T05:01:06.503828+00:00",
          "review_method": "Original HTML and substantive text read; raw bytes and SHA-256 retained",
          "limits": "Date-only issue. Dynamic page creation time is not publication time. Prose read; no quantitative values inferred from map pixels."
        },
        {
          "source_id": "GEN-BOM-PRIOR-20261001",
          "url": "https://www.bom.gov.au/video/long-range-forecast-october-to-december-2026",
          "title": "Long-range forecast: October to December 2026",
          "publisher": "Australian Bureau of Meteorology",
          "source_clock": {
            "original": "Transcript says issued 1 October; page date is 2 October. Context only; forecast window differs from new product.",
            "normalized_utc": null,
            "precision": "unverified"
          },
          "event_clock": {
            "original": "October–December 2026 forecast; September conditions",
            "precision": "month / season"
          },
          "retrieved_at_utc": "2026-10-09T05:01:14.134352+00:00",
          "review_method": "Original HTML and substantive text read; raw bytes and SHA-256 retained",
          "limits": "Transcript says issued 1 October; page date is 2 October. Context only; forecast window differs from new product."
        },
        {
          "source_id": "GEN-NOAA-RONI-METHOD",
          "url": "https://www.cpc.ncep.noaa.gov/products/analysis_monitoring/enso/roni/",
          "title": "Relative Oceanic Niño Index definition and historical series",
          "publisher": "NOAA CPC",
          "source_clock": {
            "original": "Methodology only. Historical series not used to fit an impact model or derive an OTR percentage.",
            "normalized_utc": null,
            "precision": "unverified"
          },
          "event_clock": {
            "original": "Methodology; seasonal history through 2026",
            "precision": "month / season"
          },
          "retrieved_at_utc": "2026-10-09T05:01:31.590305+00:00",
          "review_method": "Original HTML and substantive text read; raw bytes and SHA-256 retained",
          "limits": "Methodology only. Historical series not used to fit an impact model or derive an OTR percentage."
        },
        {
          "source_id": "GEN-WMO-CONTEXT-20261008",
          "url": "https://wmo.int/news/media-centre/sea-surface-temperatures-reflect-strengthening-el-nino",
          "title": "Sea-surface temperatures reflect strengthening El Niño",
          "publisher": "WMO",
          "source_clock": {
            "original": "Visible date 8 October conflicts with HTML published 6 October 09:00:27Z and modified 6 October 14:38:19Z. Context only; not counted as a verified fresh publication.",
            "normalized_utc": null,
            "precision": "date"
          },
          "event_clock": {
            "original": "October–December 2026 seasonal outlook",
            "precision": "month / season"
          },
          "retrieved_at_utc": "2026-10-09T04:59:45.886247+00:00",
          "review_method": "Original HTML and substantive text read; raw bytes and SHA-256 retained",
          "limits": "Visible date 8 October conflicts with HTML published 6 October 09:00:27Z and modified 6 October 14:38:19Z. Context only; not counted as a verified fresh publication."
        }
      ],
      "source_links": [
        "https://www.cpc.ncep.noaa.gov/products/analysis_monitoring/enso_advisory/ensodisc.shtml",
        "https://www.bom.gov.au/climate/ahead/outlooks/",
        "https://www.bom.gov.au/video/long-range-forecast-october-to-december-2026",
        "https://www.cpc.ncep.noaa.gov/products/analysis_monitoring/enso/roni/",
        "https://wmo.int/news/media-centre/sea-surface-temperatures-reflect-strengthening-el-nino"
      ],
      "supplied_intelligence_layers": {
        "evidenceClusters": "We checked the original NOAA discussion and the Bureau’s full text outlook. The Bureau’s regional forecast and its climate-driver explanation support different steps: the map describes the outlook, while the warm-sea discussion gives a plausible moisture pathway. We do not claim a measured share of rainfall caused by that pathway. We connect this with OTR Database Data’s earlier work on forecast quality and service disruption: a broad indicator needs a local check before it guides an operational decision. [NOAA](https://www.cpc.ncep.noaa.gov/products/analysis_monitoring/enso_advisory/ensodisc.shtml) [Bureau](https://www.bom.gov.au/climate/ahead/outlooks/)",
        "behaviouralMemory": "No market-price history applies. The useful historical check is whether the climate measures are comparable. NOAA’s RONI is a three-month index that adjusts Pacific warmth for tropical background warmth; its newest values may later be revised. We did not calculate a historical disaster rate or treat each overlapping season as a separate case. A fair impact study would also need local exposure and weather records. [Index definition](https://www.cpc.ncep.noaa.gov/products/analysis_monitoring/enso/roni/)",
        "contradictionEngine": "The Australian rainfall split was already visible in the previous outlook, so this is not a newly discovered climate pattern. Local influences could weaken and later forecasts could move closer to the usual El Niño pattern. We would change the regional planning view if newer local forecasts and measurements no longer support it. Seasonal guidance also cannot settle the date or severity of a particular event. We also lack location-level forecast skill checks for a particular farm, town or utility. The national product is useful context, but it does not validate a single local operating choice.",
        "signalReversalTracker": "No investment direction applies and no earlier published call is changed. The earlier Bureau outlook, issued 1 October, already described a mixed regional rain pattern for October–December. The new product extends guidance into November–January; the seasons differ, so we do not call it a same-window reversal. Our new connection is the need to keep local heat and water checks together as the Pacific event strengthens. [Earlier outlook](https://www.bom.gov.au/video/long-range-forecast-october-to-december-2026)",
        "socialRealityCheck": "We did not measure public opinion or claim that a misleading narrative is spreading. The shortcut we test is simply using “strong El Niño” as a complete local plan. Actual official guidance carries regional exceptions and different forecast periods. Source reports of a likely warmer season also do not establish that a particular heatwave has occurred.",
        "predictionCalibration": "We have no matched, resolved OTR sample for this planning thesis. A forecast issued on 8 October cannot be scored against an unfinished November–January season. Later evaluation would need the frozen regional forecast, its baseline and matching outcomes. Publication dates, source authority and agreement cannot substitute for that evaluation. We retain the earlier forecast as context, without awarding a hit or miss."
      },
      "probability_framework": "This is a noninvestment signal. Market-direction percentages do not apply. Bayesian · what changed the estimate? The updated Pacific evidence strengthens the case for checking El Niño-related risks. We would update a local assessment with local rain, heat and water observations, rather than transfer the Pacific probability directly. We have not fitted a local-impact likelihood model or assigned an OTR probability. de Finetti · are the comparisons fair? We would compare the same region, season, index and starting conditions. NOAA, WMO and the Bureau use overlapping climate observations and model families; their agreement is not three independent trials. Past El Niño episodes also need checks for local ocean warmth and other climate conditions before they become fair comparisons. Kolmogorov · do the numbers agree? Pacific index strength, local rain and local heat are different events. Their percentages must not be added as parts of one whole. NOAA gives 83% for October–December and 70% for November–January at its stated historic-strength threshold. We use the latter alongside the Bureau’s November–January map. These are source forecasts, not OTR success odds.",
      "probability_framework_details": [
        {
          "title": "Bayesian · what changed the estimate?",
          "text": "The updated Pacific evidence strengthens the case for checking El Niño-related risks. We would update a local assessment with local rain, heat and water observations, rather than transfer the Pacific probability directly. We have not fitted a local-impact likelihood model or assigned an OTR probability."
        },
        {
          "title": "de Finetti · are the comparisons fair?",
          "text": "We would compare the same region, season, index and starting conditions. NOAA, WMO and the Bureau use overlapping climate observations and model families; their agreement is not three independent trials. Past El Niño episodes also need checks for local ocean warmth and other climate conditions before they become fair comparisons."
        },
        {
          "title": "Kolmogorov · do the numbers agree?",
          "text": "Pacific index strength, local rain and local heat are different events. Their percentages must not be added as parts of one whole. NOAA gives 83% for October–December and 70% for November–January at its stated historic-strength threshold. We use the latter alongside the Bureau’s November–January map. These are source forecasts, not OTR success odds."
        }
      ],
      "probability_framework_sections": [
        {
          "title": "Bayesian · what changed the estimate?",
          "text": "The updated Pacific evidence strengthens the case for checking El Niño-related risks. We would update a local assessment with local rain, heat and water observations, rather than transfer the Pacific probability directly. We have not fitted a local-impact likelihood model or assigned an OTR probability."
        },
        {
          "title": "de Finetti · are the comparisons fair?",
          "text": "We would compare the same region, season, index and starting conditions. NOAA, WMO and the Bureau use overlapping climate observations and model families; their agreement is not three independent trials. Past El Niño episodes also need checks for local ocean warmth and other climate conditions before they become fair comparisons."
        },
        {
          "title": "Kolmogorov · do the numbers agree?",
          "text": "Pacific index strength, local rain and local heat are different events. Their percentages must not be added as parts of one whole. NOAA gives 83% for October–December and 70% for November–January at its stated historic-strength threshold. We use the latter alongside the Bureau’s November–January map. These are source forecasts, not OTR success odds."
        }
      ],
      "accordion_sections": [
        {
          "title": "How likely is this call? · Three frameworks",
          "text": "This is a noninvestment signal. Market-direction percentages do not apply. Bayesian · what changed the estimate? The updated Pacific evidence strengthens the case for checking El Niño-related risks. We would update a local assessment with local rain, heat and water observations, rather than transfer the Pacific probability directly. We have not fitted a local-impact likelihood model or assigned an OTR probability. de Finetti · are the comparisons fair? We would compare the same region, season, index and starting conditions. NOAA, WMO and the Bureau use overlapping climate observations and model families; their agreement is not three independent trials. Past El Niño episodes also need checks for local ocean warmth and other climate conditions before they become fair comparisons. Kolmogorov · do the numbers agree? Pacific index strength, local rain and local heat are different events. Their percentages must not be added as parts of one whole. NOAA gives 83% for October–December and 70% for November–January at its stated historic-strength threshold. We use the latter alongside the Bureau’s November–January map. These are source forecasts, not OTR success odds.",
          "nested_sections": [
            {
              "title": "Bayesian · what changed the estimate?",
              "text": "The updated Pacific evidence strengthens the case for checking El Niño-related risks. We would update a local assessment with local rain, heat and water observations, rather than transfer the Pacific probability directly. We have not fitted a local-impact likelihood model or assigned an OTR probability."
            },
            {
              "title": "de Finetti · are the comparisons fair?",
              "text": "We would compare the same region, season, index and starting conditions. NOAA, WMO and the Bureau use overlapping climate observations and model families; their agreement is not three independent trials. Past El Niño episodes also need checks for local ocean warmth and other climate conditions before they become fair comparisons."
            },
            {
              "title": "Kolmogorov · do the numbers agree?",
              "text": "Pacific index strength, local rain and local heat are different events. Their percentages must not be added as parts of one whole. NOAA gives 83% for October–December and 70% for November–January at its stated historic-strength threshold. We use the latter alongside the Bureau’s November–January map. These are source forecasts, not OTR success odds."
            }
          ]
        },
        {
          "title": "Evidence behind this view",
          "text": "We checked the original NOAA discussion and the Bureau’s full text outlook. The Bureau’s regional forecast and its climate-driver explanation support different steps: the map describes the outlook, while the warm-sea discussion gives a plausible moisture pathway. We do not claim a measured share of rainfall caused by that pathway. We connect this with OTR Database Data’s earlier work on forecast quality and service disruption: a broad indicator needs a local check before it guides an operational decision. [NOAA](https://www.cpc.ncep.noaa.gov/products/analysis_monitoring/enso_advisory/ensodisc.shtml) [Bureau](https://www.bom.gov.au/climate/ahead/outlooks/)"
        },
        {
          "title": "What past price moves show",
          "text": "No market-price history applies. The useful historical check is whether the climate measures are comparable. NOAA’s RONI is a three-month index that adjusts Pacific warmth for tropical background warmth; its newest values may later be revised. We did not calculate a historical disaster rate or treat each overlapping season as a separate case. A fair impact study would also need local exposure and weather records. [Index definition](https://www.cpc.ncep.noaa.gov/products/analysis_monitoring/enso/roni/)"
        },
        {
          "title": "Evidence against this view",
          "text": "The Australian rainfall split was already visible in the previous outlook, so this is not a newly discovered climate pattern. Local influences could weaken and later forecasts could move closer to the usual El Niño pattern. We would change the regional planning view if newer local forecasts and measurements no longer support it. Seasonal guidance also cannot settle the date or severity of a particular event. We also lack location-level forecast skill checks for a particular farm, town or utility. The national product is useful context, but it does not validate a single local operating choice."
        },
        {
          "title": "Why the direction changed",
          "text": "No investment direction applies and no earlier published call is changed. The earlier Bureau outlook, issued 1 October, already described a mixed regional rain pattern for October–December. The new product extends guidance into November–January; the seasons differ, so we do not call it a same-window reversal. Our new connection is the need to keep local heat and water checks together as the Pacific event strengthens. [Earlier outlook](https://www.bom.gov.au/video/long-range-forecast-october-to-december-2026)"
        },
        {
          "title": "What people say vs the facts",
          "text": "We did not measure public opinion or claim that a misleading narrative is spreading. The shortcut we test is simply using “strong El Niño” as a complete local plan. Actual official guidance carries regional exceptions and different forecast periods. Source reports of a likely warmer season also do not establish that a particular heatwave has occurred."
        },
        {
          "title": "How past forecasts performed",
          "text": "We have no matched, resolved OTR sample for this planning thesis. A forecast issued on 8 October cannot be scored against an unfinished November–January season. Later evaluation would need the frozen regional forecast, its baseline and matching outcomes. Publication dates, source authority and agreement cannot substitute for that evaluation. We retain the earlier forecast as context, without awarding a hit or miss."
        }
      ],
      "expanded_sections": [
        {
          "title": "What’s changing?",
          "text": "NOAA’s 8 October discussion reports a strengthening El Niño. It gives a 70% chance that the three-month Relative Oceanic Niño Index reaches at least +2.5°C in November 2026–January 2027. That is a Pacific climate-index forecast. [NOAA](https://www.cpc.ncep.noaa.gov/products/analysis_monitoring/enso_advisory/ensodisc.shtml)\n\nFor the same November–January season, the Bureau of Meteorology’s 8 October outlook favours wetter conditions across southern and central Western Australia and several inland areas farther east. Parts of the north and south-east lean drier, while many other areas there have roughly even chances. Warmer days and nights are broadly favoured. [Australian outlook](https://www.bom.gov.au/climate/ahead/outlooks/)\n\nThe Bureau also says warm seas around Australia can supply moisture and energy for rain systems. We infer that preparations based only on the El Niño label could miss a local mix of water and heat risks. We have not measured each driver’s contribution or shown that any operator has made that mistake. A forecast of wetter seasonal totals alone cannot establish flooding or damage."
        },
        {
          "title": "Key points",
          "items": [
            "We use November–January when placing the Pacific outlook beside Australia’s regional outlook. A different season answers a different question.",
            "Heat readiness may still matter in an area whose rain outlook is wetter. Local soil moisture, rivers and short-range warnings are the next checks.",
            "We read new source products dated 8 October. Their exact release hours are unverified, so a strict last-24-hour publication claim remains uncertain. No qualifying last-hour publication was established."
          ]
        },
        {
          "title": "What could change this view?",
          "text": "The Australian rainfall split was already visible in the previous outlook, so this is not a newly discovered climate pattern. Local influences could weaken and later forecasts could move closer to the usual El Niño pattern. We would change the regional planning view if newer local forecasts and measurements no longer support it. Seasonal guidance also cannot settle the date or severity of a particular event."
        },
        {
          "title": "Bottom line",
          "text": "We would use the stronger Pacific signal to sharpen local checks. Heat, rainfall, soil moisture and river conditions need separate attention. This is a public-preparedness research signal; it carries no crop-price, currency or stock call."
        }
      ],
      "report_authored_at_utc": "2026-10-09T05:06:44.762798Z",
      "forecast_prepared_at_utc": "2026-10-09T05:06:44.762798Z",
      "native_publication_time_utc": null,
      "publication_timestamp": null,
      "clock_label": "Research prepared",
      "clock_note": "Actual preparation and source retrieval times are recorded separately from publication. No native publication is claimed.",
      "fact_review_state": "SOURCE_RESEARCH_WITH_DISCLOSED_CLOCK_LIMITS",
      "review_status": "PASS_WITH_FRESHNESS_AND_FORECAST_LIMITS",
      "review": {
        "facts_and_prices_fully_verified": false,
        "status": "PASS_WITH_FRESHNESS_AND_FORECAST_LIMITS"
      },
      "source_batch": "otr-force-20261009-0454",
      "novelty_review": {
        "read_scope": "All 375 existing signal titles; full climate/forecast-method related cards; prior forced-run General candidate; latest bounded OTR Database Data report sections.",
        "new_mechanism": "New local-readiness synthesis connects stronger Pacific evidence with region-specific rainfall, broad heat and moisture from nearby seas; no claim that mixed rain was first discovered today.",
        "nearest_existing_signal": "GEN-20261005-COP31-HEALTH-AGENDA",
        "difference": "Prior signal concerns agenda placement and health infrastructure; this concerns current seasonal guidance, regional water conditions and planning scope."
      },
      "sources_review": {
        "Source trail": "OTR Database Data; NOAA CPC; Bureau of Meteorology; WMO contextual release.",
        "Review status": "Two cross-desk peers reopened primary NOAA and Bureau pages and passed the forecast/impact, window and dependence boundaries. A third verifier reviewed original source facts. Exact publication hours remain unverified.",
        "Freshness": "New NOAA and Bureau products display 8 October; exact publication hours unverified. No last-hour publication claim. WMO clock conflict held as context.",
        "Signal evolution": "New synthesis with prior regional-outlook context. No published direction or historical outcome amended."
      },
      "research_cutoff_utc": "2026-10-09T05:24:20Z",
      "research_finalized_at_utc": "2026-10-09T05:07:59.992339Z",
      "public_expanded_text": "NOAA’s 8 October discussion reports a strengthening El Niño. It gives a 70% chance that the three-month Relative Oceanic Niño Index reaches at least +2.5°C in November 2026–January 2027. That is a Pacific climate-index forecast. [NOAA](https://www.cpc.ncep.noaa.gov/products/analysis_monitoring/enso_advisory/ensodisc.shtml)\n\nFor the same November–January season, the Bureau of Meteorology’s 8 October outlook favours wetter conditions across southern and central Western Australia and several inland areas farther east. Parts of the north and south-east lean drier, while many other areas there have roughly even chances. Warmer days and nights are broadly favoured. [Australian outlook](https://www.bom.gov.au/climate/ahead/outlooks/)\n\nThe Bureau also says warm seas around Australia can supply moisture and energy for rain systems. We infer that preparations based only on the El Niño label could miss a local mix of water and heat risks. We have not measured each driver’s contribution or shown that any operator has made that mistake. A forecast of wetter seasonal totals alone cannot establish flooding or damage.\n\nKey points\nWe use November–January when placing the Pacific outlook beside Australia’s regional outlook. A different season answers a different question.\nHeat readiness may still matter in an area whose rain outlook is wetter. Local soil moisture, rivers and short-range warnings are the next checks.\nWe read new source products dated 8 October. Their exact release hours are unverified, so a strict last-24-hour publication claim remains uncertain. No qualifying last-hour publication was established.\n\nWhat could change this view?\nThe Australian rainfall split was already visible in the previous outlook, so this is not a newly discovered climate pattern. Local influences could weaken and later forecasts could move closer to the usual El Niño pattern. We would change the regional planning view if newer local forecasts and measurements no longer support it. Seasonal guidance also cannot settle the date or severity of a particular event.\n\nBottom line\nWe would use the stronger Pacific signal to sharpen local checks. Heat, rainfall, soil moisture and river conditions need separate attention. This is a public-preparedness research signal; it carries no crop-price, currency or stock call.\n\nHow likely is this call? · Three frameworks\nThis is a noninvestment signal. Market-direction percentages do not apply. Bayesian · what changed the estimate? The updated Pacific evidence strengthens the case for checking El Niño-related risks. We would update a local assessment with local rain, heat and water observations, rather than transfer the Pacific probability directly. We have not fitted a local-impact likelihood model or assigned an OTR probability. de Finetti · are the comparisons fair? We would compare the same region, season, index and starting conditions. NOAA, WMO and the Bureau use overlapping climate observations and model families; their agreement is not three independent trials. Past El Niño episodes also need checks for local ocean warmth and other climate conditions before they become fair comparisons. Kolmogorov · do the numbers agree? Pacific index strength, local rain and local heat are different events. Their percentages must not be added as parts of one whole. NOAA gives 83% for October–December and 70% for November–January at its stated historic-strength threshold. We use the latter alongside the Bureau’s November–January map. These are source forecasts, not OTR success odds.\n\nEvidence behind this view\nWe checked the original NOAA discussion and the Bureau’s full text outlook. The Bureau’s regional forecast and its climate-driver explanation support different steps: the map describes the outlook, while the warm-sea discussion gives a plausible moisture pathway. We do not claim a measured share of rainfall caused by that pathway. We connect this with OTR Database Data’s earlier work on forecast quality and service disruption: a broad indicator needs a local check before it guides an operational decision. [NOAA](https://www.cpc.ncep.noaa.gov/products/analysis_monitoring/enso_advisory/ensodisc.shtml) [Bureau](https://www.bom.gov.au/climate/ahead/outlooks/)\n\nWhat past price moves show\nNo market-price history applies. The useful historical check is whether the climate measures are comparable. NOAA’s RONI is a three-month index that adjusts Pacific warmth for tropical background warmth; its newest values may later be revised. We did not calculate a historical disaster rate or treat each overlapping season as a separate case. A fair impact study would also need local exposure and weather records. [Index definition](https://www.cpc.ncep.noaa.gov/products/analysis_monitoring/enso/roni/)\n\nEvidence against this view\nThe Australian rainfall split was already visible in the previous outlook, so this is not a newly discovered climate pattern. Local influences could weaken and later forecasts could move closer to the usual El Niño pattern. We would change the regional planning view if newer local forecasts and measurements no longer support it. Seasonal guidance also cannot settle the date or severity of a particular event. We also lack location-level forecast skill checks for a particular farm, town or utility. The national product is useful context, but it does not validate a single local operating choice.\n\nWhy the direction changed\nNo investment direction applies and no earlier published call is changed. The earlier Bureau outlook, issued 1 October, already described a mixed regional rain pattern for October–December. The new product extends guidance into November–January; the seasons differ, so we do not call it a same-window reversal. Our new connection is the need to keep local heat and water checks together as the Pacific event strengthens. [Earlier outlook](https://www.bom.gov.au/video/long-range-forecast-october-to-december-2026)\n\nWhat people say vs the facts\nWe did not measure public opinion or claim that a misleading narrative is spreading. The shortcut we test is simply using “strong El Niño” as a complete local plan. Actual official guidance carries regional exceptions and different forecast periods. Source reports of a likely warmer season also do not establish that a particular heatwave has occurred.\n\nHow past forecasts performed\nWe have no matched, resolved OTR sample for this planning thesis. A forecast issued on 8 October cannot be scored against an unfinished November–January season. Later evaluation would need the frozen regional forecast, its baseline and matching outcomes. Publication dates, source authority and agreement cannot substitute for that evaluation. We retain the earlier forecast as context, without awarding a hit or miss.",
      "last_prose_review_utc": "2026-10-09T05:07:59.992339Z",
      "release_id": "OTR-SIGNALS-20261009-052420Z-FORCE-1"
    }
  ],
  "new_items_count": 5,
  "category_counts_primary": {
    "general": 1,
    "investments": 1,
    "singapore": 1,
    "social": 1,
    "technology": 1
  },
  "continued_from_release_id": "OTR-SIGNALS-20261009-0220Z-R1",
  "continued_current_records": [
    {
      "release_id": "OTR-SIGNALS-20261009-0220Z-R1",
      "release_payload_sha256": "9fbbfb18e0ff9b4b5974aed2c237d230d43406e3d6f356352766d9de55aa5414",
      "signal_id": "SG-20261009-CUSTODY-CASH-STATUS",
      "original_record_sha256": "9539e687ed8a824bbbaedc649f7418a9efaa2424a0a6e46b20f60f5dcedc3c93"
    },
    {
      "release_id": "OTR-SIGNALS-20261009-0220Z-R1",
      "release_payload_sha256": "9fbbfb18e0ff9b4b5974aed2c237d230d43406e3d6f356352766d9de55aa5414",
      "signal_id": "GEN-20261009-NIGERIA-STATE-SPENDING-DELIVERY",
      "original_record_sha256": "6e072ef8d263b1427bd54cc6ca944d599f9694992d147b6898ed92153a33465d"
    },
    {
      "release_id": "OTR-SIGNALS-20261009-0220Z-R1",
      "release_payload_sha256": "9fbbfb18e0ff9b4b5974aed2c237d230d43406e3d6f356352766d9de55aa5414",
      "signal_id": "TECH-20261009-PYTHON-GPU-ALLOCATION-CLEANUP",
      "original_record_sha256": "26088f58ad552af569702f7d44d47fb6a11a1c3d6f8afc72e786183479bf5775"
    },
    {
      "release_id": "OTR-SIGNALS-20261009-0220Z-R1",
      "release_payload_sha256": "9fbbfb18e0ff9b4b5974aed2c237d230d43406e3d6f356352766d9de55aa5414",
      "signal_id": "SOC-20261009-COFFEE-CLAIM-CLARIFICATION-ATTENTION",
      "original_record_sha256": "ff7a09405772905a251eef933e3a339bf32ed0c640cb26209cf0ea97bcc79c19"
    },
    {
      "release_id": "OTR-SIGNALS-20261009-0220Z-R1",
      "release_payload_sha256": "9fbbfb18e0ff9b4b5974aed2c237d230d43406e3d6f356352766d9de55aa5414",
      "signal_id": "INV-20261009-BRENT-GULF-SHUTDOWN-72H",
      "original_record_sha256": "ff2468daa3e7045f01ea79d6eca20c7f45858b440fb4d6d8852060b57df4360e"
    },
    {
      "release_id": "OTR-SIGNALS-20261009-0220Z-R1",
      "release_payload_sha256": "9fbbfb18e0ff9b4b5974aed2c237d230d43406e3d6f356352766d9de55aa5414",
      "signal_id": "INV-20261009-GOLD-REAL-YIELD-RELIEF-72H",
      "original_record_sha256": "a60533bc111a11d6e3419604b6698237d2ac6f8449a5d38d12a8a4160ac8b67f"
    }
  ],
  "source_handoff": {
    "schema": "OTR-SIGNALS-FORCED-EDITION-HANDOFF-1",
    "status": "FINAL_CONTENT_APPROVED_FOR_SINGLE_NATIVE_PUBLICATION",
    "publisher_stage_sha256": "dc735f215ffcfd35ddf1f5fcd61775ec609f0d035f9faba8f06cc28ebf067fd7",
    "final_handoff_sha256": "62d6eba3e1347ee852ca793a77a2fc04e40981cbf47ec16dc85ba41e0abc3cf0",
    "noninvestment_sources": [
      {
        "id": "SG-20261009-MYREPUBLIC-BRAND-NETWORK-OFFERS",
        "category": "singapore",
        "sha256": "4363dedf3602a861354a377d21aee36e637c688e765dec1eca5d04372a8e20ec"
      },
      {
        "id": "TECH-20261009-CONNECTION-BALANCE-HEALTH-CHECK",
        "category": "technology",
        "sha256": "01287472295ae786e31c7b6bf62ebcf30d5b058d755a206cdfd7bb790a4c5e81"
      },
      {
        "id": "SOC-20261009-THERANOS-PLAYFUL-PROMOTION-DISCLOSURE",
        "category": "social",
        "sha256": "3d68a91c7124a778b641178666faa11bbe34f32eb94c41b921936b73bac13d59"
      },
      {
        "id": "GEN-20261009-ELNINO-LOCAL-HEAT-WATER",
        "category": "general",
        "sha256": "01e709112d304a15ec1a3dab4795dc9421611f1ecbbe12d94b0557e3d64ef2fd"
      }
    ],
    "investment_signal_ids": [
      "INV-20261009-FAST-RETAILING-EARNINGS-RESET-168H"
    ],
    "investment_source_card_sha256": "5296903fd4ea37258f95de4338618cbdcd52b99ceefe6a058fcf1bbbc9394663",
    "investment_freeze_receipt_sha256": "01ea5f622041a1cafce16052aafa4d4fa7e2f23fda309409e87c30043930023c",
    "investment_quote_source_receipt_sha256": "bb1864158046b6142a235779ea87f986b13b2761aa9ce3c445066a5c1fe67764",
    "investment_engine_input_sha256": "5b0d3165944c3730df25fb18a7dce2ba62e0015dbddb3142b06e683d9f36d483",
    "investment_issue_utc": "2026-10-09T05:20:29.009Z",
    "investment_expiry_utc": "2026-10-16T05:20:29.009Z",
    "publication_timestamp_mapping": {
      "source": "Legacy card field aliases frozen research issue; preserved in private mapping receipt.",
      "projected_value": null,
      "issue_preserved_in": [
        "forecast_prepared_at_utc",
        "probability_input.issueUTC",
        "resolution_ledger.issue_utc"
      ],
      "native_publication_time_utc": null
    },
    "held_candidate": {
      "instrument": "USD/JPY",
      "state": "NOT_ISSUED_NO_FRESH_REFERENCE",
      "reason": "A fresh provider row was unavailable on the single same-route retry; no price, issue time or expiry was frozen. Stale research snapshot excluded."
    },
    "source_attribution": "OTR Database Data for database-derived context; each card retains its direct source links.",
    "native_first_publication_clock": "Not yet known. Record only after successful native Sites deployment; separate from research cutoff, preparation and per-call issue/expiry."
  },
  "coverage": {
    "new_signals": 5,
    "baseline_current_signals": 375,
    "continued_current_cards": 6,
    "by_primary_category": {
      "general": 1,
      "investments": 1,
      "singapore": 1,
      "social": 1,
      "technology": 1
    },
    "scope": "Five reviewed current signals, one per category. Fast Retailing is the sole frozen directional investment call. USD/JPY remained unissued because no fresh reference row could be verified; its stale draft is excluded.",
    "source_coverage_limit": "The described evidence and reading scopes are bounded; no claim that every stored Drive item or every word was reviewed.",
    "first_publication": "Null until successful native Sites deployment; the deployment receipt is retained separately."
  },
  "editorial_standard": "Secondary 3 English; source facts, OTR interpretation, opposing evidence and uncertainties remain distinct.",
  "_public_delivery_projection": {
    "projection_id": "otr-current-method-locator-20261010",
    "original_record_sha256": "384a2ea336f275b0142ec21ccbc7ee4a07f7fefcd4c3924e60a8cc5574f27084",
    "original_public_url": "/data/signals/releases/OTR-SIGNALS-20261009-052420Z-FORCE-1.json",
    "notice": "Retired Method locators point to the current Method page. Signal content, calls and outcomes are unchanged."
  }
}