Carrying the order, making the call¶

This is where defence architecture begins to diverge sharply from civilian architecture. Two layers sit together here: the networks that carry information, and the command layer that turns it into decisions. Everything below this generates information. Everything above executes a choice. The command layer is the join.

Communications¶

Most defensive bodies of any size run several overlapping signals systems rather than one, because the requirements pull in different directions.

The administrative networks carry routine business and resemble ordinary government clacks. The operational networks carry planning and command, with higher security and harder separation. The tactical networks carry an operation while it happens: field signal systems, mobile relay nodes, deployable command posts, the semaphore that travels with whoever the city sends out. The strategic networks carry distance: the Grand Trunk backbone, hardened relay sited to survive a tower going dark, and the alliance connections that let material cross between Circle Sea partners on a shared scheme.

The design goal that runs through all of it is survivability over efficiency. Many bodies maintain signal paths intended to keep functioning during a large conflict, paying for redundancy and hardening that ordinary economics would never justify, because the day the paths are needed is the day nothing else is working.

Command and control¶

This is, arguably, the heart of the force. The components are familiar in outline: command centres, operational headquarters, battle-management systems, planning systems, the dashboards that show a situation at a glance, and the fusion environments where scattered reports become a single picture.

A useful mental model is the harbourmaster. The harbourmaster does not own the ships and does not sail them, but holds the picture of what is where, what is moving, and what is about to collide, and issues the small instructions that keep a crowded water from becoming a wreck. The command layer does the same for operations rather than vessels, at scales that can run from a single posting to an alliance acting together.

For the city this is the Long Table: the place where fragments are consolidated into the view that eventually reaches the Patrician, who sits above the command layer in the way the source diagrams never quite capture, and who resolves most disputes by raising an eyebrow at the party he wishes to reconsider.