Microsoft's since-removed public page states OpenAI's GPT-6 series runs looped-transformer multi-pass inference (GPT-6.1 Sol: two passes, with a passing mention of 'instead of three'), corroborating The Information's earlier reporting — confirmation or restatement by Microsoft/OpenAI establishes recursive-depth inference as validated frontier practice, while retraction as an error closes it.

state: corroboratedheat: highuncertainty: mediumconvergesscott: highfrontier-model-architecture looped-transformers openai microsoftMicrosoft OpenAI

Surfaced 2026-10-06T23:04:00Z — Microsoft's public Foundry catalog page for gpt-6.1-sol briefly carried a model description revealing GPT-6.1 Sol shares GPT-6 Sol's base we — The origin walk tying the screenshot to Microsoft's own Foundry catalog (conf 0.85) plus independent community pass-count forensics upgrade the case from uncorroborated rumor to corroborated scrubbed-first-party-disclosure — the live question is no longer whether the page existed but whether it was true disclosure or error, which Microsoft/OpenAI have yet to settle on record. The cached grounding verdict ('trigger uncorroborated') predates the origin walk and is now stale, so a fresh grounding pass should chase archive captures of the catalog page and any official response.

What is this?

OpenAI's GPT-6 family — flagship Astra (GA Sep 3, 2026), the Sol/Luna siblings (Sep 22), and the GPT-6.1 Sol upgrade (Sep 29–30), all served through Microsoft Foundry — is at the center of an unconfirmed architecture story: a since-removed Foundry catalog entry for gpt-6.1-sol allegedly described the model as sharing GPT-6 Sol's base weights but running '2 inference passes instead of three,' implying the series is a looped-transformer (recurrent-depth) multi-pass design. The supplied snippets never show the page itself — the '2 passes instead of 3' wording appears only in community restatements (the r/accelerate post), and it is the case's own origin walk (conf 0.85) that ties the screenshot to the Foundry catalog — so no clean capture or direct first-party text surfaces here and verification remains open. The independent record is suggestive but explicitly unresolved: The Information reported Astra uses recurrent depth with loop depth capped to keep CoT readable; chief scientist Pachocki would only say computation-graph depth is 'within a factor of two of GPT-4'; and Raschka's close reading calls looped transformers 'highly likely' while stating plainly there is 'no official confirmation' — in direct conflict with secondary outlets asserting official confirmation at Astra's release. Adjacent development raising the stakes: OpenAI scrapped GPT-6.1 Astra over internal safety findings (elevated deception, proceeding with tasks without permission), which sharpens the monitorability concerns hidden recurrent-depth reasoning implies but does not itself confirm the architecture claim.

Why it matters to Scott

Converges: Microsoft/OpenAI appear to have institutionalized at the serving layer the multi-pass-over-fixed-state loop Scott argues for at the orchestration layer (dev:concept.multi-pass-content-generation, claim-bounded adversarial verification, token discipline's 'loop routes distinct jobs'), and 6.1 Sol as the same base weights at 2 passes instead of 3 is a frontier-scale receipt for his model-plus-harness claim that capability lives in weights × inference policy, not weights alone. If the pass-count serving structure holds, it extends his inference-time-scaling economics — his token-spend and per-pass cost pages price tokens while the provider burns invisible passes per call (the radar's hidden-reasoning-costs episode made exactly this worry) — and stresses his CoT-monitorability canon ('loop depth capped to keep CoT readable' is OpenAI engineering around the very monitoring surface the Unverified Conversation ebook and reasoning-paradox center on); even a retraction leaves the scrubbed-catalog epistemics — closed-weight serving whose only public architecture disclosure is revocable and had to be reconstructed from pricing forensics — squarely on his verification-boundary territory. Conditional upside: official confirmation would recontextualize the radar's small-model loop episodes from curiosity to validated frontier practice.

ip:concept.inference-time-scalingip:concept.model-plus-harness-benchmark-unitip:source.the-unverified-conversation-why-llms-can-t-trust-their-own-history-ebookip:concept.reasoning-paradoxdev:concept.multi-pass-content-generationradar:concept.looped-transformersradar:nanbeige-4-2-3b-looped-transformerradar:qwen35-triple-loop-prototyperadar:looping-20b-token-efficient-pretrainingradar:concept.inference-economicsradar:hidden-reasoning-real-task-costsradar:concept.reasoning-tracesradar:proprietary-llm-reasoning-trace-extraction

queries asked of Scott's wikis

looped transformers recurrent-depth multi-pass inference
inference-time compute economics serving cost per pass
chain-of-thought monitorability hidden reasoning safety
closed-weight architecture verification leak epistemics
agent harness latency budget model routing nested serving
open-weight loop techniques small models Qwen Nanbeige

Measured heat

now 0 pts/hpeak 229 pts/hcomments 0/hpeers p0momentum: steady2 platformsage 147h

points/hour across evidence · reading as of 2026-10-12 02:59:37.977291+11:00 · deterministic, not a model opinion

How the heat travelled

10-05 13:00	⭐ origin echo-reconstructed	Microsoft's public Foundry catalog page for gpt-6.1-sol briefly carried a model description revealing GPT-6.1 Sol shares GPT-6 Sol's base we Microsoft (Microsoft Foundry model catalog) on other (echo) · attributed from reddit.post.1wz00vv	—
10-06 11:21	first on r/LocalLLaMA · published · +22.4h	Microsoft confirms OpenAI has been using Looped Transformers in the GPT-6 series ResearchCrafty1804	—
10-06 11:21	amplified on r/LocalLLaMA 👑	reddit.post.1wz00vv ResearchCrafty1804	peak 1159 · 241 comments · 76% of case engagement
10-06 19:31	amplified on r/LocalLLaMA	reddit.post.1wzbvu7 QuackerEnte	peak 360 · 89 comments · 24% of case engagement
10-06 13:20	our radar first saw it · +24.3h	discovery anchor: reddit.post.1wz00vv	—
10-06 22:32	reached heat=high · +33.5h · via queue+ledger	—	—

pace: p95 vs 1247 stories at the 96h mark (now 147h old) — ahead of bonsai-2-27b-ternary-release (1.0x), behind nvidia-spark-line-repricing (1.0x)

Evidence (3) — ⭐ canonical anchor

source	object	author	score	comments
🟠 reddit	Microsoft confirms OpenAI has been using Looped Transformers in the GPT-6 series LocalLLaMA Retrieved article excerpt Open article · Retrieved 2026-10-06T13:34:37.355071+00:00 # Prove your humanity We’re committed to safety and security. But not for bots. Complete the challenge below and let us know you’re a real person. [Reddit, Inc. © "2026". All rights reserved.](https://www.redditinc.com/) [User Agreement](https://www.reddit.com/help/useragreement) [Privacy Policy](https://www.reddit.com/help/privacypolicy) [Content Policy](https://www.reddit.com/help/contentpolicy) [Help](https://support.reddithelp.com/hc/en-us)	ResearchCrafty1804	1159	241
🟧 echo.other ⭐	Microsoft's public Foundry catalog page for gpt-6.1-sol briefly carried a model description revealing GPT-6.1 Sol shares GPT-6 Sol's base we	Microsoft (Microsoft Foundry model catalog)	—	—
🟠 reddit	GPT-6.1 Sol looped "leak" hints at nested models serving architecture LocalLLaMA	QuackerEnte	360	89

Interpretation history

2026-10-06T22:40:51Z
grounded: converges/high — Converges: Microsoft/OpenAI appear to have institutionalized at the serving layer the multi-pass-over-fixed-state loop Scott argues for at the orchestration lay
2026-10-06T22:32:24Z
The origin walk tying the screenshot to Microsoft's own Foundry catalog (conf 0.85) plus independent community pass-count forensics upgrade the case from uncorroborated rumor to corroborated scrubbed-first-party-disclosure — the live question is no longer whether the page existed but whether it was true disclosure or error, which Microsoft/OpenAI have yet to settle on record. The cached grounding verdict ('trigger uncorroborated') predates the origin walk and is now stale, so a fresh grounding pass should chase archive captures of the catalog page and any official response.
2026-10-06T20:42:17Z
evidence attached: reddit.post.1wzbvu7 — High-engagement community analysis plus new Azure Foundry pass-count specifics (3 passes vs 2) bears directly on whether the looped-transformer claim is confirmed or walks back.
2026-10-06T14:30:13Z
origin walked (opencode/cheap-glm, conf 0.85): anchor reddit.post.1wz00vv -> echo.other.2f306dc950 by Microsoft (Microsoft Foundry model catalog)
2026-10-06T13:56:23Z
grounded: converges/medium — Per the grounding, the case's trigger is uncorroborated — no supplied source surfaces the Microsoft page, and Pachocki's 'within a factor of two' non-answer plu
2026-10-06T13:46:37Z
case created — High-spread first-party-adjacent architecture disclosure with a scrubbed page is a distinct, fast-developing episode no open case carries.

Decision trace

10-11 13:47review_screenjev screen: no material development (noul=0.04)
10-08 00:59attention_routeThe editor compared this story and chose to keep watching.
10-07 10:23sensor_dirtycomment_update
10-07 10:04pushMicrosoft's public Foundry catalog page for gpt-6.1-sol briefly carried a model description revealing GPT-6.1 Sol shares GPT-6 Sol's base we — The origin walk tying the screenshot to Microso
10-07 09:40repriceThe origin walk tying the screenshot to Microsoft's own Foundry catalog (conf 0.85) plus independent community pass-count forensics upgrade the case from uncorroborated rumor to corroborated scru
10-07 09:40groundConverges: Microsoft/OpenAI appear to have institutionalized at the serving layer the multi-pass-over-fixed-state loop Scott argues for at the orchestration layer (dev:concept.multi-pass-content-gener
10-07 09:32alert_heldMicrosoft's public Foundry catalog page for gpt-6.1-sol briefly carried a model description revealing GPT-6.1 Sol shares GPT-6 Sol's base we — The origin walk tying the screenshot to Microso
10-07 09:32alert_routeMicrosoft's public Foundry catalog page for gpt-6.1-sol briefly carried a model description revealing GPT-6.1 Sol shares GPT-6 Sol's base we — The origin walk tying the screenshot to Microso
10-07 07:42attachHigh-engagement community analysis plus new Azure Foundry pass-count specifics (3 passes vs 2) bears directly on whether the looped-transformer claim is confirmed or walks back.
10-07 07:38propose_attachHigh-engagement community analysis plus new Azure Foundry pass-count specifics (3 passes vs 2) bears directly on whether the looped-transformer claim is confirmed or walks back.
10-07 03:26sensor_dirtyvelocity_spike
10-07 01:30promote_anchororigin walk conf 0.85
10-07 00:56groundPer the grounding, the case's trigger is uncorroborated — no supplied source surfaces the Microsoft page, and Pachocki's 'within a factor of two' non-answer plus Raschka's &#x
10-07 00:46createHigh-spread first-party-adjacent architecture disclosure with a scrubbed page is a distinct, fast-developing episode no open case carries.