Last day of the review period. Since Jeremy raised the question, the review for a specification is as initially submitted and posted; modifications are supposed to be in a change log in the subsequent draft submission. I know, a little bit of bureaucratic delay, but it does mean that everyone is looking at the same material. Since I’ve already given this a once-over for SSSF/MNP compliance prior to posting this, the review is going to be more a look at the specification as an RP environment.

For those unfamiliar, SNIP in this context (similar to how RP posts go) means I have nothing to say in regard to that part of the specification, so I don’t have questions to address or changes to recommend.

Posted by Fleet Captain Nicholas Villarreal (Assistant EDir. 1 & Dockmaster) in Sprecification Review: Empress-class Heavy Dreadnought
After some tweaks and modifications, this spec is compliant with SSSF and MNP. Everyone, please take a look and comment.

Two weeks for review, so the review deadline is 19 June 2026.

EMPRESS-CLASS
CATEGORY: DREADNOUGHT
VARIANT: HEAVY
DESIGNER: Patrick McGarry
Mark I
Draft 1
DATE: 4 June 2026
REFERENCED URLs: None
​
History And Mission Overview

SNIP
​

Structure And Construction
​The Empress-class utilizes a reinforced tritanium-duranium structural frame built around a triple-spine load-bearing architecture designed to distribute combat stress across the entire superstructure during sustained weapons discharge cycles.

There isn’t a lot of structural stress from energy-based weapons, and you’ve only got four torpedo launchers. You can probably exclude the last part of this sentence. Vessel combat is going to put stresses on the structure regardless; specifying it as being for weapons use seems unnecessary.

​The physical layout features a forward circular upper main section mated directly to an integrated, heavily armored aft engineering hull. This direct connection eliminates the traditional, vulnerable structural neck to maximize combat survivability. The propulsion system utilizes three asymmetric warp nacelles mounted along a ventral-dorsal offset arrangement (two lateral-swept attached to the aft hull, one dorsal-centerline), providing an imposing, high-tonnage profile optimized for combat field stability.

The sentence beginning, “This direct connection,” feels unnecessary. Sure, you’ve got a couple of canon vessels during this time frame that still have a separated engineering hull - California-class and Steamrunner-class, most notably - but in general, we’ve seen that standard Starfleet design is to not have a separate engineering hull as such (e.g. Sovereign, Intrepid, Nova, Inquiry, among others). A separate engineering hull is the divergence here, not the standard.

​Hull armor consists of 10.0cm ablative combat armor layered above a reinforced tritanium-duranium support lattice. Four internal interspatial cargo decks are included within the lower engineering hull; these sections are unmanned and entirely automated during normal operation.

This last sentence doesn’t belong in the structural section of the specification unless the cargo decks are larger than standard vessel decks. Staffing isn’t a consideration in construction, that’s a detail you include elsewhere.

Science And Remote Sensing Systems

SNIP.

I saw that you have GORBI-NX as an interface in the Technical Specifications section. I know you’ve addressed it elsewhere, but I wanted to emphasize that you need to detail it here. Seeing as the Trafalgar-class is where the original GORBI interface is found (https://www.star-fleet.com/library/museum/museummain/trafalgar/), I would recommend mentioning the Trafalgar, and why this latest iteration of GORBI, exists.
​

Warp Propulsion System

SNIP. I like the rationale behind the third nacelle, as well as the restriction on warp power in combat. Nice detail on vessel design balance.
​

Impulse Propulsion System

SNIP

Tactical Systems
​Defensive Shields

SNIP

Phaser Systems

SNIP

Torpedo Systems

SNIP

​Heavy Spinal P ser Lance

Spelling error, easy fix.

​The Empress-class mounts a single, fixed-forward heavy spinal phaser lance running heavy-graded primary structural spine of the vessel. This weapon design is derived from tactical telemetry of modified Galaxy-class fleet command variants (Ref: USS Enterprise-D, alternate timeline Stardate 47988). Unlike standard orbital strips, the lance utilizes a sequence of inline, high-capacity focusing crystals to discharge a tightly concentrated, continuous beam of pure energy.

​The weapon is designed exclusively for anti-capital ship engagements to penetrate heavy-grade hull armor. Due to the thermal and energy drain on the EPS grid, the spinal lance cannot be discharged simultaneously with maximum defensive shield reinforcement without a brief, automated cycling of secondary auxiliary power.

The Galaxy-class in question doesn’t exist in the Prime timeline, and therefore this point of reference is not actually a point of reference. I’m okay with the technology existing if you want to use it, but you need an in-character justification for the weapon; seeing it in “Yesterday’s Enterprise” is an out-of-character explanation that simply means that, as it appears in a canon work, we don’t necessarily need an accompanying technology submission.

Command And Support Systems
​Bridge

I’m having a little difficulty envisioning this fully. The Sovereign-class seems like a similar comparison, but that’s a tri-level setup, whereas this sounds like a two-level setup such as we see on the Galaxy-class and similar.
​
SNIP

Combat Information Center (CIC)
​Located deep within the armored core on Deck 2, the Combat Information Center provides complete tactical redundancy. The CIC is physically isolated from the primary Bridge by secondary automated bulkheads, ensuring the vessel maintains uninterrupted fleet command and internal defensive capability if the primary Bridge superstructure is compromised.

Deck 2 isn’t exactly a deep point in the hull. I get that it’s contained on the aft of the upper hull, in a hardened area, but that’s still pretty exposed for an area that’s supposed to be redundant.

Utility Systems

SNIP

Crew Support Systems

SNIP

Auxiliary Spacecraft Systems
​The primary launch and maintenance facilities span Decks 20 and 21. The standard auxiliary complement consists of 12 standard shuttlecraft, 4 tactical runabouts, 6 work bees, and a dedicated Captain’s Yacht integrated into the ventral hull.

That’s a lot of vessels crammed into one space, even if it does take up the whole of 2 decks, minus access corridors and utility space. I don’t think, even with the vessel dimensions that you have, that having as many auxiliary craft as an outpost for a non-carrier vessel is practical. It might not even be physically possible. Also, why does the captain have a personal vessel on a combat ship?

Technical Specifications

SNIP. Other than the GORBI-NX question, everything snipped is fine.

​Offensive Systems:
​Torpedoes
​Tubes
​4x Type-6 Burst Fire Launcher
​Standard Payload
​500 Total Casings (300 Quantum Torpedoes, 175 Photon Torpedoes, 25 Probes)

Change this into list format

​Phaser system
​18 Type-12 phaser arrays, 1 Heavy Spinal Phaser Lance

Put the Spinal Phaser Lance on a separate line

​Deck Layout

No glaring errors here, but please put all deck locations in list format instead of in-line format. Not sure how I missed this when I posted it; that’s on me.

Ships Of Class
​USS Empress, NCC-84900 (Class Ship)
USS Majestic, NCC-84901
USS Imperator, NCC-84902
USS Valiant, NCC-84904
USS Aegis, NCC-84905
USS Titania, NCC-84906
USS Resolute, NCC-84907
USS Invictus, NCC-84908
USS Vanguard, NCC-84909
USS Warlord, NCC-84910

If the specification is not allowed to use the Vanguard because it was an RP area, even with me as the designer who had it in the Maverick-class vessel registry, then the Titania also needs to be replaced. https://www.star-fleet.com/library/museum/museummain/Titania/

I’m also having some difficulty finding any sort of thematic coherence, which is somewhat typical of Starfleet vessels (the NX-class ships being named for space shuttles, Nova-class vessels being named after stellar terminology, the upgraded Novas being named after USA states, California-class vessels being named after California locations, Parliament-class ships being named after Canadian cities and provinces, etc.). Something to consider.

Conclusion

SNIP

​Submitted on 4 June 2026 by Patrick McGarry

Some concerns here and there to take care of, and I’m aware that some of them have already been addressed. The review period remains open through the end of the day.

Nicholas A. Villarreal
Assistant Engineering Director / Dockmaster