Nine Layers of Verification in the F1 Analysis Engine, and the Lesson of an Empty Input

On 28 October 2026, the FIA announced an Accepted Breach Agreement with Red Bull Racing: a 7 million US dollar fine and a 10 per cent reduction in permitted aerodynamic testing over 12 months. The penalty did not target a single part on the car. It targeted a set of documents.

That moment shaped how I read everything in this sport. The most expensive thing in Formula 1 does not sit in the garage. It sits in the way an expense is recorded, cross-referenced, and then checked a second time by a party with no direct interest. The FIA Financial Regulations turned accounting into a performance department. They also turned the gap between a submission and reality into a measurable breach, expressed in lap time, because every percentage point of testing time removed comes back on track as thousandths of a second lost somewhere in the season.

That is why I built a nine-layer analytical framework for F1. It is also why this piece has an unusual shape: it is about the day that framework received an empty input.

A season of change at the root layer

The 2026 season changes the sport at its root. The grid expands to eleven teams. Audi takes over Sauber and runs as a works team. Red Bull puts its own engine on track under the Red Bull Ford Powertrains banner. Honda moves to Aston Martin. Alpine switches to customer Mercedes power. Cadillac joins as the eleventh team, with a published plan to run customer engines in the initial phase.

Four of those changes sit in the power supply chain. They matter more than any aerodynamics upgrade release, because the engine determines the budget, determines the development window, and determines the market value of every seat. A customer team does not sit at the table when engine maps are agreed. A works team does.

The 2026 technical regulations shift the power split between the internal combustion engine and the electrical system, and change how active aerodynamics is managed. For a writer, that is a compelling problem. For a reader, it is a sea of noise.

Two regulatory tools matter more than any upgrade claim: the cost cap and the aerodynamic testing restriction. The cost cap started at 145 million US dollars for the 2026 season and stepped down on a published schedule before being indexed for inflation. The testing allowance is allocated in reverse order of the previous season's constructors' standings: the champion receives 70 per cent of the base allocation, the last-placed team receives 115 per cent. The gap between the two ends reaches 45 percentage points.

The paradox is that the weaker team has more testing time but fewer resources to convert that time into performance. Very few commentaries analyse this structure, because it generates no headline.

In the transfer window, the noise spikes. Driver names appear and vanish within hours. A post from a credible journalist travels faster than an official statement. The problem is not the volume of news. The problem is that the reader has no instrument to separate signal from echo.

Nine layers, three groups

I split the framework into three groups: what is measured, what is recorded, and what is narrated. Each group holds three layers.

What is measured

The technical layer is the hardest to verify, because it happens behind closed doors. A change at the floor edge can produce a downforce delta measured in single-digit points, but that value only becomes a fact when the track reproduces it. I always place three sources side by side: the team's claim, the session data, and the gap between two drivers in the same car. When the three disagree, I keep the status undetermined rather than picking the most convenient source. A technical claim only holds value once it survives the third cross-check.

The validation window for an upgrade package usually runs three to four races. A team announces the upgrade at the first race, gathers correlation data at the second, and only by the third or fourth knows whether the package genuinely produces performance. Journalism calls the first-race result a turning point. Engineers call it a test run.

The race strategy layer is the only one that can be verified almost completely once the race is over. Pit loss varies widely between circuits, from roughly 17 seconds at venues with short pit lanes to more than 20 seconds at places like Monaco. That figure governs the entire logic of the race. At a low-loss circuit, the pit-stop overtake is cheap and used continuously. At a high-loss circuit, track position is close to the only asset a driver owns, and one badly timed stop can end the afternoon.

The driver layer has an advantage no other layer has: a perfect comparator. Two cars in the same team, the same parts, the same baseline data. The qualifying gap between team-mates, once fuel load and tyre compound are stripped out, is one of the most stable indicators in this sport. Based on my experience following race weekends across many seasons, a qualifying gap that repeats at one tenth of a second across twelve consecutive rounds says more than any points table.

What is recorded

The governance layer revolves around three categories of document: FIA technical directives clarifying how a rule is read, scrutineering reports after each round, and sporting penalties. The 2026 financial penalty is the most important precedent, because it proved that a divergence between submitted figures and actual figures can be converted into a sanction with a direct effect on on-track performance. Technical directives on bodywork flexibility and on plank wear are two examples of an administrative document erasing the advantage of an entire car concept within weeks.

The financial layer is the one most fans skip. The cost cap carries its own exemption mechanism for driver salaries, marketing activity and several other items. A team can parade an expensive line-up without breaching, provided the spending sits in the right exempt box. Conversely, a small team can run into trouble over a misrecorded item inside the capped portion. A team's real story sits in the structure of its exemptions, not in its published total budget.

The driver market layer operates through contract structures that journalism usually reduces to "a deal until year X". Reality is more complex: automatic extension clauses, conditional release clauses, and performance triggers. A driver can be announced until 2028 while the contract contains a threshold allowing an exit if the team fails to reach a specified constructors' position. Lewis Hamilton's move to Ferrari from the 2026 season and Adrian Newey's move to Aston Martin are two examples showing that the value of a seat is decided by structure more than by raw speed.

What is narrated

The public narrative layer measures how well the underlying data supports a story in circulation. A young driver finishing in the top five at two consecutive rounds generates a praise cycle. But a two-race sample says nothing about true pace. I always check whether that result came with a chain of favourable conditions: a safety car at the right moment, the tyre compound, the weather, or the number of retirements.

The risk layer is the defensive one. I split it into six categories: sporting risk, technical risk, personnel risk, financial and legal risk, public opinion risk, and systemic risk. Each needs a time horizon and a trigger condition. A team can be the strongest on track and the most fragile in personnel, because one chief engineer leaving takes an entire development timeline with them.

The industrial transmission layer is the furthest one. A change in the power supply chain pulls changes in the commercial value of the series, in broadcast rights, and in the flow of capital into teams. When a manufacturer decides to enter or leave, the consequences do not stop at the standings.

When the input is zero

This industry believes more data produces better answers. I think the bottleneck sits elsewhere. The problem with modern analysis is not a shortage of data, but a shortage of provenance trails for that data.

In a recent processing run, the information pipeline I use to build the framework returned an empty file. No article title, no source, no information points, no core claim. Only a single domain label survived. My nine-layer framework ran all nine times, and all nine returned the same conclusion: insufficient information to assess.

A writer's first reflex is to fill that gap with speculation. That is the largest temptation and the most serious error. The tactical machine does not run on emotion; it runs on information. When the information is zero, the machine must stop, and it is not permitted to generate its own fuel.

There is something I learned from an old mistake and keep in my personal file. In 2026 I wrote a prediction piece on the World Cup final between France and Croatia, and made two errors inside one paragraph: I misspelled N'Golo Kanté's name, and I recorded three tackles when the correct figure was four. The site was mocked by readers for a week. I deleted the piece and rebuilt a five-layer checking process: verify the source, review the footage, recount the incidents, ask a specialist, and wait thirty minutes before publishing. My mistake is called Kanté, and I do not want to forget it.

That explains why an empty file carries information. It carries a specific cause: a blocked page, a page rendered only by javascript, or a failed content-extraction step. The framework itself did not collapse. The pipeline feeding it collapsed. A failure at the collection layer can disable the whole analytical chain behind it without making a sound.

And here is the most counter-intuitive part: the absence of a warning does not mean the absence of risk. When the input is empty, all nine layers return an unassessed status. A hurried reader will take that as a clean result. In fact, it is a blind result.

In the transfer market, this mechanism repeats daily. Fans ask which driver is fastest. The right question is which system is on whose side. A driver at a works team has its own engine, an early say over the car concept, and a stable season in which to develop. A driver at a customer team with identical speed will always be half a season slower to adapt. Thousandths of a second do not close a structural gap. A framework only matures after reality refutes it, and mine has been refuted often enough that I know exactly where it goes silent.

The rest belongs to the reader

The lesson from an empty input sits in discipline, not in technology. A good analyst is someone who can tell two very different states apart: no data available, and data showing no problem.

The 2026 season, with eleven teams and five engine manufacturers, will generate more information than any season before it. Most of it will go unverified. The analysis group that builds a provenance trail for every fact will hold a bigger advantage than the group that simply collects more data.

And if any framework can return an unassessed status, the rest belongs to the reader: when the information pipeline goes silent, who is accountable for the blank space?