CLASSIFICATION: RESTRICTED ACCESS — COMMAND STAFF OMEGA-2 CLEARANCE / NAVIGATOR SANCTUM ADDENDUM
++TRANSCRIPTION NOTE: The following report was dictated by Navigator Zephyr via holo-projection from the Navigation Sanctum, 847.M41, at the formal request of Judge Thorne (ref: Legal Requisition 447-V/Supplementary, filed under Lex Imperialis, Title IX, §3.2: Obligation of Specialist Officers to Provide Testimony in Matters of Vessel Security). Transcription by Ensign Daveth Morrn, Bridge Watch (Third). The Navigator declined three (3) invitations to review the final document for editorial correction. Non-standard commentary has been preserved at the Navigator’s insistence, over the transcribing officer’s reservations.++
++REDACTIONS APPLIED UNDER INQUISITORIAL AUTHORITY. DO NOT ATTEMPT RECONSTRUCTION.++
VESSEL: Incarnatus Mechanicus | DATE: 847.M41
INCIDENT TYPE: Detection Failure Analysis / Warp Translation Event — Supplementary to Boarding Action Reports (ref: Incident Report 127-GAMMA; ref: Boarding Action — Portside Sectors, filed 852.M41)
STATUS: RESOLVED (Tactical) / UNRESOLVED (Navigational)
REPORTING OFFICER: Navigator Zephyr, Navis Nobilite (Unaffiliated)
COUNTERSIGNED: Judge Thorne, Adeptus Arbites (Seconded under Warrant Authority)
MISSION CONTEXT
[NAVIGATION LOG — STANDARD ENTRY, 847.M41, ANTE-ENGAGEMENT]
The Incarnatus Mechanicus entered the Palladian Shoals at 03:17 Standard Shipboard Time on the date of the engagement, operating under Trade Route Security Order 1142-V, issued by the Warrant Holder. The vessel’s mission profile was the investigation of reported Freeboota activity disrupting commercial traffic through the Shoals — specifically, the disappearance of three independent freight haulers and one Administratum tithe-courier over the preceding seventeen Standard months.
Annotation [Z.]: “Voss had been watching the shipping manifests for months. Three missing freighters is a pattern. A missing tithe-courier is a statement. He wanted to know who was making it.”
The Palladian Shoals comprise approximately 1.2 million cubic kilometres of high-density asteroidal debris — remnants of a planetary body (designation unknown, pre-Imperial survey records inconsistent) distributed across a complex gravitational architecture. The region offers extensive sensor occlusion, numerous gravitational anchorages suitable for concealed vessel berthing, and natural warp translation points where local mass concentrations create stable Mandeville-adjacent zones.
Annotation [Z.]: “In plain language: it is a very good place to hide and a very easy place to jump in and out of the warp. Which is precisely why pirates love it and precisely why we were there.”
Navigation through the Shoals was conducted under the Navigator’s direct guidance, employing non-standard wayfinding techniques supplemented by the vessel’s archival stellar drift calculations (ref: Navigation Archive, pre-Imperial survey data, estimated age 14,000+ Standard years). Standard augur sweeps were maintained on continuous rotation throughout transit.
Annotation [Z.]: “The ship remembers this place. Her archives hold charts of these rocks from before the Imperium existed. The debris has shifted — fourteen millennia of orbital drift — but the deep gravitational architecture remains. I could feel her ██████████████████. She had been here before.”
DETECTION SEQUENCE
At 13:37 Standard Shipboard Time, the Navigator registered an anomalous psychic displacement in the local warp fabric, duration approximately 0.3 seconds, bearing 247-mark-012 relative to vessel heading. The disturbance was initially assessed as consistent with natural warp current fluctuation amplified by the Shoals’ gravitational complexity.
Annotation [Z.]: “This is where Judge Thorne would like me to say I failed to identify the threat. I will say instead that I identified a disturbance and assessed it correctly given available information. A 0.3-second psychic displacement in a gravitationally complex debris field is not, by any established navigational precedent, an indicator of imminent warp translation. It is noise. The warp is full of noise. My job is to separate signal from noise across an infinite frequency range while threading a fifteen-thousand-year-old vessel through a rock field at considerable velocity. I am very good at my job.”
At 13:40, vessel augur arrays registered multiple propulsion signatures on intercept trajectory. Signature analysis confirmed orkoid attack craft. Time elapsed between Navigator’s psychic registration and augur confirmation: approximately 180 seconds.
Annotation [Z.]: “Three minutes. They were in the warp, and then they were not, and then they were shooting torpedoes at us. Three minutes is an eternity in Navigator’s time. It was not enough.”
WARP TRANSLATION ANALYSIS
The following analysis is provided at the Reporting Officer’s specialist discretion and represents the Navigator’s professional assessment of the xenos approach methodology.
[NAVIGATOR’S ACCOUNT — DICTATED]
“What emerged at 13:37 was not a ship translating from the warp in any manner consistent with Imperial, xenos, or archival navigation methodology. I have served as Navigator aboard this vessel for fifteen years. In that time, and in the decades before it, I have observed ██████████████████████████ and once — at considerable distance — registered what I believe was ██████████████████. I have a reasonable professional baseline for anomalous warp events.”
“This was none of those things.”
“An Imperial vessel translates from the warp through calculated breach of the Gellar envelope at a designated Mandeville point, guided by Navigator or auto-systems. The process is controlled, predictable, and leaves a characteristic psychic signature — a thinning of the veil followed by a localised reality reassertion. It takes time. It announces itself.”
“What the Ork vessel did was arrive. The local warp fabric did not thin. It shattered. One moment the Immaterium in that bearing was turbulent but navigable — standard background agitation for a gravitationally complex region. The next moment, something was simply there that had not been there before, and the warp around it was screaming.”
Annotation [Z.]: “I need to be precise about what I mean by ‘screaming,’ because Thorne will want to know and because it matters. The warp is a medium of psychic energy. It responds to consciousness. When an Imperial ship translates, the local warp accommodates. It reshapes around the event, like water closing behind a stone. When this Ork vessel translated, the warp did not accommodate. It was ██████████████. The psychic displacement I registered was not the warp responding to a translation — it was the warp ████████.”
“The Ork vessel — subsequently identified through wreckage analysis as a modified Kill Kroozer of Freeboota configuration — emerged from the warp at a point approximately 4,700 kilometres from the Incarnatus Mechanicus. This is, for context, suicidally close. The standard minimum safe translation distance for a vessel of that mass is approximately 80,000 kilometres. The Orks either did not know this or did not care. Given my professional understanding of orkoid psychology, I suspect both.”
Annotation [Z.]: “I want it on the record that I am not being flippant. The Ork approach to warp travel is — and I choose this word carefully — ██████████. They have no Navigators. They have no Astronomicon. They have no Gellar fields worthy of the name. What they have is █████████████████████████████████ and somehow — somehow — that is enough. ████████████████████ ██████████████████████████████. It is ████████████████ and I do not enjoy thinking about it.”
AUGUR SYSTEM ASSESSMENT
The vessel’s augur arrays — [CLASSIFICATION LEVEL RESTRICTS TECHNICAL SPECIFICATION — noted as ‘pre-standard Imperial manufacture’] — performed within expected parameters throughout the engagement period. Augur systems are designed to detect and classify objects and energy signatures within realspace. They are not designed to detect objects in transit through the Immaterium, as such objects do not exist in realspace until the moment of translation.
Annotation [Z.]: “Thorne asked me, quite reasonably, why the augurs did not detect the Ork ship before it translated. The answer is the same reason a man standing on a beach cannot see a fish until it jumps. The augurs watch the surface. I watch what is underneath. And what was underneath gave me 0.3 seconds of warning before approximately eight thousand tonnes of angry green ceramite and scrap metal punched through the surface of reality at close range.”
The detection gap — the period between the Ork vessel’s warp translation and the augur confirmation of boarding torpedo launch — was approximately 180 seconds. During this window, the Ork vessel completed realspace materialisation, achieved fire-ready status, and launched eight (8) boarding torpedoes. The brevity of this window is assessed as the product of three factors:
1. Proximity of translation point. At 4,700 kilometres, the Ork vessel was already within extreme torpedo range at the moment of emergence.
2. Speed of orkoid combat readiness. The vessel launched torpedoes within approximately 120 seconds of completing translation — a response time consistent with a crew that was prepared for immediate engagement upon arrival, or that does not distinguish meaningfully between ‘arriving’ and ‘fighting.’
3. Sensor occlusion from asteroidal debris. The Shoals’ dense particulate environment degraded augur resolution by an estimated 15–20%, contributing to delayed classification of the emerging vessel’s profile.
Annotation [Z.]: “Factor two is the one that matters. An Imperial vessel translating from the warp needs time to recalibrate, to confirm position, to assess the tactical situation. The Orks needed no such interval. They came through the warp already fighting. I do not believe this was preparation. I believe it is simply what they are.”
NAVIGATOR’S ASSESSMENT — PROBABILITY OF PRIOR DETECTION
The Reporting Officer assesses that detection of the Ork vessel prior to warp translation was not possible through any augur system available to the vessel, regardless of specification or configuration. The vessel existed in the Immaterium until the moment of translation and was therefore invisible to all realspace detection methods.
Detection of the Ork vessel through warp-side observation was theoretically possible but practically unreliable. The Navigator registered a 0.3-second psychic disturbance consistent with — but not uniquely indicative of — imminent warp translation. In a region of complex gravitational interaction, such disturbances are common. Elevating this reading to a threat classification would require abandoning the vessel’s mission profile on the basis of every transient warp fluctuation in a region specifically characterised by such fluctuations.
Annotation [Z.]: “If I sounded the alarm every time the warp twitched in the Palladian Shoals, we would never stop running. The honest answer — and Thorne insists on honesty, though I suspect he would prefer a different honest answer — is that I could not have identified the threat in time. Not with certainty. Not with enough warning to evade.”
SUPPLEMENTARY ASSESSMENT — ON THE QUESTION OF COINCIDENCE
Annotation [Z.]: “This is the part Thorne did not ask for. I am including it because it needs to be somewhere, and an incident report filed under the Warrant’s authority seems as good a place as any.
“The Palladian Shoals are large. 1.2 million cubic kilometres of debris, gravitational complexity, and navigational hazard. The Incarnatus Mechanicus was conducting a systematic survey along a specific transit corridor. The Ork vessel translated from the warp within 4,700 kilometres of our position — not in the vast empty spaces of the Shoals, not at one of the dozen stable translation points my charts identified, but practically on top of us.
“There are two explanations. The first is coincidence. The Orks were operating from a concealed anchorage within the Shoals, as our mission profile predicted. They detected our presence through their own crude augur systems or scouts, retreated to the warp for a short tactical jump, and emerged in an attack position. This is the operationally sound explanation and the one I expect will satisfy the record.
“The second explanation is ████████████████████████████████ ███████████████████████████████████████████████████████████ ███████████████████████████████████████████████████████████ ███████████████████████████████████████████████████████████ Whether we were not simply found, but drawn toward. Whether the fist was aimed.
“I do not have evidence for this. I have a Navigator’s instinct honed over decades, and fifteen years of reading this vessel’s currents — currents that should not be readable. The warp does not operate on evidence. It operates on ████████.
“I am noting this for the record. I am not recommending action on the basis of it. I am recommending that if this vessel enters regions of known orkoid activity in the future, the Navigation Sanctum be consulted regarding local psychic conditions before committing to a search pattern.
“The fish jumped. We survived. I would like to understand why it jumped where it did.”
ORK VESSEL IDENTIFICATION (POST-ENGAGEMENT)
Subsequent analysis of debris recovered from the Ork vessel’s warp translation point and of boarding torpedo wreckage identified the following:
Vessel Class: Kill Kroozer (Modified), Freeboota configuration
Estimated Tonnage: 7,500–8,500 tonnes
Distinguishing Markings: Hull plates bearing crude glyphwork consistent with the “Blud Toof” Freeboota warband, previously reported operating in Subsector Palladia transit lanes.
Armament Profile: Torpedo tubes (confirmed), weapons batteries (probable), close-assault rams (standard for class).
Post-Engagement Status: The Ork vessel withdrew from the engagement zone following torpedo launch, sustaining no confirmed damage. Current location: unknown.
Annotation [Z.]: “The Ork ship ran. After it vomited eight torpedoes at us and presumably expected to return to collect the wreckage, it watched us kill everything it sent and decided to be elsewhere. Ork cowardice is widely considered impossible. I prefer to think of it as an excellent tactical assessment.”
Annotation [V.M.]: “The ‘Blud Toof’ warband matches three of the four missing vessel profiles from our original mission intelligence. We found our pirates. The engagement was not the investigation outcome I had planned, but the Emperor provides as He sees fit. Recommend continued patrol operations in the Palladian Shoals at a later date, in force. They have an anchorage in there somewhere, and I would very much like to find it.”
CASUALTIES
See primary engagement reports (ref: Incident Report 127-GAMMA; ref: Boarding Action — Portside Sectors, filed 852.M41). No additional casualties are attributed to the detection gap.
SUMMARY
An orkoid Kill Kroozer of Freeboota configuration translated from the warp at extreme close range to the Incarnatus Mechanicus during routine investigation of pirate activity in the Palladian Shoals. The warp translation was not detectable by standard augur systems and was registered by the Navigator only as a transient psychic disturbance insufficient for threat classification. The resulting 180-second detection gap between warp translation and augur confirmation of torpedo launch constrained but did not prevent effective defensive response by the Warrant Holder and crew, as documented in the primary engagement reports.
The Navigator assesses that no failure of systems or personnel contributed to the detection gap. The Ork vessel’s approach methodology — direct warp translation at suicidal proximity — falls outside all standard detection and evasion doctrines. Revised navigational advisory protocols for operations in regions of known orkoid activity are recommended.
Annotation [Z.]: “We were looking for pirates. We found them. They arrived by a method that no reasonable person would anticipate because no reasonable species would attempt it. The crew’s response — forty-eight minutes of preparation, sub-four-minute engagement, zero casualties — speaks for itself. I have nothing further to add, and I would very much like to stop talking into this transcription device now.”
FILED BY: Navigator Zephyr, Navis Nobilite (Unaffiliated) | COUNTERSIGNED: Judge Thorne, Adeptus Arbites (Seconded under Warrant Authority) | NOTED: Rogue Trader Voss Meridian, Warrant Holder
ARCHIVED: Imperial Standard Date 847.M41
++END REPORT++ | ++THE EMPEROR PROTECTS++ | ++STARS GUIDE THE FAITHFUL++
++TRANSCRIPTION NOTE: The Navigator’s request to title this document ‘Why I Could Not See The Fish: A Formal Complaint’ has been noted and denied per standard filing protocols. — Ensign Daveth Morrn, Bridge Watch (Third)++
++ADMINISTRATUM ROUTING: Received Sub-Office 771-Tertius, 853.M41. Catalogued: Supplementary Naval Filing, Vessel Incarnatus Mechanicus, ref. 847.M41. Routed: General Archive, Stack 14, Shelf 9 (appended to existing boarding action documentation). No queries generated. — Scribe-Adept Milus Fenk++
Tales from the Incarnatus Mechanicus 