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
- AS PER TASK GROUP ORDERS ORIGINATING CS UNDERBELT, HAVE PROCEEDED WITH COHORT, CS GOUGER, TO LAST KNOWN POSITION CS GUTPUNCH, MALTEVIC SYSTEM.
- 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.
- RESPONSE TO FORWARDED QUERIES TO SYSTEM ENTRY BUOYS IN NARIJIC AND KERJEJIC SYSTEMS INCLUDES NO HIGH-ENERGY EVENTS.
- CS GOUGER WILL PROCEED FORTHWITH TO NARIJIC SYSTEM AND COMMENCE SEARCH GRID SWEEP.
- SELF WILL PROCEED FORTHWITH TO KERJEJIC SYSTEM AND COMMENCE SEARCH GRID SWEEP.
- MORE FOLLOWS.
- AUTHENTICATION MORAINE HAMMOCK VAULT SIMMER GOLDEN PAWL / 0x9981ABD43E3ECC22
ENDS.
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™.
It’s a good question. I answer in detail here: https://eldraeverse.com/2016/02/20/fleet-communications/