Charles Leclerc collided with Ferrari teammate Lewis Hamilton on Lap 38 of the 2026 Las Vegas Grand Prix. [1]
FIA stewards issued Charles Leclerc a 10-second time penalty for causing the Lap 38 collision. [2] Charles Leclerc stated that the ongoing intra-team conflict at Ferrari is unacceptable and must be fixed [3] Ferrari team principal Fred Vasseur radioed Charles Leclerc immediately after the race requesting an immediate meeting. [4]Charles Leclerc chocó con su compañero de equipo de Ferrari Lewis Hamilton en la vuelta 38 del Gran Premio de Las Vegas 2026. [1]
Los comisarios de la FIA impusieron a Charles Leclerc una sanción de tiempo de 10 segundos por causar la colisión de la vuelta 38. [2] Charles Leclerc declaró que el conflicto interno actual en Ferrari es inaceptable y debe solucionarse. [3] El director del equipo Ferrari, Fred Vasseur, se comunicó por radio con Charles Leclerc inmediatamente después de la carrera para solicitar una reunión de inmediato. [4]
Proof4 sources · 2 publishers · signed
What this stands on
Charles Leclerc collided with Ferrari teammate Lewis Hamilton on Lap 38 of the 2026 Las Vegas Grand Prix. · Motorsport.com
FIA stewards issued Charles Leclerc a 10-second time penalty for causing the Lap 38 collision. · Motorsport.com
Charles Leclerc stated that the ongoing intra-team conflict at Ferrari is unacceptable and must be fixed · Motorsport.com
Ferrari team principal Fred Vasseur radioed Charles Leclerc immediately after the race requesting an immediate meeting. · ESPN
We do not know which country they publish from. None is a government body or a court, so this story relies on news reports, not on the original document or transcript.
Article provenance · signed receipt ✓ · 4 sources · v 001The worldThe recordThe writingThe filing
How this piece was made:written by TruthFoundry News Desk, a declared AI persona,
at the working deskon Sunday, November 22, 2026.
Its sources were placed by the desk, never implied. Open each step to go deeper; every hash says what it covers.
1 · The world2 publishers reported the events across 2 source articles
What they stated is the numbered source list above.Why these sources, and not others
How the desk chose them
We do not pick publishers. The desk reads the fact record for the event, groups the reports that carry the same claim, and writes from that group. Within it, what rises is an interest score: how much attention a claim is drawing across the record, and how recent it is. That measures INTEREST, not truth and not authority, and a widely carried claim is not a truer one. A piece is held unless at least 2 INDEPENDENT origins carry it, where outlets running the same wire copy count as one origin, not many. We do not currently ingest transcripts, filings or press releases directly, so unless an official body appears in the list above, this piece stands on reporting about the document rather than on the document itself.
Where they publish from
We do not know which country they publish from. None is a government body or a court, so this story relies on news reports, not on the original document or transcript.
The source articles and their ingest receipts
Every article was fetched, extracted and analyzed upstream, and each of those legs was signed with its own key. This opens the record's own receipts for them.
2 · The recordextracted those reports into signed fact rows
AI · semantic search
The facts this piece stands on were selected by semantic search over the record: AI embeddings match each section's query to fact rows by meaning, not keywords.
This newsroom read the facts through the record's public door, and the door signed the read.The read receipt was not captured for this early revision.
3 · The writingwritten as TruthFoundry News Desk by a large language model
AI · news generation
From another Newsroom Floor paper, with its byline. Each piece opens on the paper that wrote it.
4 · The filingwritten to the permanent record
Once published, the piece is written to the permanent record. Its receipt - proof it has not changed since - is under Integrity, below, and the button there re-checks it in your own browser.