The numbers are stated judgments. The record began on 15 October 2026 with starting confidences that a model set as the average of five separate readings, from its general knowledge and up to ten developments for each assessment first reported in the three weeks before, after a second model had checked the developments the readings relied on, and a published rule has made every change since. They are not measured probabilities. The question and the rule are fixed before the record begins, and each change shows its evidence and its reasons. The rule and what is not claimed are on the method page.

This record corrects the first record of the same question, Microsoft, which began on 13 October 2026 and continues unchanged under the rules it began with. What changed, and why is on this record’s method page.

The alternative

The cost of the AI capacity Microsoft builds rises faster than the revenue that capacity brings, so that by the end of 2027 Microsoft's operating profit stops growing or Microsoft cuts back its capital spending.

32.5% stated confidence, Unlikely (20–45%). Starting point on the record’s first day: Unlikely (20–45%), 32.5 per cent, the average of five readings, all five of Unlikely. Attention level: For information. Trend: Steady. Activation: Dormant. No recent change has moved toward it.

Stated confidence in the one daily state so far: 15 October 2026, 32.5 per cent. A chart is drawn once there are 3 daily states.

Key judgment

The judgment as stated before the record began

This is the leading alternative to the main assessment. Microsoft is spending on new capacity at a record rate, and roughly two thirds of that spending goes on chips and servers that are written off over several years, so the cost arrives quickly while the revenue builds over time. If AI does not pay for itself at this scale, the first signs would appear in costs: a falling gross margin on the Microsoft Cloud, free cash flow shrinking as spending climbs, and operating profit growing more slowly than revenue. Commitments made years ahead, including data centre leases not yet started, would make those costs slow to cut. Microsoft would then face a choice between slower profit growth and a slower buildout.

Starting point

How the record started this assessment

On 15 October 2026, before the record began, a model read the 8 developments below five separate times, first reported in the three weeks before and linked to this assessment's causal factors or to its rivals', and chose a term each time. A second model, from a different family, checked each development a reading relied on, disputed 1 development, and the five readings were made again without it. The record started the assessment at the average of the five final terms, taken in log-odds: 32.5 per cent, Unlikely (20–45%). Every reading and every check is kept in the first day's record.

The five final readings, in order: Unlikely, Unlikely, Unlikely, Unlikely, Unlikely. Their average, taken in log-odds, is -0.73, a stated confidence of 32.5 per cent. The readings were made by Claude Sonnet 4.6 (Anthropic) and checked by Gemini 4 Argon (Google).

Factors named above: M2 (Demand for capacity running ahead of supply), M3 (What businesses pay for AI), M4 (A falling cost for each unit of AI work), C1 (Cloud gross margin falling as AI costs rise), C3 (Higher prices for chips, memory and power), C4 (AI model developers paying less, later or elsewhere), C5 (Operating profit growing alongside spending) and C6 (Projects slowed, paused or dropped for demand or returns).

The developments shown

1. First reported 14 October 2026, 1 independent publisher. Linked to a rival's causal factors.
“Microsoft Disputes Azure 20% Cost-Cut Report as Maia 300 AI Expansion Looms” · windowsforum.com · 14 October 2026 · Open the report · archived copy
First round: relied on by 3 readings as counting against it. Second round: relied on by 4 readings as counting against it.
- Check of its use as counting against the assessment: Upheld by the second model, run on Gemini 4 Argon (Google).
  Its reason, as the model wrote it: Report 1 confirms that Microsoft denied a report of an Azure 20% cost-cutting directive while planning an AI expansion with its own Maia 300 chips to manage infrastructure costs. Both refusing to cut back spending and deploying in-house chips to manage infrastructure costs directly count against the assessment that rising costs will force Microsoft to cut back its capital spending or suffer stagnant profits. This directly supports the reading's reliance on this development against the assessment.
  - Report 1, quoted: “Microsoft Disputes Azure 20% Cost-Cut Report as Maia 300 AI Expansion Looms”
  - Report 1, quoted: “The report describes Microsoft’s denial of an Azure cost-cutting directive alongside plans to deploy Maia chips for Copilot and other AI workloads, amid pressure to manage infrastructure costs.”
2. First reported 13 October 2026, 1 independent publisher. Linked to a rival's causal factors.
“Microsoft now has 3 generations of its own AI chips. Nvidia is still the chip stock to buy.” · finance.yahoo.com · 13 October 2026 · Open the report · archived copy
First round: relied on by 4 readings as counting against it. Second round: relied on by 5 readings as counting against it.
- Check of its use as counting against the assessment: Upheld by the second model, run on Gemini 4 Argon (Google).
  Its reason, as the model wrote it: Report 1 states that Microsoft now has three generations of its own AI chips and that the Maia 300 could help shift more inference workloads to its own silicon. Developing and shifting workloads to in-house chips supports a falling cost per unit of AI work (Factor M4) by reducing reliance on expensive third-party accelerators. Because a stronger Factor M4 supports the main assessment, it properly counts against the opposing 'if_wrong' assessment.
  - Report 1, quoted: “Microsoft now has 3 generations of its own AI chips.”
  - Report 1, quoted: “Maia 300 could help Microsoft shift more inference workloads to its own chips”
3. First reported 13 October 2026, 1 independent publisher. Linked to a rival's causal factors.
“Microsoft unveils Maia 300 chip, plans gigawatt-scale AI buildout” · en.sedaily.com · 13 October 2026 · Open the report · archived copy
First round: relied on by 3 readings as counting against it. Removed from the second round, because the second model disputed it.
- Check of its use as counting against the assessment: Disputed by the second model, so the second round was read without it, run on Gemini 4 Argon (Google).
  Its reason, as the model wrote it: The reading claims that this development shows Microsoft building its own chips specifically to reduce unit costs, linking it to factor M4 (a falling cost for each unit of AI work). However, the report only states that Microsoft unveiled its Maia 300 chip and plans a large-scale AI buildout, without stating anything about unit costs, cost reductions, or chip efficiency.
  Its ground: the reports do not state the development the reading relies on.
  - Report 1, quoted: “Microsoft unveils Maia 300 chip, plans gigawatt-scale AI buildout”
  - Report 1, quoted: “Microsoft announced its Maia 300 AI accelerator and plans to begin deployment in 2027, advancing its strategy to build large-scale AI infrastructure using custom silicon.”
4. First reported 12 October 2026, 1 independent publisher. Linked to this assessment's own causal factors.
“Intel Accelerates Open Infrastructure for the Agentic AI Era” · finance.yahoo.com · 12 October 2026 · Open the report · archived copy
First round: relied on by no reading. Second round: relied on by no reading.
No reading relied on it, so it was not checked.
5. First reported 12 October 2026, 1 independent publisher. Linked to a rival's causal factors.
“d-Matrix Announces Squadron Compute Clusters for AI Inference at Data Center Scale” · finance.yahoo.com · 12 October 2026 · Open the report · archived copy
First round: relied on by no reading. Second round: relied on by no reading.
No reading relied on it, so it was not checked.
6. First reported 12 October 2026, 1 independent publisher. Linked to a rival's causal factors.
“Microsoft Needs Azure to Keep Growing Faster Than 40% When It Reports on Oct. 28” · finance.yahoo.com · 12 October 2026 · Open the report · archived copy
First round: relied on by 1 reading as counting against it. Second round: relied on by 2 readings as counting against it.
- Check of its use as counting against the assessment: Upheld by the second model, run on Gemini 4 Argon (Google).
  Its reason, as the model wrote it: Report 1 states that Microsoft faces "persistent demand exceeding available capacity, making data-center buildout a key constraint on growth" ahead of expectations for Azure growth above 40%. This directly strengthens factor M2 (demand for capacity running ahead of supply), which supports the main assessment that revenue will cover capacity costs and therefore counts against the if_wrong assessment.
  - Report 1, quoted: “Microsoft Needs Azure to Keep Growing Faster Than 40% When It Reports on Oct. 28”
  - Report 1, quoted: “persistent demand exceeding available capacity, making data-center buildout a key constraint on growth.”
7. First reported 1 October 2026, 1 independent publisher. Linked to this assessment's own causal factors.
“Microsoft and OpenAI Rewrite Their AI Alliance: Freedom, Caps and a Looser Bond” · webpronews.com · 1 October 2026 · Open the report · archived copy
First round: relied on by 5 readings as support for the assessment. Second round: relied on by 5 readings as support for the assessment.
- Check of its use as support for the assessment: Upheld by the second model, run on Gemini 4 Argon (Google).
  Its reason, as the model wrote it: The report explicitly states that Microsoft and OpenAI amended their partnership, 'ending exclusivity' and giving 'OpenAI freedom to sell across clouds'. This directly aligns with factor C4, which concerns AI model developers renegotiating commitments or moving work to other cloud providers, thereby supporting the assessment.
  - Report 1, quoted: “Microsoft and OpenAI have amended their landmark partnership twice since late 2025, ending exclusivity, capping revenue shares and removing the AGI trigger.”
  - Report 1, quoted: “The changes give OpenAI freedom to sell across clouds while Microsoft gains predictability and reduced obligations.”
8. First reported 29 September 2026, 1 independent publisher. Linked to this assessment's own causal factors.
“TSMC is raising 3nm chip prices up to 15% and nobody can say no - Startup Fortune” · startupfortune.com · 29 September 2026 · Open the report · archived copy
First round: relied on by 5 readings as support for the assessment. Second round: relied on by 5 readings as support for the assessment.
- Check of its use as support for the assessment: Upheld by the second model, run on Gemini 4 Argon (Google).
  Its reason, as the model wrote it: The report explicitly states that TSMC is raising 3nm chip prices by up to 15% for leading-edge AI chips. This directly supports factor C3 (Higher prices for chips, memory and power) and bears against factor M4, both of which support the if_wrong assessment that the cost of AI capacity rises faster than revenue. The development is new within the window and does not equally favour any of the listed alternatives.
  - Report 1, quoted: “TSMC is raising 3nm chip prices up to 15% and nobody can say no”
  - Report 1, quoted: “TSMC makes essentially every leading-edge chip that matters in AI right now, and it just told its biggest customers to pay more for the privilege.”

The readings, and their reasons

The first round, before the check

Reading 1: Unlikely (20–45%), from 8 developments shown. It relied on development 8 as support for the assessment, development 7 as support for the assessment, development 2 as counting against the assessment, development 1 as counting against the assessment.
Its reason, as the model wrote it: Development 8 shows TSMC raising 3nm chip prices up to 15%, which supports factor C3 by raising input costs. Development 7 reports Microsoft and OpenAI rewriting their alliance with caps and a looser bond, which supports C4 by suggesting OpenAI's committed Azure consumption may be constrained. However, development 2 linked through the rival shows Microsoft building its own chips to reduce dependence on expensive third-party silicon, which weakens C3 over time. Development 1 linked through the rival shows Microsoft disputing a demand-weakness narrative, which weakens C6. The prior record of growing operating income and management guidance toward continued profit growth means the base case already ran against this assessment before these developments.
Reading 2: Unlikely (20–45%), from 8 developments shown. It relied on development 8 as support for the assessment, development 7 as support for the assessment, development 3 as counting against the assessment, development 2 as counting against the assessment.
Its reason, as the model wrote it: Development 8 reports TSMC raising 3nm chip prices up to 15 percent, which supports C3 by raising the cost of capacity components. Development 7 reports Microsoft and OpenAI rewriting their alliance with caps and a looser bond, which supports C4 by raising the possibility that OpenAI reduces or shifts its Azure commitments. However, developments 3 and 2, linked through the rival, show Microsoft building its own chips specifically to reduce unit costs, supporting the alternative CX2, and development 6 shows Azure demand remaining strong. The baseline before these developments was Microsoft reporting consistently growing operating profit and no cutbacks attributable to weak demand, which is the condition that most directly weakens this assessment.
Reading 3: Unlikely (20–45%), from 8 developments shown. It relied on development 7 as support for the assessment, development 8 as support for the assessment, development 1 as counting against the assessment, development 3 as counting against the assessment.
Its reason, as the model wrote it: Development 7 on OpenAI and Microsoft rewriting their alliance and loosening their bond supports factor C4, as it suggests Azure commitments from its most important model developer may be reduced or capped. Development 8 reports TSMC raising 3nm chip prices up to 15 percent, directly supporting factor C3 on rising component costs. However, developments 1 and 3, linked through the rival assessment, show Microsoft disputing cost-cut reports and launching its own Maia 300 chip at scale, which count against this assessment by showing cost efficiencies and continued demand. The balance of evidence points more toward costs being managed than spiraling ahead of revenue, making a profit stop or spending cutback by 2027 unlikely but not remote.
Reading 4: Unlikely (20–45%), from 8 developments shown. It relied on development 8 as support for the assessment, development 7 as support for the assessment, development 2 as counting against the assessment, development 3 as counting against the assessment, development 6 as counting against the assessment.
Its reason, as the model wrote it: Development 8 reports TSMC raising 3nm prices up to 15 percent, which supports C3 on higher component costs. Development 7 reports Microsoft and OpenAI renegotiating their alliance with caps and a looser bond, which could support C4 if OpenAI reduces Azure commitments. However developments 2 and 3 show Microsoft investing in proprietary chips that lower per-unit costs over time, and development 6 points to analyst expectations of Azure growth above 40 percent, both of which support CX2 and count against this assessment. The overall balance of evidence, combined with Microsoft's historically growing operating profit, makes the cost-overrun scenario unlikely rather than even.
Reading 5: Unlikely (20–45%), from 8 developments shown. It relied on development 8 as support for the assessment, development 7 as support for the assessment, development 2 as counting against the assessment, development 1 as counting against the assessment.
Its reason, as the model wrote it: Development 8 reports TSMC is raising 3nm chip prices up to 15 per cent, which supports factor C3 by raising the input cost of AI capacity. Development 7 reports Microsoft and OpenAI rewrote their alliance with looser commitments and caps, which supports C4 by suggesting OpenAI may consume less Azure capacity than previously contracted. However developments 2 and 3, linked through the rival assessment, show Microsoft building its own chips to cut unit costs, which supports alternative CX2 and weakens C3's net effect. Development 1, also linked through the rival, shows Microsoft disputing cost-cut reports rather than announcing demand shortfalls, undercutting C6. The developments are few and the prior record of growing operating profit alongside rising capex weighs against this assessment.

The second round, after the check, which set the start

Reading 1: Unlikely (20–45%), from 7 developments shown. It relied on development 8 as support for the assessment, development 7 as support for the assessment, development 2 as counting against the assessment, development 6 as counting against the assessment.
Its reason, as the model wrote it: Development 8, the TSMC 3nm price increase of up to 15 percent, supports higher input costs and counts in favor of this assessment through factor C3. Development 7 on the looser Microsoft and OpenAI alliance introduces some risk of a major customer paying less or later, supporting factor C4. However development 2, linked through the rival, describes Microsoft deploying three generations of its own AI chips, which points toward falling unit costs that would undercut this assessment. Development 6, also linked through the rival, reflects analyst expectations of Azure growing faster than 40 percent, which would mean revenue is keeping pace with costs. On balance the evidence points more toward the rival assessment holding, making this alternative unlikely rather than even-chance.
Reading 2: Unlikely (20–45%), from 7 developments shown. It relied on development 8 as support for the assessment, development 7 as support for the assessment, development 2 as counting against the assessment, development 1 as counting against the assessment.
Its reason, as the model wrote it: Development 8 reports TSMC raising 3nm chip prices up to 15 percent, supporting factor C3 that input costs are rising. Development 7 reports Microsoft and OpenAI rewriting their alliance with caps and a looser bond, supporting factor C4 that a key AI model developer may commit less capacity to Azure. However, developments linked through the rival assessment show Microsoft building its own chips to cut unit costs (developments 2 and 1 via main), which directly supports alternative CX2 and weakens this assessment. Prior widely known evidence shows Microsoft's operating profit and cloud margins have continued to grow alongside rising capex, which supports factor C5 and counts against this assessment. The balance of evidence does not support the scenario where costs outrun revenue by 2027.
Reading 3: Unlikely (20–45%), from 7 developments shown. It relied on development 8 as support for the assessment, development 7 as support for the assessment, development 1 as counting against the assessment, development 2 as counting against the assessment.
Its reason, as the model wrote it: Development 8, TSMC raising 3nm chip prices up to 15 percent, supports C3 by raising the cost of capacity components. Development 7, the restructured Microsoft and OpenAI alliance with caps and a looser bond, supports C4 as it suggests some reduction in the depth of OpenAI's Azure commitment. Development 1, linked from the rival assessment, shows Microsoft disputing a reported Azure cost cut and expanding with Maia 300, which counts against this assessment by suggesting continued strong investment backed by demand. Development 2, also linked from the rival, showing three generations of Microsoft's own chips, counts against C3 by indicating Microsoft is reducing reliance on expensive third-party chips. The baseline of Microsoft's consistent operating profit growth makes the if_wrong scenario the less supported outcome at this point.
Reading 4: Unlikely (20–45%), from 7 developments shown. It relied on development 8 as support for the assessment, development 7 as support for the assessment, development 2 as counting against the assessment, development 1 as counting against the assessment, development 6 as counting against the assessment.
Its reason, as the model wrote it: Development 8 reports TSMC raising 3nm chip prices up to 15 percent, supporting factor C3 on higher component prices. Development 7 on the looser OpenAI bond with caps supports factor C4 on AI model developers potentially paying less or later. However developments 2 and 1, linked through the rival assessment, show Microsoft actively deploying its own Maia chips and disputing reports of Azure cost cuts, both pointing against C1 and C3 by suggesting unit costs are being managed. Development 6, also linked through the rival, reflects strong analyst expectations for Azure revenue growth above 40 percent, which would support C5 and weaken this assessment. The balance of evidence, together with prior knowledge of Microsoft's growing operating profit and continued capital spending growth, makes the scenario of profit stalling or spending being cut back unlikely rather than even odds.
Reading 5: Unlikely (20–45%), from 7 developments shown. It relied on development 7 as support for the assessment, development 8 as support for the assessment, development 2 as counting against the assessment, development 1 as counting against the assessment.
Its reason, as the model wrote it: Development 7 reports that Microsoft and OpenAI have rewritten their alliance with caps and a looser bond, which supports factor C4 by suggesting some reduction in OpenAI's committed Azure capacity. Development 8 reports TSMC raising 3nm chip prices up to 15 percent, supporting factor C3. However development 2, linked through the rival, shows Microsoft building its own AI chips across three generations, which supports the rival's factor M4 and weakens C3 and C4 for this assessment. Development 1, also linked through the rival, shows Microsoft disputing a cost-cut report while expanding Maia 300, suggesting pricing holds and demand remains strong, which supports rival factor M3 and undercuts this assessment. On balance the evidence leans against this alternative.

Readings made before this one

No starting point was read before this one, as the first day records.

Uncertainty

Causes of uncertainty

From July 2026 Microsoft treats its data centre buildings as lasting 25 years in place of 15, which slightly lowers depreciation and moves more of its new data centre leases out of the capital spending it reports, without changing what is built.
The gross margin on the Microsoft Cloud mixes AI with older cloud and software business, so a fall can reflect a change in the mix as much as the cost of AI.
A growing part of Microsoft's AI capacity is rented from specialized providers under contracts whose terms are only partly public.

What would change it

What would change the judgment

Microsoft's operating profit falling from a year earlier while its capital spending keeps rising.
Microsoft lowering its capital spending outlook and citing demand or returns.
An AI model developer reducing, delaying or renegotiating a large commitment for Azure capacity.

Causal factors

The causal factors, and which way each one cuts

Factor	Which way it cuts	What evidence looks like	Last moved
C1. Cloud gross margin falling as AI costs rise The gross margin on the Microsoft Cloud, which Microsoft reports each quarter, falling because the cost of AI capacity, mainly depreciation and running costs, grows faster than the revenue it brings. The Microsoft Cloud is Microsoft's measure that combines Azure, its business Microsoft 365 cloud services and its industry cloud services.	Supports. A stronger factor supports the assessment.	Microsoft reports a lower gross margin percentage for the Microsoft Cloud and links it to spending on AI capacity. A quarterly filing shows depreciation growing faster than revenue. Microsoft reports a higher cloud gross margin and cites efficiency, which bears on the factor in the other direction.	Not yet
C2. Free cash flow squeezed by spending The cash Microsoft's operations generate, less what it spends on property and equipment, falling as spending rises faster than the cash its revenue brings in.	Supports. A stronger factor supports the assessment.	An earnings release shows free cash flow lower than a year earlier because of higher capital spending. Microsoft relies more on leases or borrowing to pay for new capacity. Microsoft reports a quarter in which its spending on property and equipment exceeded the cash its operations generated.	Not yet
C3. Higher prices for chips, memory and power Rising prices for the components and power that AI capacity needs, which raise the cost of each unit of capacity without raising the revenue it brings.	Supports. A stronger factor supports the assessment.	Microsoft links part of a rise in its capital spending to higher prices for components. Makers of memory chips or AI accelerators raise their prices. Power contracts for new data centres are signed at higher prices.	Not yet
C4. AI model developers paying less, later or elsewhere AI model developers that have committed to Azure capacity reducing, delaying or renegotiating those commitments, or moving work to other providers, which leaves capacity built for them earning less than planned.	Supports. A stronger factor supports the assessment.	Microsoft reports a reduction or renegotiation of a large commitment from an AI model developer. An AI model developer reports difficulty raising the money to pay for computing it has contracted. An AI model developer moves work from Azure to another cloud provider.	Not yet
C5. Operating profit growing alongside spending Microsoft's operating profit, its operating income, growing year over year while its capital spending rises. This shows revenue covering the rising cost, which weakens this assessment.	Weakens. A stronger factor weakens the assessment.	An earnings release shows operating income up from a year earlier while capital spending rises. Microsoft keeps its outlook for operating margin close to the previous year's.	Not yet
C6. Projects slowed, paused or dropped for demand or returns Microsoft slowing, pausing or cancelling data centre projects, or walking away from leases and contracts for rented capacity, where the reason given is demand or returns. A change Microsoft attributes to accounting or to the timing of deliveries does not count.	Supports. A stronger factor supports the assessment.	Microsoft lowers its capital spending outlook and cites demand or returns. Microsoft is reported to have walked away from data centre leases or contracts for rented capacity. Microsoft pauses a data centre project and cites demand.	Not yet

Assumptions

What the assessment assumes, and what would break it

CA1. Microsoft's capacity catches up with the demand for it before the end of 2027.
If this fails, the assessment fails.
Invalidated if, on its earnings call for the quarter ending 30 September 2027, Microsoft says that customer demand still exceeds the capacity it has available, or that it remains short of capacity. If Microsoft makes no statement about its capacity on that call, the assumption is reviewed rather than invalidated.
Source: Microsoft Investor Relations, transcript of the earnings call for the fourth quarter of fiscal year 2026, which states that customer demand continues to exceed available capacity, Microsoft Investor Relations, transcript of the earnings call for the third quarter of fiscal year 2026, which expects capacity to remain constrained at least through 2026. The criterion’s fingerprint was fixed on 15 October 2026 and is part of the record’s first day.
CA2. Microsoft paces its capital spending to the returns it can see.
If this fails, the assessment weakens.
Invalidated if Microsoft's quarterly payments for property and equipment rise year over year in two consecutive quarters in which its operating income falls year over year, as filed with the SEC in its structured data format, XBRL (concepts PaymentsToAcquirePropertyPlantAndEquipment, with year-to-date figures differenced into quarters and the fourth quarter taken as the annual figure less nine months, and OperatingIncomeLoss). If Microsoft stops filing either figure in this form, the assumption is reviewed rather than invalidated.
Source: SEC, XBRL data for Microsoft, PaymentsToAcquirePropertyPlantAndEquipment, SEC, XBRL data for Microsoft, OperatingIncomeLoss. The criterion’s fingerprint was fixed on 15 October 2026 and is part of the record’s first day.

Other explanations

The rival explanations

Evidence moves the assessment only when it bears differently on the assessment than on at least one of these. Evidence that fits them equally carries no weight.

CX1. Margins fall because Microsoft builds ahead of business it has already signed, and they recover as that business arrives as revenue.
No development was recorded on this assessment in the last 7 days.
Favoured by:
- The cloud gross margin falls while revenue under contract and not yet recognized keeps rising.
- Microsoft says new capacity is committed to customers before it is built.
Ruled out by:
- The cloud gross margin keeps falling after the contracted business begins to arrive as revenue.
CX2. Spending slows because capacity becomes cheaper to build and run, while revenue from AI keeps growing.
No development was recorded on this assessment in the last 7 days.
Favoured by:
- Microsoft reports a lower cost for each unit of AI work it delivers.
- Growth in capital spending slows while Azure keeps growing quickly.
Ruled out by:
- Capital spending and Azure growth slow together.
CX3. Spending moves into leases and rented capacity, so Microsoft's own capital spending understates the cost of its AI capacity.
No development was recorded on this assessment in the last 7 days.
Favoured by:
- Microsoft signs large contracts to rent computing capacity from specialized providers.
- Leases not yet started grow while capital spending levels off.
Ruled out by:
- Leases and contracts for rented capacity shrink along with capital spending.

A development is recorded when the rule applies it to the assessment or sets it aside. Each count comes from the readings sealed with the changes, and a development set aside as fitting every alternative equally tells no alternative apart.

Evidence

Evidence behind changes in the last 30 days

Each item is a report or data series cited by a sealed change on this assessment. The update loop reads headlines and summaries, and no summary is shown as the evidence.

No evidence has been cited in the last 30 days.

Considered, set aside

Evidence considered and set aside

Developments the update loop read in the last 30 days and set aside because they fitted this assessment and each of its rival explanations equally. Under the rule such evidence carries no weight, so none of it moved anything.

Nothing on this assessment was set aside in the last 30 days.

Changes

Changes to this assessment

No change to this assessment yet.

The other assessments

The rest of the judgment

The question’s text on this page is as sealed on the record’s first day. Fingerprint . Fingerprint pending. Records are fingerprinted each day at 23:59 UTC.