Banning qualifying engine modes moved the advantage somewhere quieter

A one-mode regulation was sold as a fairness measure, and it mostly rewarded the teams with the deepest reliability margins.

One mode for qualifying, the same mode for the race. That was the rule, and on the face of it there is nothing to argue with. Nobody could turn the wick up for three minutes on Saturday and then hide behind a fuel-saving map for two hours on Sunday. Simple. Enforceable by telemetry. The kind of regulation a governing body likes because it can be checked without opening anything.

What it did to the sport is a different story.

Take away the ability to peak, and the engine that wins is the one that can sit permanently near its own limit without breaking. That is not a driver skill and it is not really a strategy skill either. It is a materials and validation programme, run on dynos, twelve months before anyone sees a grid. The rule was written to compress the field. In practice it rewarded whoever had already spent the money to make their high-output setting survivable for a full race distance, and it punished the manufacturer whose clever trick was a short, aggressive burst.

I think that is the pattern with almost every deployment regulation. Officials can police a shape, a number, a sensor reading. They cannot police the engineering culture that decides which number is easy to live with.

There is a second consequence nobody advertised. When the same map has to serve both sessions, drivers lose a lever they used to manage other problems. Overheating in traffic, a marginal brake temperature, a rear tyre going away on lap forty. Some of that used to be solved by dialling deployment back in a way the rules now make awkward to justify, because any change looks like the thing that was banned. Teams end up asking the stewards for interpretation on adjustments that were once routine.

And enforcement is asymmetric. A works team with its own engine department can demonstrate exactly what happened in every millisecond of a lap. A customer team is arguing about hardware it did not design and software it cannot fully read. When a technical delegate asks a question, the two garages are not equally able to answer it, which quietly makes compliance a function of budget.

The honest version of the rule would say so. It would admit that freezing deployment does not level anything, it just decides which kind of advantage remains legal.

Right now it protects the incumbents and calls that parity.