Napoleon before it was called operational art

In Napoleon's army, there was a unit that was required to fight alone against a superior enemy for at least a day. It's worth starting with this strange requirement.
The corps was supposed to hold out for a day against superior forces, to hold out until their neighbors arrived. It was a dry, almost regulatory requirement, but it says more about the structure of that war than tales of brilliant insights. For a corps to last a single day, it had to be built like a small army. And for such corps to form a major war, someone had to think on a level for which there was no word at the beginning of the 19th century.
The corps as a small army
Frame - corps d'armée — this was no longer an overgrown division. All branches of the armed forces were gathered here under one command: infantry, cavalry, artillery, supply trains, and auxiliary units. The corps had its own headquarters, several infantry divisions with their own artillery, a cavalry division, and additional corps artillery. This complement constituted the unit. self-sustainingIt could conduct combat, reconnaissance, cover, and supply operations without constantly looking back at headquarters.
Eighteenth-century armies also knew division, but they were divided into divisions—purely tactical units, without the full complement of branches of service. A division's horizon was a single battlefield. A corps aimed for greater scope, encompassing an entire theater of war. The divisional principle was not simply strengthened here, but expanded. The corps combined branches of service so that a single unit could operate independently for days, not hours, and did not require constant command from above.
Hence the regulation requirement of a day alone. This isn't rhetoric. It's essentially a technical requirement: the corps was designed to withstand the enemy's main attack and give the rest time to arrive. Self-sufficiency here isn't a convenience, but rather a prerequisite for dispersing the army across the theater without it being dispersed into pieces.

A. Averyanov. Drawing. 1st Grenadier Regiment of Napoleon's Old Guard (1808-1815)
Walk separately, fight together
Why would an army disperse at all? Because otherwise, it's unwieldy. A column on a single road would stretch out into transitions, devour the surrounding area on the very first day, and expose its entire length to attack. Napoleon's army moved differently. The corps marched along different roads, fanning out. Supplies were facilitated, congestion disappeared, the forces were spread out across a wide area, and the enemy had no way to catch the entire mass at once.
But dispersal is only as dangerous as the difficulty of reassembling. This is where autonomy came into play. While the units marched separately, each could fend for itself; but for battle, Napoleon brought them together in a single point, within a day's march. The principle that became the signature of this war was: go separately, fight togetherFlexibility on the march and quick concentration are two sides of the same coin, and both rested on the fact that the corps would not perish if left alone for a day.

"First Empire: The Battle of Aspern-Essling" by Giuseppe Rava depicts the May 1809 battle between Napoleon I's Imperial Guard under General Dorsenne and the Austrian army.
Decisions given down
This plan had a hidden condition, easily forgotten when looking at a post-war map, where everything is neatly marked with arrows. The army is stretched out for dozens of kilometers along several roads. Communications are like a horseman with a package. By the time the order reaches the flank, the situation will have changed.
Managing such a war from a single point was physically impossible, and Napoleon solved the problem not by accelerating communications, which was unattainable, but by redistributing decisions. Corps commanders were given a mission, not a route. The commander-in-chief set the direction, objective, and place of the corps in the overall plan, while the choice of routes, formation, and the very moment of engagement remained with the commander. The center held the main point; the details were relegated to the lower levels.
Here it's worth pausing, lest we retroactively ascribe to the past a coherence that never existed. The culture of subordinate initiative, the very one that the Germans in the second half of the 19th century would call auftragstaktikThis is, after all, a Prussian-German invention, and attributing it to Napoleon's marshals as a coherent system would be anachronistic. Napoleon himself was renowned for the opposite: rigid centralization, a distrust of the marshals' independence, and a habit of keeping everything in his head. And when the theater of operations grew to an impossible size—in Russia in 1812, in Germany in 1813—it was precisely the lack of independent commanders capable of acting independently that resulted in serious command failures. For Napoleon, delegation was a forced concession to distance, not a doctrine. But this concession proved fruitful: the corps commander, willy-nilly, became accustomed to thinking for himself, and from this habit later grew a tradition that would later be consciously understood and formalized by other armies.
War as a sequence
Put together an autonomous corps, a fan march, and decisions handed down from below, and something emerges that the military language of the era had yet to name. Napoleon was no longer directing a single battle. Before him lay a coherent series of operations. Several corps were coordinated across a broad theater; maneuvers, demonstrations, and feints paved the way for a decisive attack; the battle itself became a link in a chain subordinated to a common plan.
This is the layer between tactics and strategy. Strategy explains why the war is being waged at all. Tactics focuses on something much more specific—how to win this particular battle. And between them lies the realm where battles and marches coalesce into an operation, and operations into a campaign. Later scholars approach this layer in different ways. English-language authors A History of Operational Art They trace the practice itself back to the Napoleonic campaigns, while the Soviet military school of the 1920s—Svechin, Triandafillov, Varfolomeyev—gives this layer a name, introducing the term "operational art." It's curious that some describe the subject, while others baptize it, and almost a century separates them.
Theory catching up with practice
When action outstrips language, sooner or later those who are willing to find the words emerge. The experience of Napoleon's campaigns yielded two main interpreters, and both, in essence, described the same nameless layer, only from different entrances.
Antoine-Henri Jomini derived rules for conducting operations: lines, directions, concentration of forces at the decisive point. Carl von Clausewitz approached things differently, using the concept of the center of gravity and the desire to understand war as a whole, in its interplay with politics. Jomini was later criticized for being excessively geometric, for reducing living war to a blueprint and ignoring its political nature. There is truth in this criticism, although it shouldn't be taken as a condemnation: behind Jomini's diagrams stood a real object, and someone should have been the first to attempt to draw it, even if with overly precise lines.
And here's what's curious about this era. A unit obliged to stand alone for a day; corps spreading out along roads to converge at a given point; orders given with the expectation of someone else's decision—all of this was already in effect back then. At Austerlitz, it worked brilliantly; at Jena, it nearly fell apart at the seams: the French themselves didn't know where the Prussian main forces were, and the corps nearly entered the battle disorganized. The name for all this caught up with practice a generation late and, as often happens, found it far from as streamlined as theorists would later paint it.
Information