Microsoft Corporation
Control of this organisation’s compute: the terms, the constraints, and what the public record does not show, with every claim carrying the disclosure it came from.
9 control relations on record for Microsoft Corporation — 2 by title, 2 by operation, 5 by contract
Every claim below carries the document it came from, who disclosed it, and the date that disclosure speaks to. Where the record holds nothing, the page states whether the public record was searched and what was searched — an unsearched layer and an empty one are different facts.
Control
Control here means one of three things the substrate keeps apart: holding title to a facility, operating one, or holding capacity by contract. The three are recorded separately because an organisation can hold any one without the others, and a model built on ownership alone cannot see an organisation whose compute is entirely leased.
Receipt
“Microsoft Corp. on Tuesday announced that it has completed construction of its first datacenter facility in the Village of Mount Pleasant”
Construction-completion announcement; ~550 FTEs on-site; second facility under construction adjacent (expected 2028). No MW figure in the document — widely-reported ~2GW-class secondary figures deliberately not used.
@misc{scrutica-ctrl-microsoft-self-microsoft-fairwater-wisconsin-owns-2026-1f8e65,
title = {Press release disclosing Microsoft Corporation owns},
year = {2026},
howpublished = {\url{https://news.microsoft.com/source/2026/06/23/microsoft-completes-construction-on-first-datacenter-facility-in-mount-pleasant-wisconsin/}},
note = {Compiled in the Scrutica control ledger, claim ctrl-microsoft-self-microsoft-fairwater-wisconsin-owns-2026-1f8e65; disclosure dated 2026-06-23}
}Press release disclosing Microsoft Corporation owns (2026). Retrieved via the Scrutica control ledger (claim ctrl-microsoft-self-microsoft-fairwater-wisconsin-owns-2026-1f8e65): https://news.microsoft.com/source/2026/06/23/microsoft-completes-construction-on-first-datacenter-facility-in-mount-pleasant-wisconsin/
Receipt
“We intend to develop our new datacenter campuses in El Mirage and Goodyear, Arizona to be among the most sustainably designed”
2019 forward-looking development statement; the Goodyear campus is independently present in Epoch's frontier catalog today. The 150 MW figure in the same article is the Sun Streams 2 SOLAR plant, not facility draw — excluded. The paired El Mirage campus has no completion evidence located this sweep — no row minted for it (NULL over guess).
@misc{scrutica-ctrl-microsoft-self-microsoft-goodyear-owns-2019-08370f,
title = {Company statement disclosing Microsoft Corporation owns},
year = {2019},
howpublished = {\url{https://blogs.microsoft.com/on-the-issues/2019/07/30/building-world-class-sustainable-datacenters-and-investing-in-solar-power-in-arizona/}},
note = {Compiled in the Scrutica control ledger, claim ctrl-microsoft-self-microsoft-goodyear-owns-2019-08370f; disclosure dated 2019-07-30}
}Company statement disclosing Microsoft Corporation owns (2019). Retrieved via the Scrutica control ledger (claim ctrl-microsoft-self-microsoft-goodyear-owns-2019-08370f): https://blogs.microsoft.com/on-the-issues/2019/07/30/building-world-class-sustainable-datacenters-and-investing-in-solar-power-in-arizona/
Receipt
“The facility is now fully operational, marking a major milestone in the company's ongoing investment in Southeast Wisconsin.”
@misc{scrutica-ctrl-microsoft-self-microsoft-fairwater-wisconsin-operates-2026-55e3d3,
title = {Press release disclosing Microsoft Corporation operates},
year = {2026},
howpublished = {\url{https://news.microsoft.com/source/2026/06/23/microsoft-completes-construction-on-first-datacenter-facility-in-mount-pleasant-wisconsin/}},
note = {Compiled in the Scrutica control ledger, claim ctrl-microsoft-self-microsoft-fairwater-wisconsin-operates-2026-55e3d3; disclosure dated 2026-06-23}
}Press release disclosing Microsoft Corporation operates (2026). Retrieved via the Scrutica control ledger (claim ctrl-microsoft-self-microsoft-fairwater-wisconsin-operates-2026-55e3d3): https://news.microsoft.com/source/2026/06/23/microsoft-completes-construction-on-first-datacenter-facility-in-mount-pleasant-wisconsin/
Receipt
“The new AI datacenter in Atlanta, which began operation in October, is the second in Microsoft's Fairwater family.”
Networked to the Wisconsin site via a dedicated AI WAN ('AI superfactory'). Title row deliberately not minted from this article's weaker ownership language.
@misc{scrutica-ctrl-microsoft-self-microsoft-fairwater-atlanta-operates-2025-8e798d,
title = {Press release disclosing Microsoft Corporation operates},
year = {2025},
howpublished = {\url{https://news.microsoft.com/source/features/ai/from-wisconsin-to-atlanta-microsoft-connects-datacenters-to-build-its-first-ai-superfactory/}},
note = {Compiled in the Scrutica control ledger, claim ctrl-microsoft-self-microsoft-fairwater-atlanta-operates-2025-8e798d; disclosure dated 2025-11-12}
}Press release disclosing Microsoft Corporation operates (2025). Retrieved via the Scrutica control ledger (claim ctrl-microsoft-self-microsoft-fairwater-atlanta-operates-2025-8e798d): https://news.microsoft.com/source/features/ai/from-wisconsin-to-atlanta-microsoft-connects-datacenters-to-build-its-first-ai-superfactory/
Receipt
“We recognized an aggregate of approximately 67% of our revenue from our top customer, Microsoft, for the year ended December 31, 2025. We recognized an aggregate of approximately 77% of our revenue from our top two customers for the year ended December 31, 2024. We recognized an aggregate of approximately 73% of our revenue for the year ended December 31, 2023, from our top three customers. None of our other customers represented 10% or more of our revenue for the year ended December 31, 2025.”
CoreWeave's FY2025 Form 10-K (CIK 1769628, filed 2026-03-02), customer-concentration risk factor, read directly at its canonical sec.gov address — the earlier tier-3 rating reflected a third-party mirror rather than the instrument, and sec.gov is reachable with a declared User-Agent. Org-level: the filing states no capacity or site, so this row evidences the SCALE of Microsoft's contracted position with CoreWeave and nothing narrower. CORRECTION carried by the re-derivation: the mirror asserted Microsoft was 'up from 62% in FY2024', which the filing does not state — its FY2024 figure is 77% from the top TWO customers, a different quantity, and the 62% has no counterpart in the document. Dropped rather than repeated.
@misc{scrutica-ctrl-microsoft-coreweave-org-level-capacityreservation-2026-e840cb,
title = {SEC Form 10-K disclosing Microsoft Corporation capacity reservation with CoreWeave},
year = {2026},
howpublished = {\url{https://www.sec.gov/Archives/edgar/data/1769628/000176962826000104/crwv-20251231.htm}},
note = {Compiled in the Scrutica control ledger, claim ctrl-microsoft-coreweave-org-level-capacity_reservation-2026-e840cb; disclosure dated 2026-03-02}
}SEC Form 10-K disclosing Microsoft Corporation capacity reservation with CoreWeave (2026). Retrieved via the Scrutica control ledger (claim ctrl-microsoft-coreweave-org-level-capacity_reservation-2026-e840cb): https://www.sec.gov/Archives/edgar/data/1769628/000176962826000104/crwv-20251231.htm
Receipt
“a new, dedicated AI factory campus in Abilene, Texas... Supporting large scale AI workloads for Microsoft”
site: Abilene, TX — new 900 MW AI factory campus — Crusoe's own release (fetched). A campus distinct from the Stargate I/Lancium site — combined Crusoe Abilene target ~2.1 GW. 900 MW basis unspecified (sources disagree whether gross generation or IT load; an unverified secondary claimed 2×336 MW IT — excluded). First building targeted mid-2027; onsite power plant included.
@misc{scrutica-ctrl-microsoft-crusoe-org-level-capacityreservation-2026-622bdf,
title = {Press release disclosing Microsoft Corporation capacity reservation with Crusoe},
year = {2026},
howpublished = {\url{https://www.crusoe.ai/resources/newsroom/crusoe-announces-new-900-mw-ai-factory-campus-in-abilene-texas-to-support-microsoft-ai-infrastructure}},
note = {Compiled in the Scrutica control ledger, claim ctrl-microsoft-crusoe-org-level-capacity_reservation-2026-622bdf; disclosure dated 2026-03-27}
}Press release disclosing Microsoft Corporation capacity reservation with Crusoe (2026). Retrieved via the Scrutica control ledger (claim ctrl-microsoft-crusoe-org-level-capacity_reservation-2026-622bdf): https://www.crusoe.ai/resources/newsroom/crusoe-announces-new-900-mw-ai-factory-campus-in-abilene-texas-to-support-microsoft-ai-infrastructure
Receipt
“IREN will deliver large scale GPU clusters accommodated within IREN's liquid cooled data centers under construction at its 750 MW campus located in Childress, Texas.”
site: IREN Childress campus (Horizon 1-4), Childress, TX — $9.7B 5-year contract, 20% prepayment, NVIDIA GB300s, phased through 2026; filed as 8-K same date (sec.gov unfetchable in this environment — cited via IREN's own release). 200 MW critical IT per the release set.
@misc{scrutica-ctrl-microsoft-iren-limited-au-org-level-capacityreservation-2025-688af4,
title = {SEC Form 8-K disclosing Microsoft Corporation capacity reservation with IREN Limited},
year = {2025},
howpublished = {\url{https://iren.com/resources/blog/iren-signs97-billion-agreement-with-microsoft-to-deploy-ai-cloud-infrastructure}},
note = {Compiled in the Scrutica control ledger, claim ctrl-microsoft-iren-limited-au-org-level-capacity_reservation-2025-688af4; disclosure dated 2025-11-03}
}SEC Form 8-K disclosing Microsoft Corporation capacity reservation with IREN Limited (2025). Retrieved via the Scrutica control ledger (claim ctrl-microsoft-iren-limited-au-org-level-capacity_reservation-2025-688af4): https://iren.com/resources/blog/iren-signs97-billion-agreement-with-microsoft-to-deploy-ai-cloud-infrastructure
Receipt
“Lambda to deliver mission-critical AI cloud compute at scale under a multi-year contract.”
'Multibillion-dollar' multi-year agreement, 'tens of thousands' of NVIDIA GPUs (incl. GB300 NVL72) deployed in Lambda's own US data centers, Lambda operating the infrastructure. No MW, dollar figure, or site disclosed. Initial deployment 2026.
@misc{scrutica-ctrl-microsoft-lambda-technologies-org-level-capacityreservation-2025-2ea645,
title = {Press release disclosing Microsoft Corporation capacity reservation with Lambda Technologies},
year = {2025},
howpublished = {\url{https://lambda.ai/blog/lambda-announces-multibillion-dollar-agreement-with-microsoft-to-deploy-ai-infrastructure-powered-by-tens-of-thousands-of-nvidia-gpus}},
note = {Compiled in the Scrutica control ledger, claim ctrl-microsoft-lambda-technologies-org-level-capacity_reservation-2025-2ea645; disclosure dated 2025-11-03}
}Press release disclosing Microsoft Corporation capacity reservation with Lambda Technologies (2025). Retrieved via the Scrutica control ledger (claim ctrl-microsoft-lambda-technologies-org-level-capacity_reservation-2025-2ea645): https://lambda.ai/blog/lambda-announces-multibillion-dollar-agreement-with-microsoft-to-deploy-ai-infrastructure-powered-by-tens-of-thousands-of-nvidia-gpus
Receipt
“Nebius will deliver dedicated capacity to Microsoft from its new data center in Vineland, New Jersey starting later this year.”
site: Nebius Vineland data center, Vineland, NJ — $17.4B (up to $19.4B) 5-year agreement. Facility's planned total is 300 MW (expandable) but the Microsoft-dedicated MW split is undisclosed — capacity null rather than equating the two (E36). Furnished as a 6-K exhibit on EDGAR (tm2525580d1_ex99-1.htm); the §4.28 instrument taxonomy has no sec_6k value, so instrument records the release itself — taxonomy gap routed to the orchestrator.
@misc{scrutica-ctrl-microsoft-nebius-org-level-capacityreservation-2025-7d9220,
title = {Press release disclosing Microsoft Corporation capacity reservation with Nebius},
year = {2025},
howpublished = {\url{https://nebius.com/newsroom/nebius-announces-multi-billion-dollar-agreement-with-microsoft-for-ai-infrastructure}},
note = {Compiled in the Scrutica control ledger, claim ctrl-microsoft-nebius-org-level-capacity_reservation-2025-7d9220; disclosure dated 2025-09-08}
}Press release disclosing Microsoft Corporation capacity reservation with Nebius (2025). Retrieved via the Scrutica control ledger (claim ctrl-microsoft-nebius-org-level-capacity_reservation-2025-7d9220): https://nebius.com/newsroom/nebius-announces-multi-billion-dollar-agreement-with-microsoft-for-ai-infrastructure
None of the disclosures behind those terms states a contract start date, so the figure draws duration and prints the disclosure date rather than placing bars on a calendar. 2 of 2 term-carrying positions are in that state.
Across the 16 organisations carrying control relations in this substrate, 7 hold contractual capacity without a single titled facility on record. That pattern is what the three-way split exists to make visible: an attribution model keyed on ownership records the 7 as holding nothing.
Constraint
What regime the organisation sits under, and whether any export-control designation in the Federal-Register-anchored list held here reaches it. A quiet result is reported as a check with its date rather than left as silence.
The organization record places this company’s headquarters in the United States, on the strength of the company’s own published statements cited there.
No export-control designation is linked to this organization. The cross-reference that would carry such a link resolves 50 organizations to entries on the Federal-Register-anchored lists; this organization is not among them.
The denominator is printed because a zero on its own cannot be told from a check that never ran. The lists themselves last moved on Nov 10, 2025, so a quiet result here reflects the record rather than a stalled feed.
Disclosure posture
What the organisation itself has put on the record with the registries that ask, and which registries reach it at all. Each regime asks a different question of a different population, so each finding carries what that regime counts; nothing here is divided by anything else.
The organization holds legal entity identifier INR2EJN1ERAN0W5ZP974.
Registration of the entity itself in the global LEI system.
Declares a parent that does not consolidate — The organization has declared that a parent exists but does not consolidate it under the applicable accounting standard, so the consolidation regime records no parent even though one exists.
What the registrant itself declared to the LEI registry about its consolidating parent, per parent category.
Registry reason code: NON_CONSOLIDATING · as of Aug 8, 2026 · registry record ↗
60 active consolidation records name this identifier as parent (26 direct, 34 ultimate). 2 of the reporting entities resolve to organizations tracked here — a boundary of this platform’s entity resolution, not of the registry’s records.
Entities holding identifiers of their own that report being consolidated into this organization’s audited accounts. Identifier adoption is uneven by jurisdiction, so this is a lower bound on structure, not a census.
as of Aug 8, 2026 · registry record ↗
The organization files with the SEC (CIK 789019); its Exhibit 21 has not been retrieved into this corpus.
Exhibit 21 lists legal subsidiaries above a materiality threshold — a threshold-bounded list, not a complete structure.
Capacity
Facilities this organisation is linked to in the substrate. Frontier-site capacity figures come from Epoch AI’s data-center catalog and are cited to them per record; where Epoch records who owns the AI hardware at a site, that is rendered as what it is — hardware ownership per Epoch — and not as facility ownership or operation.
| Status | Facilities | Capacity where recorded |
|---|---|---|
| operational | 117 | 1.7 GW across the 23 of 117 with a figure |
| under construction | 1 | no capacity figures recorded |
| announced | 3 | no capacity figures recorded |
The 121 facilities the sums above are drawn from
| Facility | Status | Capacity |
|---|---|---|
| Microsoft Sweden Gävle | announced | not recorded |
| Microsoft Sweden Sandviken | announced | not recorded |
| Microsoft Sweden Staffanstorp | announced | not recorded |
| Microsoft Fairwater Atlanta | operational | 636 MW (est.) |
| Microsoft Fairwater Wisconsin | operational | 369 MW (est.) |
| Microsoft Goodyear | operational | 202 MW (est.) |
| Microsoft Project Osmium | operational | 190 MW (est.) |
| OpenAI/Microsoft Goodyear Arizona | operational | 143 MW (est.) |
| Microsoft SAT40 | operational | 75 MW (est.) |
| Microsoft SAT14 | operational | 47 MW (est.) |
| Microsoft GPT-4 cluster | operational | 21 MW (est.) |
| Microsoft Azure Eagle | operational | 21 MW |
| Azure OpenAI GPT-3 Cluster | operational | 7 MW (est.) |
| Microsoft Azure ND H100 v5 VM | operational | 6 MW |
| Microsoft Azure Meta AI Rental | operational | 5 MW |
| Microsoft Ares/Maia | operational | 2 MW (est.) |
| Microsoft Explorer-WUS3 | operational | 2 MW |
| Microsoft Azure Voyager-EUS2 | operational | 2 MW |
| ND A100 v4 | operational | 2 MW (est.) |
| Microsoft Azure Pioneer-EUS | operational | 1 MW |
| Microsoft Azure Pioneer-SCUS | operational | 1 MW |
| Microsoft Azure Pioneer-WEU | operational | 1 MW |
| Microsoft Azure Pioneer-WUS2 | operational | 1 MW |
| Microsoft Azure Immunity Bio | operational | 819 kW |
| Microsoft Azure ND v2 Largest Stated | operational | 533 kW |
| Microsoft Research Hypercluster | operational | 384 kW |
| AZURE Australia Central | operational | not recorded |
| AZURE Australia Central 2 | operational | not recorded |
| AZURE Australia East | operational | not recorded |
| AZURE Australia Southeast | operational | not recorded |
| AZURE Austria East | operational | not recorded |
| AZURE Belgium Central | operational | not recorded |
| AZURE Brazil South | operational | not recorded |
| AZURE Brazil Southeast | operational | not recorded |
| AZURE Canada Central | operational | not recorded |
| AZURE Canada East | operational | not recorded |
| AZURE Central India | operational | not recorded |
| AZURE Central US | operational | not recorded |
| AZURE Chile Central | operational | not recorded |
| AZURE Denmark East | operational | not recorded |
| AZURE East Asia | operational | not recorded |
| AZURE East US | operational | not recorded |
| AZURE East US 2 | operational | not recorded |
| AZURE France Central | operational | not recorded |
| AZURE France South | operational | not recorded |
| AZURE Germany North | operational | not recorded |
| AZURE Germany West Central | operational | not recorded |
| AZURE Indonesia Central | operational | not recorded |
| AZURE Israel Central | operational | not recorded |
| AZURE Italy North | operational | not recorded |
| AZURE Japan East | operational | not recorded |
| AZURE Japan West | operational | not recorded |
| AZURE Korea Central | operational | not recorded |
| AZURE Korea South | operational | not recorded |
| AZURE Malaysia West | operational | not recorded |
| AZURE Mexico Central | operational | not recorded |
| AZURE New Zealand North | operational | not recorded |
| AZURE North Central US | operational | not recorded |
| AZURE North Europe | operational | not recorded |
| AZURE Norway East | operational | not recorded |
| AZURE Norway West | operational | not recorded |
| AZURE Poland Central | operational | not recorded |
| AZURE Qatar Central | operational | not recorded |
| AZURE South Africa North | operational | not recorded |
| AZURE South Africa West | operational | not recorded |
| AZURE South Central US | operational | not recorded |
| AZURE Southeast Asia | operational | not recorded |
| AZURE South India | operational | not recorded |
| AZURE Spain Central | operational | not recorded |
| AZURE Sweden Central | operational | not recorded |
| AZURE Switzerland North | operational | not recorded |
| AZURE Switzerland West | operational | not recorded |
| AZURE UAE Central | operational | not recorded |
| AZURE UAE North | operational | not recorded |
| AZURE UK South | operational | not recorded |
| AZURE UK West | operational | not recorded |
| AZURE West Central US | operational | not recorded |
| AZURE West Europe | operational | not recorded |
| AZURE West India | operational | not recorded |
| AZURE West US | operational | not recorded |
| AZURE West US 2 | operational | not recorded |
| AZURE West US 3 | operational | not recorded |
| Microsoft Air Gapped Supercomputer | operational | not recorded |
| CYS41 Datacenter | operational | not recorded |
| CYS42 Datacenter | operational | not recorded |
| Microsoft - Azure Datacenter | operational | not recorded |
| Microsoft Data Center 1 | operational | not recorded |
| Microsoft EAT02 | operational | not recorded |
| Microsoft IAD11 | operational | not recorded |
| Microsoft | operational | not recorded |
| Microsoft San Antonio | operational | not recorded |
| Microsoft TRP2 | operational | not recorded |
| Microsoft Columbia Data Center | operational | not recorded |
| AMS05 | operational | not recorded |
| Microsoft DUB03 / DUB04 | operational | not recorded |
| Microsoft DSF | operational | not recorded |
| Microsoft Ireland | operational | not recorded |
| Microsoft Data Center | operational | not recorded |
| Microsoft Data Centre | operational | not recorded |
| PHX-11 | operational | not recorded |
| Microsoft MAD01 | operational | not recorded |
| Microsoft Newport data centre | operational | not recorded |
| CPH01 | operational | not recorded |
| Microsoft MAD02 | operational | not recorded |
| Microsoft MEL11 | operational | not recorded |
| COLO 2 | operational | not recorded |
| Microsoft SYD05 Data Centre | operational | not recorded |
| Microsoft MEL04 | operational | not recorded |
| Microsoft MEL07 | operational | not recorded |
| Microsoft Chile | operational | not recorded |
| AMS06 | operational | not recorded |
| AMS07 | operational | not recorded |
| Microsoft Boydton Data Center | operational | not recorded |
| AMS08 | operational | not recorded |
| AMS09 | operational | not recorded |
| PHX-10 | operational | not recorded |
| Microsoft Datacenter West Europe | operational | not recorded |
| Microsoft Datacenter | operational | not recorded |
| AMS11 | operational | not recorded |
| AMS12 | operational | not recorded |
| Crusoe Abilene Expansion | under construction | not recorded |
7 of the 121 linked facilities are in Epoch’s frontier catalog, carrying 1.5 GW between them. Sums cover only the facilities with a recorded figure; the count of those is printed beside each row of the table above, because a megawatt total whose denominator is invisible reads as a census when it is a partial sum.
Supply
This layer publishes what is known about the completeness of the supply picture, not the picture itself. Some supply records here were established with reference to subscription corporate-data sources that cannot be republished, so what renders is the epistemic state — position in a distribution, a corroboration class, whether a contradiction was found — and never a relationship, a counterparty, or a count from those sources.
Some records behind this layer were established with reference to subscription corporate-data sources that cannot be republished. What renders here is the epistemic state — position in a distribution, a corroboration class, whether a contradiction was found — and never a relationship, a counterparty or a count from those sources.
This organization’s supply-relationship count sits above the 99th percentile of the 5,088 organizations in the tracked supply graph. The underlying counts and distribution ride subscription-licensed rows and are not published; the percentile band is the disclosure (see the sourcing note below).
Partially corroborated — the tracked supply corpus independently connects some, but not most, of the 5 subject–counterparty pairs on the control ledger. The class is coarse by design: which pairs, and how the licensed rows describe them, is not published.
No contradiction between the subscription-licensed corpus and the public-record claims rendered on this page was found in the review of Aug 12, 2026. Where such a contradiction is found, the public claim renders here with a flag that conflicting subscription evidence exists — the flag is the maximum disclosure.
Working detail — grades, sources, and what is withheld
1 · How claims are graded
No confidence value is stored anywhere. Each grade is derived when the page renders from three recorded facts — the authority tier of the source, who disclosed it, and whether the value is flagged as an estimate — so a grade cannot disagree with the claim it sits beside.
Attested Stated in a primary or research-grade record by the subject, a counterparty to the relation, or a regulator.
Reported Carried by press or third-party reporting rather than a party’s own record.
Inferred Derived or estimated — including ceilings a party states as “up to” figures.
An estimate outranks its source: a ceiling stated in a counterparty’s own press release (“up to 5 GW”) grades inferred, because the number is a bound and not a measurement.
2 · Where each layer reads
Control. control_relations only — never a facility’s owner or operator column. Those columns carry, for catalog rows, a copy of the hardware-owner field whose own published definition disclaims facility ownership and operation, so they were retired as attribution sources.
Constraint. Export-control designations anchored to Federal Register citations, the platform’s designation-to-organisation cross-reference, and rule-derived country access classifications.
Disclosure posture. The Global LEI Foundation golden copy — registration, parent-reporting declarations, and consolidation records — read by the organisation’s own identifier, plus its SEC registrant record where one exists.
Capacity. The facilities substrate, with Epoch AI cited per record for catalog rows.
3 · How absence is recorded
Three states, kept apart everywhere on this page. Rows: the record holds claims. Searched, nothing admissible: a search was run, its method and date are printed, and what it found could not be reduced to a citable primary. Not swept: no search is on file.
Collapsing the last two would let a budget limit read as a finding about the world. A lead that cannot be traced to a document is recorded as a lead, never as a row.
4 · What is not published, and why
Some records here were established with reference to subscription corporate-data sources that cannot be republished. Where that applies, the published record cites the public primary that establishes it; the subscription source informed only which records to seek and how complete we believe the result to be. No subscription-sourced record, identifier or value is served by this site.
That is why the supply layer publishes a percentile band rather than a count, and a corroboration class rather than a list. Those forms cannot be inverted back into the underlying rows, which is the property that makes them publishable at all.
Everywhere else on this page, a derived figure prints the operands it was computed from.
The four records in this instrument were chosen to span the cases the substrate has to handle: compute held only by contract, compute held by title, compute held by operation, and an organisation the public record barely reaches. Other organisations have directory entries; a record like this one exists where the control layer has been swept.