Fleet Communication Protocols - Revision history

Scottsigler: /* See Also */

2025-04-24T16:48:25Z

‎See Also

Scottsigler: /* Current Voidcraft Types in Use */

2025-04-24T16:48:03Z

‎Current Voidcraft Types in Use

Scottsigler: /* Current Voidcraft Types in Use */

2025-04-24T16:47:52Z

‎Current Voidcraft Types in Use

Scottsigler: /* Current Voidcraft Types in Use */

2025-04-24T16:47:30Z

‎Current Voidcraft Types in Use

Scottsigler at 16:46, 24 April 2025

2025-04-24T16:46:37Z

Scottsigler: Created page with "‘’‘Fleet Communication Protocols’’’ The Planetary Union Fleet employs a structured and scalable communication protocol to identify and coordinate voidcraft during..."

2025-04-24T16:43:08Z

Created page with "‘’‘Fleet Communication Protocols’’’ The Planetary Union Fleet employs a structured and scalable communication protocol to identify and coordinate voidcraft during..."

New page

‘’‘Fleet Communication Protocols’’’

The Planetary Union Fleet employs a structured and scalable communication protocol to identify and coordinate voidcraft during missions. This system ensures clarity across multiple ships and squadrons, particularly in engagements involving dozens or even hundreds of combat assets.

== Voidcraft Communication Protocol ==
This naming system governs all small craft operating from a larger capital-class vessel or base, including APCs, fighters, and interceptors.

=== Standard Format ===
• ‘’’[Class] + [Local Number]’’’
• Example: ‘‘Crawler One’’, ‘‘Sentinel Three’’
• Used during low-traffic operations or when only a few craft are in the battlespace.

=== Group Format ===
• ‘’’[Mothership/Base Code] + [Class] + [Local Number]’’’
• Example: ‘‘Crawler Kilo-Echo-One’’, ‘‘Sentinel Alpha-Kilo-Three’’
• Required when operating in multi-ship environments or when call sign duplication is possible.
• The mothership or base code is a two-letter abbreviation derived from the vessel or base name:
** ‘‘Kilo-Echo (KE)’’ = [[PUV James Keeling]]
** ‘‘Alpha-Kilo (AK)’’ = [[PUV Akathaso]]
** ‘‘Golf-Whiskey (GW)’’ = [[Gateway Station]]

=== Mission Suffix Format ===
• ‘’’[Mothership/Base Code] + [Class] + [Local Number] + [Mission Suffix]’’’
• Example: ‘‘Sentinel Alpha-Kilo-Three Razor’’, ‘‘Crawler Kilo-Echo-One Needle’’
• Used in high-density or carrier-based operations to designate specific mission roles.

== Recognized Voidcraft Classes ==
• ‘’‘Sentinel’’’ — U-90 Interceptor (fighter)
• ‘’‘Crawler’’’ — GU-44 Ochthera (APC)

== Mission Role Suffixes ==
• ‘’‘Noise’’’ — Electronic warfare
• ‘’‘Carton’’’ — Troop transport and assault
• ‘’‘Dump’’’ — Mine-laying operations
• ‘’‘Needle’’’ — Troop transport for boarding actions
• ‘’‘Blast’’’ — Counter-air mission
• ‘’‘Jolly’’’ — Search and rescue (SAR)
• ‘’‘Razor’’’ — Deep penetration strike
• ‘’‘Shield’’’ — Counter-boarding / internal defense

== Usage Guidelines ==
• Use the short form (e.g., ‘‘Sentinel Three’’) during basic operations or when only a few craft are in the battlespace.
• Use the group format (e.g., ‘‘Sentinel KE-Three’’) when multiple capital ships are fielding similar craft.
• Append a mission suffix only during high-intensity or carrier-style operations, where multiple mission roles are running simultaneously.
• In radio communication, clarity is paramount. Use full call signs until the tactical situation permits shortening.

== Examples ==
• Low-density op: ‘’“Crawler One, you’re clear to launch.”’’
• Carrier environment: ‘’“Crawler Kilo-Echo-One Needle, maintain your vector for boarding operations.”’’
• Combat air patrol: ‘’“Sentinel Alpha-Kilo-Three Blast, bandits inbound bearing zero-seven-zero.”’’

[[Category:The Crypt]]
[[Category:Planetary Union Fleet]]

← Older revision		Revision as of 16:48, 24 April 2025
Line 63:		Line 63:

	== See Also ==		== See Also ==
−	* [[PUV James Keeling]]
−	* [[GU-44 Ochthera]]
−	* [[U-90 Sentinel]]
−	* [[Planetary Union Fleet]]
	* [[Fleet Contact Management System (CMS)]]		* [[Fleet Contact Management System (CMS)]]

@@ Line 45: / Line 45: @@
 * [[GU-44 APC %22Ochthera%22]]: Multi-role armored personnel carrier
 ** Typical callsign: ''Crawler''
-* [[U-90_Interceptor_%22Sentinel%22]]: Interceptor voidcraft
+* [[U-90 Interceptor %22Sentinel%22]]: Interceptor voidcraft
 ** Typical callsign: ''Sentinel''

@@ Line 43: / Line 43: @@
 == Current Voidcraft Types in Use ==
-* [[GU-44_APC_%22Ochthera%22]]: Multi-role armored personnel carrier
+* [[GU-44 APC %22Ochthera%22]]: Multi-role armored personnel carrier
 ** Typical callsign: ''Crawler''
 * [[U-90_Interceptor_%22Sentinel%22]]: Interceptor voidcraft

@@ Line 43: / Line 43: @@
 == Current Voidcraft Types in Use ==
-* [[GU-44 Ochthera]]: Multi-role armored personnel carrier
+* [[GU-44_APC_%22Ochthera%22]]: Multi-role armored personnel carrier
 ** Typical callsign: ''Crawler''
-* [[U-90 Sentinel]]: Interceptor voidcraft
+* [[U-90_Interceptor_%22Sentinel%22]]: Interceptor voidcraft
 ** Typical callsign: ''Sentinel''

@@ Line 1: / Line 1: @@
-‘’‘Fleet Communication Protocols’’’
+'''Fleet Communication Protocols''' are the standardized naming and transmission procedures used by the [[Planetary Union]] Fleet in ''[[The Crypt]]'' series. These protocols help ensure clarity and coordination during ship-to-ship, fighter, and boarding operations — particularly in dense battlespaces or missions involving multiple capital vessels, voidcraft, and support teams.
-The Planetary Union Fleet employs a structured and scalable communication protocol to identify and coordinate voidcraft during missions. This system ensures clarity across multiple ships and squadrons, particularly in engagements involving dozens or even hundreds of combat assets.
+== Voidcraft Communications ==
-== Voidcraft Communication Protocol ==
+Fleet voidcraft such as the [[GU-44 Ochthera]] and [[U-90 Sentinel]] follow a standardized comms protocol based on class, origin, and mission type.
-This naming system governs all small craft operating from a larger capital-class vessel or base, including APCs, fighters, and interceptors.
-=== Standard Format ===
+=== Individual Operation Naming Convention ===
-	•	‘’’[Class] + [Local Number]’’’
+Used when voidcraft operate independently from a single capital ship or base.
-	•	Example: ‘‘Crawler One’’, ‘‘Sentinel Three’’
-	•	Used during low-traffic operations or when only a few craft are in the battlespace.
-=== Group Format ===
+* Format: <class> + <local number>
-	•	‘’’[Mothership/Base Code] + [Class] + [Local Number]’’’
+* Example: ''Crawler One'' (the first Ochthera assigned to the PUV ''Keeling'')
-	•	Example: ‘‘Crawler Kilo-Echo-One’’, ‘‘Sentinel Alpha-Kilo-Three’’
-	•	Required when operating in multi-ship environments or when call sign duplication is possible.
-	•	The mothership or base code is a two-letter abbreviation derived from the vessel or base name:
-** ‘‘Kilo-Echo (KE)’’ = [[PUV James Keeling]]
-** ‘‘Alpha-Kilo (AK)’’ = [[PUV Akathaso]]
-** ‘‘Golf-Whiskey (GW)’’ = [[Gateway Station]]
-=== Mission Suffix Format ===
+=== Group Operation Naming Convention ===
-	•	‘’’[Mothership/Base Code] + [Class] + [Local Number] + [Mission Suffix]’’’
+Used when voidcraft operate in task groups or multi-ship operations.
-	•	Example: ‘‘Sentinel Alpha-Kilo-Three Razor’’, ‘‘Crawler Kilo-Echo-One Needle’’
-	•	Used in high-density or carrier-based operations to designate specific mission roles.
-== Recognized Voidcraft Classes ==
+* Format: <mothership/base short code> + <class> + <local number>
-	•	‘’‘Sentinel’’’ — U-90 Interceptor (fighter)
+* Example: ''Crawler Kilo-Echo-One''
-	•	‘’‘Crawler’’’ — GU-44 Ochthera (APC)
+** "Kilo-Echo" is the short code for the PUV ''Keeling''
-== Mission Role Suffixes ==
+=== Mission-Based Suffixes ===
-	•	‘’‘Noise’’’ — Electronic warfare
+Suffixes indicate a voidcraft’s specific mission role in complex engagements. These are only used when multiple craft of the same class are operating with differing assignments.
-	•	‘’‘Carton’’’ — Troop transport and assault
-	•	‘’‘Dump’’’ — Mine-laying operations
-	•	‘’‘Needle’’’ — Troop transport for boarding actions
-	•	‘’‘Blast’’’ — Counter-air mission
-	•	‘’‘Jolly’’’ — Search and rescue (SAR)
-	•	‘’‘Razor’’’ — Deep penetration strike
-	•	‘’‘Shield’’’ — Counter-boarding / internal defense
-== Usage Guidelines ==
+* Example: ''Sentinel Alpha-Kilo-Three Razor''
-	•	Use the short form (e.g., ‘‘Sentinel Three’’) during basic operations or when only a few craft are in the battlespace.
+* Format: <base code> + <class> + <number> + <suffix>
-	•	Use the group format (e.g., ‘‘Sentinel KE-Three’’) when multiple capital ships are fielding similar craft.
+* Example breakdown:
-	•	Append a mission suffix only during high-intensity or carrier-style operations, where multiple mission roles are running simultaneously.
+** ''Sentinel'': Class name (U-90 Interceptor)
-	•	In radio communication, clarity is paramount. Use full call signs until the tactical situation permits shortening.
+** ''Alpha-Kilo'': Mothership short code for the PUV ''Akathaso''
-== Examples ==
+=== Mission Suffix Key ===
-	•	Low-density op: ‘’“Crawler One, you’re clear to launch.”’’
+These suffixes are only used in engagements with high craft volume or mixed-mission sorties.
-	•	Carrier environment: ‘’“Crawler Kilo-Echo-One Needle, maintain your vector for boarding operations.”’’
-	•	Combat air patrol: ‘’“Sentinel Alpha-Kilo-Three Blast, bandits inbound bearing zero-seven-zero.”’’
+* ''Noise'' — Electronic warfare
 [[Category:The Crypt]]
 [[Category:Planetary Union Fleet]]