Laphisto
High Commander of the Lilaste Order
OUT OF CHARACTER INFORMATION
Intent:To codify and document the comprehensive defense network known as the Bastion Curtain—a territory-spanning strategic initiative enacted by the Diarchy and enforced by the Lilaste Order and DAF forces to secure and fortify Diarchal-controlled space following the Sartinaynian Crisis. While also making a severe obstacle that invading forces must breach before they can make ground fallCanon:
N/A
Permissions:
N/A
Links:
- [Diarchy Faction]
- [Lilaste Order]
- [Sartinaynian Crisis]
- [Planetary Guns]
- [ODP platforms]
- [Inner Curtain Stations]
- [Frontier Sations]
GENERAL INFORMATION
Name:The Bastion Curtain Reformation
Reform Type:
Military / Strategic Defense Reformation
Reform Passage:
Diarchal Decree B-17, issued by High Commander Laphisto and Diarch’s Rellik and Reign, ratified unanimously by the Diarchal Council following the Sartinaynian Crisis.
Description:
The Bastion Curtain Reformation is a comprehensive militarization and defensive restructuring effort designed to create an unbroken wall of fortifications, fleet patrols, and planetary defense networks surrounding all Diarchy-controlled space. Conceived as a direct response to the near-catastrophic invasion of Bastion during the Sartinaynian Crisis, the Curtain marks the single largest military infrastructure initiative in Diarchal history.
Spanning every sector under Diarchal jurisdiction, the Bastion Curtain integrates orbital defense platforms, fortified shipyards, planetary mass driver networks, and rapid-response fleets into a seamless, self-sustaining perimeter grid. Its purpose is twofold: to deter large-scale incursions from foreign empires and to ensure any force breaching the perimeter faces overwhelming, layered resistance at every level—from border space to the planetary surface.
The Curtain’s philosophy is simple: make invasion impractical, attrition inevitable, and sovereignty absolute.
SOCIAL INFORMATION
Notable Figures Involved in the Reform:- High Commander Laphisto – Supreme architect of the Bastion Curtain. Oversaw structural doctrine, logistical standardization, and military execution under the authority of the Lilaste Order. His leadership solidified the reform into a unified defense policy across all sectors.
- Diarch’s Rellik and Reign – Co-signatory of Decree B-17 and primary advocate for total militarization following the Sartinaynian Crisis. His political influence ensured unanimous ratification by the Diarchal Council.
- Commander Julian Tarain – Advisor on planetary defense logistics and siege doctrine. Authored the Tarain Line Model, the framework for integrating ground-to-orbit artillery into the Curtain’s layered defense approach.
. - The High Admiralty – Established patrol doctrine and fleet dispersal protocols, ensuring each region within the Curtain maintained autonomous but interlinked defense capabilities.
Public Reception:
The announcement of the Bastion Curtain divided public sentiment across Diarchy space. Among the populace of Bastion and neighboring systems, it was heralded as a symbol of strength, unity, and survival the physical embodiment of “never again.” To those who had witnessed the devastation of the Sartinaynian Crisis firsthand, the construction of the Curtain was viewed as a necessary sacrifice, one that traded mobility for security and liberty for endurance.
Within the government and military, the reform was near-universally praised. High-ranking officers viewed it as a long-overdue modernization of the Diarchy’s defensive structure. Civilian leaders, while concerned about economic strain, acknowledged the psychological and strategic need for deterrence. The curtain promised not merely protection but control.
Outside Diarchal space, observers noted the rapid militarization of border systems and a quiet but unmistakable shift in tone among Diarchal envoys measured, resolute, and unwavering. While few dared comment openly, whispers circulated throughout the greater galaxy: the Diarchy had become a fortress state, its will embodied in steel and silence.
For the people within, however, the Bastion Curtain was not seen as isolation it was safety, identity, and endurance made manifest. Behind its watchful guns and gleaming stations, the Diarchy stood unconquered.
EVENTS
Event Name:The Sartinaynian Crisis
Participants:
- Diarchy Delegation
- Diarchs Rellik and Reign
- Bastion Defense Command
- Lilaste Order
- High Commander Laphisto
- Opposing Forces
- Empire of the Lost
- Dark Empire Contingent Forces
Overview:
The Sartinaynian Crisis marked the baptism of fire for the newly unified Lilaste Order under the banner of the Diarchy—a devastating conflict that erupted mere days after their formal induction. What began as a gesture of alliance and mediation became a test of loyalty written in fire across the skies of Bastion.
The Order had entered the Bastion system as part of a diplomatic escort, accompanying Diarchal envoys to finalize the terms of mutual defense and integration. The objective was peacekeeping symbolic of a new era of cooperation between the Diarchy’s core worlds and the Lilaste frontier fleets.
Without warning, one of the Empire of the Lost’s capital ships broke formation and unleashed a full orbital bombardment on Bastion’s surface. In minutes, the planetary defense grid was annihilated. Thousands perished as shockwaves tore through the capital’s lower districts, obliterating every orbital gun and anti-orbit platform before the planetary shields could cycle online.
Even as the Diarchal fleets scrambled to regroup, a second hostile formation emerged from hyperspace—vessels bearing the crimson insignia of the Dark Empire. Whether a coordinated betrayal or an opportunistic strike remains unknown, but the result was catastrophic: two enemy powers descending upon Bastion simultaneously, turning the capital system into a battlefield.
The Lilaste Order, still operating under provisional command structure, immediately joined the defense. High Commander Laphisto ordered his ships to break diplomatic standby and engage, forming a defensive wall between the retreating Diarchal fleets and the invading forces. In the chaos, the Order’s cruisers and carriers absorbed the brunt of the opening volleys, their intervention preventing the total destruction of Bastion’s evacuation lanes.
The battle lasted only hours, yet its intensity reshaped the Diarchy’s future. The combined defense of Diarchal and Lilaste forces drove both aggressors into retreat, though at immense cost—half the orbital fleet destroyed, every planetary gun silenced, and much of Bastion’s surface reduced to scorched wasteland.
When the firing ceased, the capital stood wounded but unbroken. In the aftermath, Diarchs Rellik and Reign addressed the surviving forces, with High Commander Laphisto at their side. Their message was simple and resolute:
"The Diarchy endures—not through isolation, but through unity. Never again will Bastion or any world protected by the Diarchy stand undefended."
From that vow emerged the Bastion Curtain formation, a complete overhaul of Diarchal defense doctrine. The Sartinaynian Crisis had proven one thing beyond all doubt—peace without vigilance was an illusion, and unity without strength was a death sentence.
HISTORICAL INFORMATION
Standardized System Template — Finalized Disposition
To ensure consistency and mutual support across thousands of star systems, the Diarchy adopted a single standardized template for each system within a sector of the Curtain. These templates were binding; local governors could adjust minor details based on terrain, but the core counts and hierarchies were fixed.Per-System Base Template (Interior Systems / Standard Systems):
- LO-DIA ODP (Outer Defense Platforms): 400–500+ per system, arrayed in overlapping belts and Lagrange clusters. These provide the layered, first-contact detection and interdiction network.
- Tro’khil-Class War Forge Station MKII: 6–8 per system (interior systems), serving as mid-tier command, repair, and light production hubs. Tro’khil stations coordinate ODP sectors and support local fleet operations.
- Local Defense Fleet (per system):
- 1–2 Heavy Cruisers (capital patrol / area denial)
- 3–5 Frigates (escort, interdiction)
- 6–12 Corvettes (interdiction, rapid response)
- Auxiliaries & Logistics (tenders, tankers, repair barges)
- LO-DIA ODP: 600–800+ (concentrated on inbound vectors)
- Tro’khil-Class Stations: 1–2 (forward Tro’khils, hardened and optimized for resupply)
- Forgepoint-Class War Station: 1 per border world — the sector anchor. Forgepoint functions as the principal command, capital yard, and last defensive bastion for its sector.
- Local Defense Fleet (per border system): same basic structure but generally higher readiness and increased corvette counts for picket duties.
- LO-HV-MD (Ground-to-Orbit Hypervelocity Mass Drivers): 30–50+ per planet, sited to create overlapping approach denial fields. Emplacements placed on elevated terrain, coastlines, and fortified mountain ranges; some moons host mobile or secondary batteries.
- Planetary Defense Garrisons: multiple PDC hubs and missile stores to support LO-HV-MD operation, maintenance, and ammunition manufacturing.
Forgepoint & Tro’khil Distribution Notes
- Tro’khil-Class War Forge Station MKII: Interior systems received 6–8 as a steady backbone. Border systems retained 1–2 forward Tro’khils designed to be highly survivable, with rapid detachment capability to re-route supplies and host regional patrols. Tro’khils functioned as both repair yards and fire-control relay nodes for local ODP clouds.
- Forgepoint-Class War Stations: One Forgepoint anchors each border world. A Forgepoint is an orbital fortress city: command citadel, full capital shipyard, magazine stores, and regional administrative offices. Forgepoints also host regional reserve fleets and act as distribution centers for mass-driver ammunition and heavy ordnance.
LO-DIA ODP Grid — Deployment & Employment
- Purpose: The ODP fabric is the Curtain’s sensory and immediate engagement layer — automatically targeting incoming corvettes, boarding craft, and missile barrages while relaying tactical data to Tro’khils and Forgepoints.
- Density & Redundancy: With 400–500+ ODPs per system, the grid’s redundancy means the loss of hundreds of platforms still leaves an effective interdiction net. ODPs are semi-autonomous — low crew counts, high automation — designed to be saturated rather than invulnerable.
- Integration: ODPs integrate targeting feeds into Tro’khil coordination centers for multi-platform salvo routing and into planetary PDCs for integrated ground-to-orbit firing solutions.
LO-HV-MD (Planetary GTO Mass Drivers) — Tactical Role
- Count: 30–50+ per planet.
- Function: Fixed, hardened ground emplacements deliver hypervelocity kinetic rounds into low orbit — capable of disabling or destroying medium and heavy ships and denying orbital staging areas. Multiple batteries coordinate timed salvos to produce overlapping kill envelopes; planetary defenses are the Curtain’s last line before ships can approach atmosphere or attempt boarding operations.
- Logistics: LO-HV-MD munitions are mass-produced at Forgepoint foundries and stockpiled in planetary depots. Each battery requires extensive maintenance teams, electromagnetic capacitors, and precision guidance arrays.
Fleet Distribution — Local and Patrol Fleets
Local Defense Fleets (System Level):- Designed to hold while reinforcements arrive. Typical composition: 1–2 Heavy Cruisers, 3–5 Frigates, 6–12 Corvettes, and logistical vessels. Local fleets are trained in coordinated defense with ODP volleys and LO-HV-MD firing windows.
- Each patrol fleet’s area of responsibility encompassed 3–5 systems. Patrol fleets are intentionally mobile: they rotate along pre-planned corridors to maintain presence, intercept incipient incursions, and respond to fast transits.
- A regional patrol force typically consists of: 2–4 Cruisers, 6–12 Frigates, 12–24 Corvettes, plus a small carrier contingent for fighter wings and logistics tenders. Patrol fleets can surge to a threatened system within hours using pre-coordinated jump points and forward Tro’khil supply nodes.
numbers.
Regional Patrol Fleet Ship Complement (per patrol fleet covering 3–5 systems)
Standard Patrol Fleet (peacetime / routine rotation)- Capital Ships: 1
- Cruisers: 2
- Frigates: 6
- Corvettes: 12
- Support / Logistics Vessels: 3 (repair tender, fuel tanker, resupply barge)
- Total hulls (approx): 24
Reinforced Patrol Fleet (heightened alert / contested sector)
- Capital Ships: 2
- Cruisers: 3
- Frigates: 8
- Corvettes: 18
- Support / Logistics Vessels: 5 (2 repair tenders, 2 tankers, 1 ammo barge)
- Total hulls (approx): 40
Strike-Ready Task Force (immediate surge / offensive posture)
- Capital Ships: 3
- Heavy Cruisers: 2
- Cruisers: 4
- Frigates: 6
- Corvettes: 12
- Assault Transports / Landing Ships: 4 (for boarding and planetary operations)
- Support / Logistics Vessels: 6 (repair & ammunition tenders)
- Total hulls (approx): 54
Reinforcement Doctrine:
- Trigger: Local fleet reports hostile engagement and requests assistance.
- Response Window: Regional patrol fleet aim to respond within 3–8 hours to ensure massing of force before an attacker establishes siege or orbital superiority. Forgepoints can dispatch reserve squadrons or rapid repair tenders for immediate support. Reinforcement fleets are also called in from nearby sectors - if the attacked sector is a border/ Frontier world then local defense forces from inner curtain systems are called in to provide rienforcements
- Escalation: If multiple systems are engaged simultaneously, CBDC authorizes sector-wide mobilization, activating reserve fleets and enacting deeper Curtain responses.
Industrial & Logistical Realities
- Production Output: Yearly targets required hundreds of ODP hulls, multiple Tro’khil stations, and continuous LO-HV-MD battery fabrication. To meet demand, the Diarchy implemented shift-work across planetary yards, prioritized ore allocations, and conscripted civilian foundry workers under state direction.
- Supply Chains: Forgepoints served as primary production hubs for heavy ordnance; Tro’khils handled mid-tier repairs and quick turnaround; local PDCs maintained ammunition stocks for planetary batteries.
- Training & Manning: Massive recruitment and accelerated training produced crews for ODP maintenance, Tro’khil engineering, and LO-HV-MD operation. Command staff trained under integrated war games to coordinate cross-domain fires.
Doctrine Codification & Standard Operating Procedures
- Curtain Doctrine Manual standard engagement protocols, ODP prioritization rules, LO-HV-MD salvo synchronization procedures, and regional reinforcement plans.
- Curtain Drills: Annual full-scale exercises involving simulated multi-vector assaults tested inter-system coordination and logistics under stress.
- Fail-Safe Protocols: Tro’khil and Forgepoint stations possess autonomous defense subroutines and hardened command redundancies to maintain operations should primary CBDC links be severed.
Outcomes & Strategic Effect
- After four years of intensive construction and doctrinal maturation the Bastion Curtain achieved initial operational capability across most frontier sectors. The Curtain transformed the Diarchy from a state vulnerable to surprise strategic strikes into a region where large-scale invasion required overwhelming, sustained investment unlikely to succeed without catastrophic attrition. The combination of dense ODP belts, robust Tro’khil support, Forgepoint anchors, planetary LO-HV-MD arrays, and mobile patrol fleets ensured that the Diarchy’s borders were no longer lines on a map but active, lethal space.
Last edited: