watching
SpaceX Posts Record $7.8 Billion Revenue in First Public Earnings
Atomic claim preserved separately so evidence can move without rewriting the occurrence.
Durable event record · earnings release
This durable record identifies one bounded real-world occurrence. Its identifier does not change when the title, slug, coverage, or evidence improves. Each atomic claim remains its own case because one fact can be supported, corrected, or disputed without forcing every sibling claim into the same state. Articles are publication artifacts, and syndicated copies share a reporting origin so repetition is never presented as independent confirmation.
This durable record identifies one bounded real-world occurrence. Its identifier does not change when the title, slug, coverage, or evidence improves. Each atomic claim remains its own case because one fact can be supported, corrected, or disputed without forcing every sibling claim into the same state. Articles are publication artifacts, and syndicated copies share a reporting origin so repetition is never presented as independent confirmation. The source receipts below define what can be known and what remains open; the event container itself is not a verdict.
watching
Atomic claim preserved separately so evidence can move without rewriting the occurrence.
watching
Atomic claim preserved separately so evidence can move without rewriting the occurrence.
watching
Atomic claim preserved separately so evidence can move without rewriting the occurrence.
Coverage is grouped by reporting origin. Multiple distribution copies remain visible provenance but count once as independent reporting.
Reporting origin · nart_9ccb87b77a75651b2e3b
CNBC · original · link hash bounded excerpt
Reporting origin · nart_1bb284d3239794ac3742
Yahoo Finance · original · link hash bounded excerpt
Reporting origin · nart_90f6c8c4484b9cc79942
Reuters · wire · link hash bounded excerpt
Created 2026-08-11T05:30:00.000Z. Last identity update 2026-08-11T05:30:00.000Z. Source receipt references: none public.
Corrections and responses belong on the atomic case whose claim they bear on. Event merge and split operations preserve this ID as lineage; they never silently reuse it.