Is Its Own Replenishment Barge

The Waffle-class drop ship is a starship in mass and displacement, and in many of the other technical senses of the word. But it is not a starship.

The Waffle shares with a variety of small craft (the Marlinspike-class boarding torpedo, the Piton- and Fist- drop pods, and the like) a certain characteristic. Namely, that it is extremely likely, if not absolutely certain, that it will be used only once before being destroyed.

A starship has a name, a spirit, and a history that often goes back through multiple incarnations. Such things, it is generally felt, do not belong with such consumable vessels.

For this reason, the Waffle and its fellows are, by IN regulations, designated “ammunition”.

Very-large-caliber ammunition.

– Traditions and Tales of the Senior Service

Career Limiters

Among the most loathed and dreaded phrases in the Imperial Military Service lexicon is this: “intervention outwith mission parameters is not required”.

That phrase is your lords and masters at CORECOM, usually prompted by advice from Admiralty Intelligence, ISS, the bright chaps at External Clarification & Rectification, or even the Conclave of Clionomy, telling you that your flag privilege to identify the right thing, the thing that the honor of Their Divine Majesties requires, and then do that thing has been – if not revoked – at least severely curtailed.

There’s a reason, of course. The supplementary data that comes with the mission orders tells you what future you’re buying with your restraint, with as many details as they can give you. You can override their call – but you need to be absolutely sure that you’ll win the trade-off, lest you spend the rest of your Navy career counting spacetight valves at the Depot logistics base.

If they need it revoked completely, they’ll escalate the euphemism to “we must stress: intervention outwith mission parameters is not required”. That’s politely mandatory, usually Fifth Directorate, and you don’t want to know the reasons they’re not telling you. In these operations, you don’t sleep well afterwards, but you’ll sleep less well for knowing the reason why.

Exceptionary Circumstances, those are called. Most officers will go through their careers without encountering any. Hope to be one of them, but be prepared for the worst.

– Fleet Admiral Ossil Teresu, classified memoir

Unstuck

FROM: CORE COMMAND (OPERATIONAL MANAGEMENT)
TO: ALL SHIPS

***** ROUTINE
***** FLEET CONFIDENTAL E2048
***** ADVISORY

ALL FLIGHT COMMANDERS:

  1. THIS MESSAGE CONSTITUTES A ROUTINE UPDATE OF STANDING ORDER 147 (TEMPORAL IDENTIFICATION PROTOCOL).
  2. AS PER STANDING ORDER 147(A) TRANSPONDER/IFF SUFFIX PIP 1471 IS TO BE USED BY ANY IMPERIAL NAVY STARSHIP OPERATING NONSEQUENTIALLY IN EMPIRE TIME, EXCEPT AS PROVIDED FOR IN STANDING ORDER 147(C) BELOW.
  3. AS PER STANDING ORDER 147(B) TRANSPONDER/IFF CODES IN SERIES 87413-NNNNNN ARE ALLOCATED TO IMPERIAL NAVY STARSHIPS WHICH HAVE NOT ENTERED SERVICE AT THE TIME OF ENGAGEMENT/ENCOUNTER, AND ARE TO BE CONSIDERED VALID FOR TWO YEARS FROM RECEIPT OF THIS MESSAGE. SUCH IFF CODES ARE TO BE VALIDATED BY PROTOCOL OROELLE BLUESHIFT FRATERNAL AT EARLIEST POSSIBLE CONVENIENCE.
  4. AS PER STANDING ORDER 147(C) TRANSPONDER/IFF SUFFIX PIP 1472 PLUS INSTANCE SEQUENCE NUMBER IS TO BE USED BY ANY IMPERIAL NAVY STARSHIP OR STARSHIPS OPERATING IN CONJUNCTION WITH ITSELF. INSTANCE SEQUENCE NUMBERS ARE TO INCREASE MONOTONICALLY WITH EMPIRE TIME.
  5. AS PER STANDING ORDER 147(D) TRANSPONDER/IFF SUFFIX PIP 1473 IS TO BE USED BY ANY IMPERIAL NAVY STARSHIP EXISTING SOLELY AS A RESULT OF A CAUSAL LOOP.
  6. AS PER STANDING ORDER 147(E) TRANSPONDER/IFF SUFFIX PIP 1474 IS TO BE USED BY ANY IMPERIAL NAVY STARSHIP WHOSE TEMPORAL ALIGNMENT VIS-A-VIS EMPIRE TIME IS UNKNOWN.
  7. AS PER STANDING ORDER 147(F) TRANSPONDER/IFF SUFFIX PIP 1475 IS TO BE USED BY ANY IMPERIAL NAVY STARSHIP WITH REASON TO BELIEVE THAT IT WAS ACTUALIZED FROM A POTENTIAL ALTERNATE WORLDLINE.
  8. AS PER STANDING ORDER 147(G) TRANSPONDER/IFF SUFFIX PIP 1476 IS TO BE USED BY ANY IMPERIAL NAVY STARSHIP WITH REASON TO BELIEVE THAT IT IS SUFFERING AN ONTOLOGICAL PARADOX OR OTHER RELATED EFFECT NOT COVERED BY THE CATEGORIES ABOVE.
  9. NOTE THAT IDENTICAL TRANSPONDER/IFF SUFFICES ARE IN USE BY STARSHIPS ASSIGNED TO THE IMPERIAL EXPLORATORY SERVICE AND IMPERIAL SERVICE. FOR THE PURPOSES OF STANDING ORDER 147(B), SEQUENCES 87412-NNNNNN and 87411-NNNNNN RESPECTIVELY HAVE BEEN ASSIGNED.
  10. AUTHENTICATION: OGRE ANCESTOR SILVER PLUM STAFF NEEDLE / 0x77BB4129A6678A6A

ADM MACIAN CORINTHOS
DIVISION OF RELATIVISTICS & TEMPORAL NAVIGATION

Citation

With the gratitude of the Empire and the thanks of the Lords of Admiralty: that Ardíra “the Bathrobe¹” Octarthius-ith-Octarthius, while commanding Their Divine Majesties’ destroyer Faithful Hound, did successfully escape a surprise attack mounted by linobir vessels of approximate cruiser and battlecruiser type at the commencement of the Linobir-Embatil War, and in so doing did such damage to the cruiser that she was scuttled by her own crew, while preserving the lives of her crew and the fighting weight of her ship, despite the manifest advantages of the enemy in mass, armaments, and attire. Her coolness under fire, gift for tactical innovation, and the fighting spirit of Faithful Hound do her and her crew great credit, and reflect the highest traditions of the Imperial Navy.

– Mentioned in Dispatches: Imperial Navy Awards, 5300-5400


  1. When battle stations sound, you don’t stop to change.

Bigger and Uglier

DROPSHIPS: EMPIRE OF THE STAR

This supplement to the current edition of Naval Warships presents an update to the infamous Flapjack– and Flapjack II-class cavalry dropships. The Imperial Navy has recently adopted the Waffle-class vehicular dropship – also designated the Flapjack I (Block II) – as a phased replacement for the Flapjacks currently in service.

The Waffle resembles the older Flapjack in most ways, inasmuch as it too is based on the disk-type hull form, and makes use of a pair of laser-fusion nuclear-pulse drives to perform a high-velocity descent followed by a “suicide burn” deceleration. However, unlike the Flapjack, the Waffle does not land to disembark vehicles.

The main body of the Waffle, between the pusher plates, replaces the cylindrical garage of the Flapjack with a bunch-of-grapes packed between the central core and the sidewall armor. These “grapes” are the payload: tanks, IFVs, and chariots – any vehicle type equipped with a vector-control core – enclosed in a protective armor clamshell oversprayed with ablative foam.

As the Waffle performs its suicide burn, it dumps angular momentum from its core gyro, spinning the entire ship up. At the terminus of the suicide burn – typically no more than 2000′ above ground – the ship explosively discards the sidewall armor and severs the retaining structure which retains the “grapes”, causing them to be jettisoned along with a large swarm of decoys, chaff, and hunter-seeker antidefensive missiles.

At this point, the basic dropship structure is abandoned, and the vehicles, lightened by their vector-control cores, are scattered over a wide area, discarding their clamshell protection immediately before landing.

Thus, the Waffle eliminates the core disadvantage of the Flapjack, the requirement for rapid disembarkation and dispersal from a single landing site. Additionally, the psychological effect of a cloud of fireballs raining armies from the sky should not, in this author’s opinion, be underestimated.

– Naval Starships of the Associated Worlds, INI Press, Palaxias,
supplement to the 433rd ed.

Haz Beans

Neither somewhere you can visit, nor even somewhere you can see up close – it being found deep within a restricted system – it would nonetheless be remiss to omit Ómílarith, the 14th moonlet of the gas giant Bunker (Arvael IV), in the Palaxias (Imperial Core) system.

It should be obvious from the massive docking facilities built into the moonlet’s northern pole and the radiator structures of its southern tip that it has long been converted to military purposes, as has much of the Palaxias System, but Ómílarith, unlike much of the Bunker sub-system, has not been converted for gas mining, nor for antimatter storage, and nor is it a simple warehouse like the structures that surround Depot (Arvael III) with a set of metallic rings.

It is, however, a cryonic storage facility, and one dedicated to a single good.

Bioweapons? No.

Milspec bodies? No.

Pharmaceuticals? No.

Ómílarith is home to the miles and miles of tunnels lined with cryocels, each holding in perfect preservation one more ton of the seed, the fruit-pip, of the Esklavea sendaren plant.

It is, after all, well-established that the Imperial Navy runs on esklav to a far greater extent that it does on deuterium, antimatter, or even paperwork. No-one is entirely certain what would happen should the beverage cease to flow – whether the Empire’s military operations would simply grind to a grouchy halt, or contrariwise, whether the Navy would sweep through known space like an angry, migrainous wildfire – but even fewer are willing to take the chance of finding out.

Against such mischance, the Imperial Strategic Bean Reserve stands ready.

– Around the Worlds on ¤1,000 per Sol

Squishy

COLLAPSITER (THRESHER MAELSTROM)

Special weapons package THRESHER MAELSTROM, or the collapsiter warhead, is a kugelblitz-based delivery system suitable for deployment from a large-bore heavy mass driver. Put simply, the principle of the collapsiter is the activation upon detonation of a spherical array of annihilation-pumped lasers focused on a single point, raising the mass-energy density of that point to such a degree that a black hole is formed, one which rapidly adds the remaining mass of the warhead to itself. The layout and activation of the array is computed to impart considerable angular momentum to the resulting hole.

The destructive effect of the collapsiter warhead comes primarily not from direct interaction, but rather from the shredding effect of the intense tidal forces exerted by the nascent hole upon objects in its vicinity. Conveniently, these are aligned perpendicular to the controllable rotation axis of the hole, making the collapsiter one of the few coplanar weapons systems in the armamentarium, if one discounts the secondary destructive effect of the eventual quantum evaporation of the kugelblitz and the return of the invested energy in the form of an intense particle radiation burst.

Collapsiter warheads, as relatively contained gravitic weapons capable of remote deployment, are also of particular note for their ability to disrupt and destroy via sharp inflection the controlled space-time distortions used in wormhole-based systems and other metric engineering technologies.

High-yield collapsiter warheads are considered Tier II prohibited weapons under the Ley Accords. However, in practice, the largest barrier to wider collapsiter deployment – bearing in mind the Ley Accords prohibition is on use rather than manufacture or deployment – is the outrageously high insurance rate charged by tort carriers for guaranteeing stargate leases for or in any polity known to deploy collapsiter-based weapons systems. As a corporation dependent upon metric engineering technologies and inasmuch as collapsiter warheads are one of the few weapons systems considered good candidates to overcome the vector-lock armoring of the stargates themselves, Ring Dynamics considers collapsiter deployment in or near systems they serve to warrant a highest-risk assessment.

– A Brief Guide to Special Weapons Packages, IN Press

Neither Fish Nor Fowl

And next in our review of less conventional starship types, we come to that odd duck, the aerospace cruiser. (And many of these remarks, naturally, also apply to its larger cousin, the aerospace carrier.)

Ever since the early Imperial Navy absorbed the old air forces into its Close Orbit and Atmospheric Command (CLATMOCOM, under the Second Space Lord), these specialized classes and their equally specialist crewers have existed in something of a limbo, engaging in practices often deemed unnatural among decent, right-thinking spacers. Such as, if I may write in hushed tones for a moment, streamlining.

In short, while normally one can rely on a comfortable dichotomy between airships – which stay down in the nice, warm, notably present air – and starships – which avoid atmosphere in the much the same way that a thirsty Leirite avoids water – the aerospace cruiser defies this. While even the interface vehicles that bridge these two realms tend to minimize their time spent in the inconvenient middle, it spends all its operational time in a realm too low for low orbit and too high for upper atmosphere, being beholden to neither.

This requires a large number of rather unsettling compromises. Let’s begin our examination with the fundamental reason why: the entire purpose of an aerospace cruiser is to provide a secure base from which atmospheric combat vehicles can sortie, and in order to let them be competitive ACVs, it is necessary not to weigh them down with large extra drive mechanisms just to enable them to get to and from the mama bird. Thus, said mothership must not operate merely in low orbit, but dipping well into the atmosphere – into the lower mesophere – at typical altitudes for lithic worlds no more than 65 to 80 km (211,000 – 264,000′) above the surface. Such altitudes are already painfully difficult to reach for dedicated air vehicles, but manageable with relatively small auxiliary aerospikes.

And yet, the implications! A non-interface starship at this altitude suffers from high levels of atmospheric drag, enough to rip any normal starship’s – one not designed for atmospheric entry – structure apart, and thus, aerospace cruisers must share the great attention to streamlining and the heavier structure required by interface vehicles, but to an even greater extent, since the aerospace cruiser must not only penetrate the entry interface, but hang in it while launching and receiving aircraft from its vomitories.

(This in turn involves various trade-offs in other starship systems, like radiators, which must be accommodated behind streamlined panels while still functioning effectively; the point-defense laser grid must be tuned to atmospheric frequencies despite the effects on performance – and aerospace cruisers are well within the practical offensive range of ground-based aircraft and anti-aircraft systems; the engines must not choke when run in atmosphere; and so forth.)

The next issue, fortunately, partly cancels out this one. While an aerospace cruiser sustaining (via continuous burn; copious fuel supplies and an oiler or two to restock them are also essentials for space-to-atmo operations) orbit at 72 km would have to deal with an arbitrarily long period of fending off the atmosphere at 8 km/sec, consider that the period of such an orbit is a little under 1.5 hours, meaning that an aerospace cruiser maintaining its “natural” orbital velocity will pass very rapidly over the battlespace and out of air range; and pilots in general, it should be said, are notably unappreciative when their mothership leaves them behind.

To avoid this, aerospace cruisers are required to operate in forced orbits, maintaining station above a particular location. This requires, of course, even more copious supplies of fuel and multiplies the required continuous – and for those not familiar with the concept, continuous here means if the drive ever stops, you fall right out of the sky and die – station-keeping burn considerably, but at least it spares you quite so much brutalization by the atmosphere and makes launching and receiving aircraft practical, not just theoretically possible.

So before we continue and look at specific types, let’s raise a glass to these low-flying, fuel-gulping, plasma-shocking, sky-hanging abominations of nature, and all that sail in them! We don’t look down on you – except literally – but we wouldn’t have your jobs for a Service pension and a nice retirement moon.

– the Big Boys’ Book of Boom

Begone, And Trouble Us No More

You may have seen a new Imperial Navy ship on the through route from Qechra to Palaxias in the past few weeks, and not been able to pin down her exact type: she resembles a Leviathan-class dreadnought to aft, but the whole forward half of the vessel seems to have been replaced by a long, four-pronged, blunt-ended ‘snoot’, which more closely resembles the working end of a stargate than anything else.

If the scuttlebutt is anything to go by, that’s exactly what she is – the latest unique special weapons platform of the Black Flotilla, CS Perfect Translocative Defender.

She’s not a wormhole logistics ship; those remain impractical. Despite all the improvements in linelayer-superlifters over the years, moving stargates around is still a very slow process, and one which makes even fleet carriers look speedy and maneuverable. This is largely due to the moon-sized mass of the kernel, which enables stargates to communicate with their paired counterpart. But as you can see, Perfect Translocative Defender does not house a kernel, only the Andracanth ram itself.

Without a kernel, Perfect Translocative Defender is only capable of opening an untargeted wormhole around her target, but this makes her a perfect weapon against those threats undefeatable by conventional means; once she closes to fire her weapon, the target is simply dispatched to a randomized location in space and time, thus removing it as an immediate problem – and, given the sheer vastness of the universe, very likely removing it as a problem entirely.

– Star-Spotter’s Quarterly, Autumn 7840

Gravy

“Among things that you all can be thankful for is that gravitic weapons are of almost no practical use. Partly this is because there is very little training we can give you in dealing with the resulting casualties – due to the low survival rate – but mostly because the results are ugly even by time-of-war standards.

“Gravitic shear, first, ripping a ship in twain with an opposed tractor and pressor, is probably the least bad in damage, but the worst to attend. At least that one might have survivors in the remaining halves, albeit survivors who’ve broken almost every bone in their bodies from the abrupt acceleration, but anything near the shear line will be torn apart. Worst, though, is anyone caught in the fringe effect – that bends and stretches flesh in all the wrong ways. Sophs who’ve been twisted into abstract artwork, and some of them even live through it.

“Then there’s gravitic vibration. ‘Rattling’. Leaves no bodies to bury, because it leaves no bodies. The effects are similar to an inertial damper failure, leaving you with a ship full of meat-slurry. No call for medical treatment; cleaning up after this just needs a hose, a mop, and a well-callused soul.

“And lastly there’s gravitic implosion. There are no slides for this one. No-one, to my knowledge, has ever used a gravitic imploder in combat, but if you insist upon knowing, you can find images of the tests on the IN med-weave. I do not recommend doing so. Sphagettification should have stayed beneath the event horizons where we found it…”

– Surgeon-Commander Vinea Allatrian-ith-Aplan,
lecture at the Faculty of Medicine, Imperial War College

Outsize

“Finally, let us turn to the biggest megaships of them all, the fleet carriers. Including them in this work is a choice which I expect to be somewhat controversial – many would argue that a fleet carrier is a formation, not a vessel – but with respect to those readers who may hold that position, since the Imperial Navy treats fleet carriers as a single vessel for asset accounting and command designation purposes, so in turn shall I.

“Let us begin with a look at the history of the type. Fleet carriers were not known before the Exterminomachy (5782-5901). While before that time lighthuggers had met with occasional hostility, they had proven more than capable of defending themselves against local system defense forces, in particular with the Perreinar Wheel1 – and in those cases where they were not, it was because they had encountered a Power not readily opposed by pure military force. This changed with the arrival of the skrandar berserker probes, whose numbers and willingness to embrace suicide tactics made them a serious threat to even well-defended vessels, and eliminating breeding site for which required the transport of full task forces to their host systems.

“The first fleet carriers, then, were improvisations; lighthuggers pressed into service under the right of angary. Stripped down by removing all cargo capacity, much crew space, and all other less-than-essential facilities, and enhancing their fuel capacity with multiple drop tanks, it became possible to clamp a small number of light units – overstocked with fuel and supplies – to the spine of such a vessel, and have it haul them slowly and painfully to a target system.

“Such crude improvisations were fraught with problems, from wear and tear on ships and crew during the slow transit, to the risk of interception before the transported units could free themselves from the carrier – both due to the inefficiency of the mechanical clamps, and the need to cut clamps frozen in transit or actual hard welds used where clamps would not suffice, to even entire vessels lost from the carrier in transit. (The last of these to be recovered, CS Bloodwashed3, was salvaged with all hands in 6722.)

“Fortunately, by the third year of the Exterminomachy, new designs were emerging from the cageworks at Ashen Planitia and Armory. The second-generation fleet carriers were custom-built starships, or rather, the specialized elements (the “propulsion head” and “collier module”) were, since the second generation eschewed the rigid designs of the first in exchange for dispersed tensegrity structures.

“In effect, the starships transported by the fleet carrier, along with the specialized elements, formed the floating compression struts of the overall structure, while being linked by braided cables (derived from orbital elevator technology) into a unified structure. The majority of the propulsive thrust is provided by the dedicated propulsion heads, while specialized fleet mediator software enables the use of the drives of the various carried ships to balance the structure and correct attitude. Meanwhile, supplies carried in the collier modules, distributed by rigged flexpipe and by cable-crawling logistics robots, eliminated the need to overload any individual ship with supplies, and indeed enabled the transportation of greater volumes of fuel and replenishment. Moreover, such fleet carriers could separate instantly if intercepted by simply blowing the explosive cable-couplers and engaging their drives independently, the dispersed tensegrity structure providing adequate safety separation for this.

“Such dispersed-design fleet carriers served with distinction throughout the remainder of the Exterminomachy, and have remained a key element of IN subluminal doctrine since. While there exist a third generation of fleet carrier designs, these merely reflect the evolution in technological reliability that allows the physical cables of the second generation to be replaced with vector-control tractor-pressor beams, and does not reflect any change in fundamental design or doctrine.

“As ad hoc structures, of course, it would be incorrect to say that fleet carriers have classes, in the strictest sense. However, the individual propulsion heads and collier modules, the former full starships in themselves, do. Thus, we shall begin our examination of fleet carriers with a look at the most common propulsion head in Imperial service, the Legends-class…”

– Megaships of the Imperium, Lorvis Maric, pub. 7290


  1. Perreinar2 Wheel: a fight-and-flight maneuver in which a lighthugger puts its stern towards the battle and engages its interstellar drive, thus retreating from the engagement while simultaneously treating the enemy to the close-range efflux of a pion drive – a situation which is very rarely survivable for anything larger than a baryon.
  2. From the eponymous horse archers who had perfected the “Perreinar shot” centuries before.
  3. Lost in the wreck of CS Cúlíän Daphnotarthius, which suffered a structural collapse of the spine while outward bound to IGS 31238 in the second year of the war.

On AKVs and Survivability

From the questions box:

Dear Gentlesoph,
Having been reading your posts, I have a question about AKVs such as the ‘Daggerfan’ and ‘Slasher’ classes. With high-powered lasers capable of doing damage at one light second, how do AKVs survive the 300,000km journey into single kilometer range? As stated in your ‘Nonstandard Starship Scuffles’ post, military vessels use armor woven through with thermal superconductors dumping heat into ‘thermal goo’. I assume this armor/thermal management system applies to AKVs as well, although you also state that point-defense lasers will shred a vessel unfortunate enough to get into very close range. How can an AKV survive at single kilometer ranges long enough to inflict damage on the target? Thank you for your time, I look forward to more posts!

Well, there are two parts to this: how do AKVs close to skin-dancing range, and how do they survive when they get there? I’ll take ’em one at a time.

On the first point: with great difficulty.

If you take a wing of AKVs and throw them at a fresh battleship, all you’re doing is providing its point-defense computers with skeet; they’ll be chaff and charnel before they get anywhere near the inside of the BB’s point-defense zone.

What you have to do is wear it down first. That’s is the job of the non-carriers on your side of the fight: throw a lot of kinetics at the enemy to make their PD work hard. That does three jobs: one, it keeps the PD grid busy in itself; two, any of it that gets through may just take out a chunk of the PD grid; but most importantly, three, by making them run their point-defenses, you’re building up heat in their ship. Your non-carriers also have the job of pumping heat into their ship directly with the big lasers.

That heat, in turn, is going to eat away at their PD efficiency in a variety of ways. Most simply, it’s going to have to cut back on its firing rate once the heat sinks start filling, because otherwise the crew will cook, but also the hardware becomes less efficient, processor error rates go up, and similar badness ensues.

That’s when you send in the AKVs, and you send in a lot of AKVs mingled with a lot of chaff and decoys, swamping the capabilities of the now-degraded PD grid. They won’t all get through – you plan for a lot of them not to – but once the grid’s sufficiently degraded, enough will to ruin the BB’s day.

As for when they’re there? Remember, they’re described as operating within the point-defense envelope, which is to say, inside its inner boundary, which is defined by the minimum effective range of the PD – set by a variety of factors, such as the range at which firing the PD will seriously damage your own ship, but of which probably the most important is the ability of the PD to track the target and slew to fire on it. At the sort of hug-the-hull sub-km range AKVs like to operate at, it doesn’t take much velocity to generate a huge traversal angle, and what you can’t track, you can’t reliably hit.

(And it’s hard for your screen to fire effectively at the AKVs ruining your day, ’cause even discounting the effects of the AKV exploding at point-blank range, every miss will hit you.)

All of which is to say: While there are some subtleties and complexities to the tactics (defense AKVs, screening vessels sharing PD, etc., etc.), the short answer is it takes a lot of work and losses to get an AKV force within range of a target, but once you do, that target is dead meat.

Covered In Bees

HURRICANE-CLASS DRONE BATTLESHIP (CARRIER)

Operated by: Empire of the Star
Type: Drone Battleship, General Operations
Construction: Palaxias Fleet Yards

Length: 2.3 km
Beam (avg.): 0.8 km
Dry mass: 2,900,000 tons

Gravity-well capable: No.
Atmosphere capable: No.

Personnel: 1,294

  • 396 crewers
  • 514 flight operations
  • 384 espatiers
  • Thinker-class AI

Drives:

  • Imperial Navy 3×3 “Neutrino Dawn” antimatter pion drive
  • Nucleodyne Thrust Applications 4×4 “Nova Pulse” fusion torch

Propellant:

  • Deuterium slush/metallic antideuterium
  • Deuterium/helium-3 slush blend

Cruising (sustainable) thrust: 5.6 standard gravities (5.2 Earth G)
Peak (unsustainable) thrust: 6.6 standard gravities (6.1 Earth G)
Maximum velocity: 0.3 c (rated, based on particle shielding, with flight deck doors closed)

Drones:

  • 43,200 x AKVs (loadout varies by mission, typically Daggerfan-class)
  • Associated thrust packs and modular swapout payloads, by mission
  • 64 x “Buckler VI” point-defense supplementary drones, Artifice Armaments, ICC
  • 32 x “Rook” tactical observation platforms, Sy Astronautic Engineering Collective (with supplementary IN hardware)
  • 64 x general-duty modular drones (not counting flight operations hardware)

Sensors:

  • 3 x independent standard navigational sensor suite, Cilmínar Spaceworks
  • 6 x [classified] enhanced active/passive tactical sensory suite, Sy Astronautic Engineering Collective
  • Imperial Navy tactically-enhanced longscan

Weapons (Auxiliary):

  • 96 x “Slammer III” dual turreted mass drivers (local-space defense)
  • Artifice Armaments, ICC “Popcorn” point defense/CQB laser grid

Other systems:

  • 3 x Artifice Armaments, ICC cyclic kinetic barrier system
  • Biogenesis Technologies, ICC Mark VII regenerative life support (multiple independent systems)
  • 3 x Bright Shadow, ICC custom-build megaframe data system, plus multiple EC-1140 information furnaces for sectoral control
  • AKV repair facilities
  • 3 x Extropa Energy, ICC “Calviata” second-phase fusion reactors
  • 6 x Imperial Navy AKV tactical management suite
  • 3 x Imperial Navy DN-class vector-control core and associated technologies
  • 3 x Nanodynamics, ICC “Phage-a-Phage” immunity
  • 6 x modular swapout regions (large)
  • Systemic Integrated Technologies, ICC high-capacity thermal sinks and dual-mode radiative striping; 3 x deployable droplet heat radiators
  • Tactical bridge

Small craft:

  • 4 x Nelyn-class modular cutters
  • 2 x Ékalaman-class pinnace/shuttle (atmosphere capable)
  • 16 x Élyn-class microcutter
  • 32 x Adhaïc-class workpod

(You’ll notice the obvious similarities to the Leviathan-class dreadnought in systems installed, which should come as no surprise; these two came off the drawing board at roughly the same time. And if you’re wondering why a BB-sized carrier has a DN-sized vector-control core – well, you’ll note that the much more tightly packed supplies of, for example, bunkerage plus AKV bunkerage, plus the need to propel all those AKVs, make it mass significantly more than a Leviathan in practice. Carriers tend to be thus.)

The core hull of the Hurricane-class drone battleship (carrier) is divided into five segments: from bow to stern, the flight operations section, the AKV bunkerage, the command section, the bunkerage, and the propulsion bus, laid out tail-lander style. The flight operations section, by design, is a hexagonal prism, flat faces to dorsal and ventral, and the other ship segments follow this pattern.

Attached to this on the starboard side, extending to dorsal and ventral of the core hull, and running from 100 m ahead of the flight operations section (to give AKVs exit and entrance cover) back to cover the first 100 m of the bunkerage, is the starship’s “buckler”. The core hull of the Hurricane-class is relatively lightly armored for an IN vessel, since carriers are intended, doctrinally, to stay out of CQB and mass conservation supervenes. However, to provide protection against long-distance fire in the outer engagement envelope, as a less maneuverable ship class, the buckler – heavy armor plate connected to the core hull by shock-absorbing trusses – covers and extends slightly beyond the two starboard facets, providing additional protection for as long as the vessel maintains the proper attitude.

The flight operations section at the bow, taking up the first half-kilometer of the ship, is effectively a single large flight deck, opened to space by an armored spacetight door in the for’ard hull. (Unlike smaller flight decks, this region cannot be pressurized.) The 43,200 carried AKVs occupy hexagonal cells clustered on the inner hull to port, starboard, dorsal, and ventral from which they launch themselves, while a small conventional flight deck at the aft end of the section provides space for the Hurricane‘s small craft. The after hull of the flight operations sections is heavily armored, to provide what protection it can against a lucky shot penetrating the flight deck.

Immediately behind the flight operations section is the AKV bunkerage section, which houses fuel and propellant, along with ammunition and other consumables, for the carried AKVs, permitting refueling and rearming. This is the most protected area of the ship, as AKV fuel and ammunition tends to be highly volatile.

The command section, the primary habitable area of the starship, is a relatively small area sandwiched between the AKV bunkerage and the carrier’s own bunkerage, also protected behind the buckler, and housing both the starship’s own operations and the majority of the outsize flight operations department. From dorsal and ventral, sensor towers extend beyond the buckler, allowing line-of-sight sensing and communications with the battlespace without exposing the core hull.

(As a side note, the Hurricane-class, like most large carriers, is an example of the IN’s dual command system. The starship itself is commanded by a Flight Commander, ranked Captain [O-7], from the line branch, while the AKV wings are commanded by a Group Captain, an equivalent rank. Overall command of both is held by a Mission Commander, ranked Commodore [O-8].)

Aft of these, a conventional bunkerage section and propulsion bus, equipped with droplet radiators for primary cooling, fills out the remaining length of the vessel.

Scattered about the length of the vessel is the same heavy-duty (“Popcorn”) point-defense grid used on the Leviathan-class dreadnought, along with 96 small turreted mass drivers – similar to those used on lighter IN classes – for heavier local-space defense.

(They are not intended as offensive weapons; the carrier has 43,200 of those in its AKVs, and would-be Flight Commanders who can’t resist the urge to take their ships into close-quarters battle are redirected towards frigates, destroyers, and other roles where such is (a) tactically useful and (b) much less likely to get one either cashiered for gross incompetence or relieved of command by an XO for whom it is not a good day to die.)

 

On the Role of the Dreadnought

Just to clear up a few misconceptions that may have crept in:

David Weber, alas, has done me no favors by convincing much of the SF-reading world that the standard interstellar badass is the dreadnought.

And, yes, you may remember me saying “it sure would be nice to build nothing except dreadnoughts [for ships-of-the-plane]” back when we discussed ship types, but what I did not say is that if they did, they wouldn’t be dreadnoughts. They’d be battleships, because the modal ship classes for engaging in big set-piece space battles are always designated as battleships. Says so right in the name. Battle. Ship.

Or, to put it another way, there are a lot fewer dreadnoughts than there are battleships. (And a lot more cruisers than there are battleships, for that matter, because most missions don’t have any major fleet engagements in them. But that’s another story, already told.) This is principally for economic reasons: when you examine the requirements for a ship of the plane, the battleship sits right at the bang/buck sweet spot, so that’s what you build.

A dreadnought (and to an even greater extent, a superdreadnought) has four virtues, which is why they’re built at all:

  1. It benefits in internal space from volume increasing faster than surface area, which makes it a convenient class to carry extra stuff, from complete flagship suites through shipyard-class repair facilities for its cohorts and prisoner-of-war blocks to all that is required for the many, many specialized variants on the books.
  2. It can afford a hell of a lot of extra armoring, so you are significantly less likely to get your admiral shot off and your fleet coordination suffering if you give him a DN to ride around in.
  3. It can mount a Really Big Gun of the kind you’ll rarely need to use, but you might miss if you didn’t have any of in your plane of battle.
  4. It’s bloody terrifying. When naval architects are told to draw up plans for a DN or SD, the unspoken requirement is that it dominate the battlespace like Conan the Barbarian at a convention of preadolescent pacifists: it dreads nothing, and everything dreads it.

So there aren’t all that many in service, relatively speaking. There don’t have to be – say, speaking non-canonically and off the back of the envelope, eight squadrons in the Capital Fleet (mostly in the Sixth Flotilla, which is the IN’s heavy-hitting force), four squadrons in Home Fleet, two for Field Fleet Spinward (which borders on the Seam), and one for each of the other field fleets: say, 228 in total, not counting specialist classes and the reserve.

You can assume at least four times that in BBs.

 

Leviathan, Awake

LEVIATHAN-CLASS DREADNOUGHT

Operated by: Empire of the Star
Type: Dreadnought, General Operations
Construction: Palaxias Fleet Yards

Length: 3 km
Beam (avg.): 0.8 km
Z-Beam (avg.): 0.6 km

Dry mass: 2,500,000 tons

Gravity-well capable: No.
Atmosphere-capable: No.

Personnel: 6,736

  • 4,968 crewers
  • 1,768 espatiers
  • Thinker-class AI

Drives:

  • Imperial Navy 4×2 “Neutrino Dawn” antimatter pion drive
  • Nucleodyne Thrust Applications 4×4 “Nova Pulse” fusion torch

Propellant:

  • Deuterium slush/metallic antideuterium
  • Deuterium/helium-3 slush blend

Cruising (sustainable) thrust: 7.2 standard gravities (6.7 Earth G)
Peak (unsustainable) thrust: 8.4 standard gravities (7.8 Earth G)
Maximum velocity: 0.3 c (rated, based on particle shielding)

Drones:

  • 144 x AKVs (loadout varies by mission, typically Daggerfan-class)
  • 144 x add-on thrust packs for AKVs
  • 72 x “Buckler VI” point-defense supplementary drones, Artifice Armaments, ICC
  • 72 x “Rook” tactical observation platforms, Sy Astronautic Engineering Collective (with supplementary IN hardware)
  • 72 x general-duty modular drones

Sensors:

  • 3 x independent standard navigational sensor suite, Cilmínar Spaceworks
  • 18 x [classified] enhanced active/passive tactical sensory suite, Sy Astronautic Engineering Collective
  • Imperial Navy tactically-enhanced longscan

Weapons (Primary):

  • 4800/2400 mm custom axial heavy mass driver, Artifice Armaments, ICC

Weapons (Secondary):

  • 4 x 4800/2400 mm custom heavy mass drivers, Artifice Armaments, ICC
  • 4 x “Black Lightning” axial grasers, Artifice Armaments, ICC

Weapons (Tertiary):

  • 64 x 2400/1200 mm turreted mass drivers (32 capable of broadside use), Artifice Armaments, ICC
  • 8 x 2400/1200 mm turreted mass drivers (rear-firing for kilt defense), Artifice Armaments, ICC
  • 32 x “Flashburn” turreted heavy lasers, Artifice Armaments, ICC
  • Artifice Armaments, ICC “Popcorn” point defense/CQB laser grid

Other systems:

  • 3 x Artifice Armaments, ICC cyclic kinetic barrier system
  • Biogenesis Technologies, ICC Mark VII regenerative life support (multiple independent systems)
  • 3 x Bright Shadow, ICC custom-build megaframe data system, plus multiple EC-1140 information furnaces for sectoral control
  • Class IV starship repair facilities
  • 8 x Extropa Energy, ICC “Calviata” second-phase fusion reactors
  • Flag bridge
  • 4 x Imperial Navy command communications/tactical networking suite
  • 4 x Imperial Navy DN-class vector-control core and associated technologies
  • 3 x Metric Engineering, ICC “Gloaming” ray shielding system
  • 3 x Nanodynamics, ICC “Phage-a-Phage” immunity
  • 32 x modular swapout regions (large)
  • Systemic Integrated Technologies, ICC high-capacity thermal sinks and dual-mode radiative striping

Small craft:

  • 8 x Reaver-class starfighters, with own AKVs
  • 8 x Nelyn-class modular cutters
  • 4 x Ékalaman-class pinnace/shuttle (atmosphere capable)
  • 16 x Élyn-class microcutter
  • 16 x Traest Sargas-class troop transport
  • 32 x Adhaïc-class workpod
  • 32 x Marlinspike-class boarding torpedo
  • 32 x Sledgehammer-class drop shuttle

From without, the Leviathan-class dreadnought resembles a slender wedge, a dagger-blade without a hilt. It is, of course, rather larger than virtually all equivalent dreadnought classes and even some superdreadnought classes seen elsewhere, in keeping with the Empire’s naval construction policy of “shock and awesome”.

This should come as no surprise to anyone, since the realities of armoring such a vessel mandate such a glacis, and as such virtually all ships of the plane, of whatever origin, share this common feature. The Leviathan mixes this up slightly, having a change in ratio along its length that gives the hull a subtle curve and the ship entire a forward-leaning, sleek and hungry look.

(Although those who serve aboard Leviathans, especially back in the maneuvering sector, tend to describe their workplace as the ship’s “fat ass”.)

As is also usual, the apparent outer hull of the vessel is entirely composed of armor plating, which in the case of the Leviathan is a little over 30m thick, comprised of multiple layers of heavy plate, Whipple foam, radiation-absorbent material, thermal superconductors, dilatant shock gel, flexible spreader trusses, and other necessities for survivability in the modern high-energy battlespace, many of which remain classified.

(The important thing to remember about this armor plating is that it is not there to protect against a direct hit from an opposing capital ship. No practicable material will do that. It’s there to protect against the spallation debris left behind after your point-defense grid sweeps the sky like the hand of an angry laser-spewing god.)

This armor serves as a backup to the triple-layered cyclic kinetic barrier system with which the Leviathan is equipped, along with the likewise triple-layered ray shielding to protect against photonic attack.

The majority of the space within this outer hull is unpressurized volume, occupied by machinery space, bunkerage, stores (tanks and unpressurized cargo holds), accessways, robot hotels, and magazines. The habitable volume is represented by a relatively small (roughly equivalent to a 232-storey building, laid out tail-lander style) cylinder buried deep within this, above the axial passage for the primary mass driver, with two attendant counter-rotating gravity rings providing space for gravity-requiring special facilities. Below and to port and starboard of this passage can be found the eight fusion reactors providing non-thrust power to the Leviathan.

In addition to the primary (axial) heavy mass driver, the Leviathan mounts four secondary heavy mass drivers of only slightly lower power along its dorsal-ventral centerline, spread out at 15 and 30 degrees off-axis (although with off-bore firing capability), along with four heavy grasers clustered around, and aligned to, the axial primary.

Tertiary weapons systems consist of 64 turreted mass drivers and 32 turreted heavy lasers, of which half can slew far enough to be capable of broadside firing. An additional eight turreted mass drivers are mounted on the stern for kilt defense, should the prospect of attacking through, or at best in close proximity to, the emissions plume of the Leviathan‘s 24 torch drives not be sufficient deterrent. Finally, the Leviathan is equipped with the Artifice Armaments “Popcorn” laser grid for point-defense and CQB purposes, ensuring that anyone foolish enough to close to point-defense range will have mere microseconds to contemplate their folly before vaporizing in one of the most spectacular coruscations known to sophontkind.

Also pressurized are portions of the “docks and locks” sections to port and starboard, 500 meters for’ard of the drives, which house the Leviathan‘s small craft complement. These are buried beneath the starship’s outer hull armor, which is designed to retract under non-combat conditions to provide ingress. In light of this, the multiple AKV wings and drones are launched via dog-leg tubes through the dorsal and ventral armor, and recovered – if this is necessary during an engagement – when circumstances permit turning broadside to the enemy and recovering through the far-side landing bay.

As a dreadnought, the Leviathan is equipped with a flag bridge and communications/tactical mesh suite for task force command; with the capability to effect repairs on smaller vessels of its task force; with the ability to deploy starfighters for patrol or remote operations missions; and with a substantial espatier force and the means to deploy them, whether in boarding operations or for groundside raids.

 

Hornéd Moon-class starfighter

(Note: for the avoidance of confusion, this is not the same starfighter class as Raymond McVay has been posting over on the G+ fan community; so don’t be confused by the differences…)

“It looks like a blueberry croissant.”

“Blueberry croissant… of DEATH!”

– overheard at Golden Groves (Principalities) starport

HORNÉD MOON-CLASS STARFIGHTER

Operated by: Empire of the Star (Imperial Navy, Imperial State Security, & Imperial Exploratory Service; reliable UARC-sponsored mercenaries)
Type: Starfighter, Orbital and Near-Space Operations
Construction: Ashen Planitia Fleet Yards

Length: 24.8 m
Beam: 60.4 m

Gravity-well capable: Yes
Atmosphere capable: Yes (depending on loadout)

Personnel: 2 nominal, as follows:

Flight Commander / Sailing Master
Flight Engineer

AI expert system support.

(Can operate with a single pilot.)

Additional life support capacity exists to support four passengers in addition, although this requires hot-bunking in three shifts.

Drive: Nucleodyne Thrust Applications 2×1 “Little Sparky” antimatter-catalyzed fusion torch drive
Propellant: Deuterium slush / metallic antideuterium
Cruising (sustainable) thrust: 10.2 standard gravities (9.6 Earth G)
Peak (unsustainable) thrust: 14.0 standard gravities (13.2 Earth G)
Maximum velocity: 0.3 c (based on particle shielding)

Drones:

4 x hardpoint mountings for AKVs, typically Slasher-class

(Hardpoint mountings can also hold single-legionary drop pods, Piton-class, or covert ops equivalents.)

Sensors:

1 x standard navigational sensor suite, Cilmínar Spaceworks
1 x enhanced passive tactical sensor suite, miniature, Sy Astronautic Engineering Collective
1 x enhanced-resolution planetary surface-scan sensor suite, Imperial Exploratory Service (spec.)

Weapons:

“Flyswatter” point-defense laser grid, Artifice Armaments

Other Systems:

Artifice Armaments cyclic kinetic barrier system
Cilmínar Spaceworks Mark III long-duration canned/semi-regenerative life support
3 x Bright Shadow EC-780 information furnace data systems
Ashen Planitia 1-SF vector-control core and associated technologies
Cilmínar Spaceworks high-capacity thermal sinks and integrated radiator system
Aleph Null Systems tactical communications suite

Small craft:

None.

The Hornéd Moon-class is a small starfighter intended for fast attack and fast insertion missions in planetary orbit and deploying to the surface. As such, it has atmospheric capability, and even the ability to land.

In overall form, it resembles – as the quotation indicates – a croissant or crescent moon of flying-wing conformation, with the thin “inside” edge of the crescent facing forward. The two forward-facing points of the crescent are rounded, and rise to a near-cylinder at the for’ard end, and a rectangular section of the central section is “humped” at the rear; this contains the drives, whose nozzles protrude from this rectangular shroud aft.

Atop the starfighter, paired hardpoints on the dorsal hull to port and starboard hold the AKVs, when mounted. Additional mountings near them permit jettisonable fairings to be used to permit atmospheric entry or departure when non-streamlined AKVs are carried.

In between them, atop and for’ard of the drive shroud, radiative striping mounted directly atop the hull, beneath protective shutters, provides heat dissipation. To provide additional control (to the reaction wheel system) when in atmosphere, a number of multiple-purpose aerodynamic control surfaces are mounted along the leading edge of the hull, and to two small vertical stabilizers at the port and starboard edges of the drive shroud. Deployable rollagon landing gear are fitted ventrally in a multiple tailwheel configuration.

The main body of the ship is entirely devoted to fuel storage, with multiple deuterium tanks wrapping around the small antimatter cryocels for maximum protection. Meanwhile, the starboard near-cylinder provides housing for the ship’s avionics, including (beneath the forward-mounted radome and associated shuttered ports) for the triple sensor suites and tactical communications systems.

The starship’s small habitable area is located in that to port; the forward-facing airlock (whose outermost section is covered by a retractable streamlining fairing and extendable airstair) at far port gives onto a short corridor providing access to, in order, the ship’s bridge (behind an open viewport for close-maneuvering use), a two-pod sleeping area, a small room tripling as galley, fab shop, and rest area, and a single-person ‘fresher at corridor end. Limited avionics and life support access is possible through panels in this area; however, there is no pressurized access to the main avionics bay in the starboard near-cylinder or to engineering systems; such access requires EVA. Likewise, if drop pods are carried, access to those (for pre-deployment boarding, say) is only possible through EVA.

 

Fleet Communications

A commenter raises an interesting point with regard to fleet communications, which as we have seen in various places, tend to look like this:

FROM: CS GRITFIST (FIELD FLEET RIMWARD)
TO: FIELD FLEET RIMWARD COMMAND (CS ARMIGEROUS PROPERTARIAN)

*** ROUTINE
*** FLEET CONFIDENTIAL E256
*** OVERDUE FOLLOWUP

REF: TASK GROUP R-4-118
REF: OVERDUE STATUS, CS GUTPUNCH

  1. AS PER TASK GROUP ORDERS ORIGINATING CS UNDERBELT, HAVE PROCEEDED WITH COHORT, CS GOUGER, TO LAST KNOWN POSITION CS GUTPUNCH, MALTEVIC SYSTEM.
  2. NO TRACES OF CS GUTPUNCH OR RECENT SIGNS OF COMBAT APPARENT OR RECORDED IN SYSTEM LONGSCAN BUOYS. TRANSPONDER LOGS CONFIRM OUTBOUND GATING TO NARIJIC SYSTEM IN ACCORDANCE WITH PATROL ROUTING.
  3. RESPONSE TO FORWARDED QUERIES TO SYSTEM ENTRY BUOYS IN NARIJIC AND KERJEJIC SYSTEMS INCLUDES NO HIGH-ENERGY EVENTS.
  4. CS GOUGER WILL PROCEED FORTHWITH TO NARIJIC SYSTEM AND COMMENCE SEARCH GRID SWEEP.
  5. SELF WILL PROCEED FORTHWITH TO KERJEJIC SYSTEM AND COMMENCE SEARCH GRID SWEEP.
  6. MORE FOLLOWS.
  7. AUTHENTICATION MORAINE HAMMOCK VAULT SIMMER GOLDEN PAWL / 0x9981ABD43E3ECC22

ENDS.

…to wit:

One thing about these: while I understand the stylistic motivation of using all-caps (reminiscing to WW2-era (and later) communiqués, in Isif’s world, that makes no real sense. In WW2, the all-caps was a result of having no distinct-case (and some bright chap thinking it was better to have all-caps, even if they are a lot harder to read).

I do not have a ready solution to carry the “fleet communiqué” vibe easily, but I think just the rest of the format (headers, enumeration, the “Ends.” trailer) would be good enough™.

Well, here’s the reasoning behind it. But first, I will note that not all communication to and from fleet vessels looks like this. We also see some that comes over more normal channels, which looks like this:

From: Executor Major Garren Melithos, Uulder Shore Constellation Adhoc, Imperial Exploratory Service
To: Cmdr. Leda Estenv, Flight Administrator, CS Iron Dragon
Subject: Checking up

Your Mr. Sarathos is shaping up as well as can be expected here after his transfer. Per his request, we put him to work on the hush-hush clean-up of Ekritat’s atmosphere after his oops, and he’s doing a good job there so far. Chastened, but competent.

My colleagues have some similar projects lined up for him after this. If all goes well, we might just manage to salvage him and his career.

-gm

…so what’s the difference and why the stylistic change?

Protocol.

The latter is just plain old extranet e-mail, sent out over SCP (Secure Courier Protocol), and which works the same way as any other e-mail, which is to say while rather more complicated than ours (involving the use of presence servers to first link name to location, and then routing protocols to link location-of-mobile-subnet – which is to say, starship – to current-network-location), is nothing special and can transmit arbitrary formatted data. It’s routed at standard-traffic priority, being routed over light-speed links between stargates until it gets to its destination system, then over laser tightbeam between relay stations and finally to the starship’s own receiver. Since it’s going to a military destination address, the protocol probably coerces the notrace, noloc, and deepcrypto bits on, but yet.

The former, on the other hand, is an action message, being sent over the Navy’s own GLASS PICCOLO system, which piggybacks on the extranet for some routing purposes but doesn’t use standard protocols. That’s because it’s optimized for speed, security, distribution without presence servers if need be (for starships running in communications silence), etc., but most of all minimal size, because the GLASS PICCOLO system uses the IN’s private tangle channel backbone wherever it can appropriately do so for speed, but once a tanglebit has been used in communications, that tanglebit is gone forever. It can’t be reused, only replaced. And if you’re coordinating a war, you don’t want to find yourself running out of tanglebits to do it with.

So it does have some relevant constraints. Not so much lack of distinct case – think of it more like the ELF communications the US Navy used to use, except the constraint is not speed of transmission, it’s the potential permanent consumption of the transmission medium.

GLASS PICCOLO messages are converted into five-letteral code-groups – which is why the language in them tends to be stilted, because you aren’t reading what anyone actually wrote, you’re reading the computer transliteration of the code-groups – signed, compressed, encrypted to the recipient key, and squirted out on the GP network as a single-packet datablip. The recipient’s communication computers reverse the process.

All of which is to say: it’s a deliberate stylistic choice, yes, but the reason I’m invoking those very different-looking historical communication formats is to suggest to the reader that these messages indeed ain’t like those messages.

(One side note: it’s not a matter of lacking distinct case, I append for those who aren’t keen minutiae-watchers, because none of the three major Eldraeic alphabets – runic, pen, or brush-optimized – actually have a concept of letter case. Which of the alphabets either of the above would be displayed in depends on the personal UI customization of the comms officer reading them.

There might be a tendency for slight runic to predominate, since as its hexagon-based letterals and numerals are all identical in size, it was the alphabet used by the people who designed the original fixed-width computer terminals and predecessor devices, but everyone *there* has had a WYSIWYG system for more years than humanity’s had writing, these days…

But from a Doylist perspective, all-caps makes a convenient Translation Convention.)