Scrutica
Capacity, hardware inventory, ownership chain, and supply-chain position for Mistral Large Model Implied Cluster. Any export-control exposure is walked through the canonical organization graph — surfacing when the BIS Entity List touches a node above the facility in the chain — rather than asserted at the facility row.
As of 2026-07-27
Timeline
Operational
Nov 26, 2023
Notes
Taking H100 price as $2/hr, and assuming they trained for 3 months max, this implies that the cluster they used was >4k GPUs
owner_attribution_withdrawn — This record named CloudHQ as owner. No source does: the Epoch CSV row for Mistral Large Model Implied Cluster leaves Owner empty and reads "Cloud" in the Users column, a user-category descriptor. The ingest fell back to that descriptor and resolved it through a prefix matcher, where the five-character word "cloud" matched the canonical name "cloudhq" (5/7 = 0.71 above the 0.6 length-ratio guard, and "cloudhq" starts with "cloud"). Owner withdrawn to NULL rather than replaced — no source names an owner for this site, and DQP §5 prefers an empty value to a guess. The ingest no longer runs users-column descriptors through the prefix tier (scripts/lib/epoch-org-resolver.ts, regression tests at scripts/tests/test-epoch-org-resolver.test.ts).