Project Rift

Division Details

Sleeper Technology
Ticker	ST
Leads	Cicaedis Pritchard
Archivists	Unknown
Status	Active
Channel	AJ: ST
Staff
Research	Vanneth Deckard, Kivvic, Gehen Sealbreaker, Wyke Mossari, Renee Khalida, Rhavas
Contributors	Akasha Prime, Hilen Tukoss, Renee Khalida

Formerly: Discovering Spatial Rifts

Summary

Examine, gather data and understand the spatial rift phenomena, including both long-standing examples and recent items associated with entities including the Awakened Infomorph. If possible acquire, acquire or create a rift generation device.This project is being run by the Sleeper Technology division.

Introduction

A spatial rift surrounded by a sundered superstructure.

A spatial rift in a derelict stargate. Whether or not the rift was caused by a stargate malfunction is unknown.

A spatial rift at the Sansha Command center in Saminer.

Drafted by Vanneth Deckard.

Spatial rifts have littered the cluster for as long as any can remember. Often they stand as an unapproachable display; surrounded by the ruins of a space station, or an ancient configuration of stones. Speculation into the cause of these phenomena ranges from some catastrophic explosion that sunders the fabric of space, to spontaneous appearance that ruins whatever it opens on.

The truth has not warranted intense investigation in the past. However, several recent events have dredged the rifts back into scrutiny. The sudden surge in Sleeper activity and their use of spatial rifts to attack capsuleer residents of w-space is of concern to security. The appearance of an Awakened Infomorph in apparent harmony with the appearance of a spatial rift in known space is of particular interest to the Arek'Jaalan project, given the variety of speculation into the nature of the entity.

An unprecedented aggression by Sleeper drones on a starbase.

Therefore, spatial rifts are of interest to Sleeper Technology. This project will investigate the physics responsible for these largely undefined phenomena. Recent retrieval of ship sensor data provides the opportunity to study the physical effects of traversing spatial rifts.

Related projects:

• Project Gateway
• Talocan Interstellar Drive Technology
• The Pathfinder Program

Experiment Outline

Decipher ship sensor data and provide comparative analysis to sensor data acquired from traversing wormholes, activating jump gates and jump portals (capital and covert), and static space. Results may indicate the physics responsible for the apparent space-tunneling effects.

With sufficient results, we may be able to extrapolate the possibilities of how a spatial rift is formed, giving further insight as to the capabilities of Sleeper technology.

Research Aims

• To determine the physics governing spatial rifts
• Lay groundwork for future project exploring the generation of spatial rifts

Literature Review

• Discovering Spatial Rifts
• Faster-Than-Light Travel - How? [1]
• The Principles of Jump Gate Technology [2]

Methodology

Phase One: Sensor Logging

Acquire a wide range of ship sensor data.

Spatial Rift Data

An interactive spatial rift among a swarm of rogue drones.

Data is available from the vessel involved in a classified mission for the Sisters of EVE, and from a recent expedition to a Arek'Jaalan: Rogue Drones anomaly designation Rogue Trial Yard where a spatial rift was observed, tested, and entered on YC113.08.05 by a team of Voidstalker Arbiters.

• Sensor logs from Operation: Chasing a Nightmare
• Sensor logs from the Drake-class battlecruiser Lictor
• Sensor logs from the Hurricane-class battlecruiser Katrina
• Sensor logs from the Myrmidon-class battlecruiser Street Shark
• Sensor logs from the Blackbird-class cruiser Blue Sky

Static Space Data

Log data for Arbiters while idle in static space to begin control. Logs will be taken before and after the variable gathering. Additional logs will be taken from different ships of the same class as the ones involved with the spatial rift for control purposes.

• Sensor logs from the Drake-class battlecruiser Lictor
• Sensor logs from the Hurricane-class battlecruiser Katrina
• Sensor logs from the Myrmidon-class battlecruiser Street Shark
• Sensor logs from the Blackbird-class cruiser Blue Sky

Warp Drive Data

Log data for Arbiters when activating vessel warp drive systems. Before and after logs will be used, as well as logs from control ships.

• Sensor logs from the Drake-class battlecruiser Lictor
• Sensor logs from the Hurricane-class battlecruiser Katrina
• Sensor logs from the Myrmidon-class battlecruiser Street Shark
• Sensor logs from the Blackbird-class cruiser Blue Sky

Wormhole Data

Log data for Arbiters when passing through a standard, randomly generated natural wormhole. Before and after logs will be used, as well as logs from control ships.

• Sensor logs from the Drake-class battlecruiser Lictor
• Sensor logs from the Hurricane-class battlecruiser Katrina
• Sensor logs from the Myrmidon-class battlecruiser Street Shark
• Sensor logs from the Blackbird-class cruiser Blue Sky

Stargate Data

Log data for Arbiters when transported by unmodified stargates. Before and after logs will be used, as well as logs from control ships.

• Sensor logs from the Drake-class battlecruiser Lictor
• Sensor logs from the Hurricane-class battlecruiser Katrina
• Sensor logs from the Myrmidon-class battlecruiser Street Shark
• Sensor logs from the Blackbird-class cruiser Blue Sky

Acceleration Gate Data

Log data for Arbiters when transported by unmodified acceleration gates. Before and after logs will be used, as well as logs from control ships.

• Sensor logs from the Drake-class battlecruiser Lictor
• Sensor logs from the Hurricane-class battlecruiser Katrina
• Sensor logs from the Myrmidon-class battlecruiser Street Shark
• Sensor logs from the Blackbird-class cruiser Blue Sky

Jump Drive Data

Log data for a capital ship transporting itself via jump drive.

Jump Portal Data

Log data for ships passing through a standard capital jump portal and a Black Ops covert jump portal.

Phase Two: Comparative Analysis

Once all data is acquired, analyze and compare sensor logs regarding the physical effects of the transportation process caused by spatial rifts.

Control: Sensor logs relating to known phenomena: Static space, wormhole, stargates, acceleration gates, jump portals, and jump drives. Each has a set of known physics governing it.

Variable: Sensor logs from vessels exposed to spatial rifts will be analyzed for irregularities when compared to any control group. Astrometrics data, exotic particles, abnormal hull stresses, shield fluctuations, sensor interference, euclidean warping will all be looked for and documented.

Hypothesis: Spatial rifts are governed by hyper-euclidean mathematics. If proven, it may suggest a clearer relationship between Sleepers and Talocan.

Data Assessment

Results of sensor log analysis will be examined and compared by experienced physicists of several fields. Experts in Astrometrics, Quantum Physics, Electromagnetic Physics, Graviton Physics, Jump Portal Generation, Sleeper Technology and Talocan Technology will apply their respective expertise to the assessment.

Time Frame

Phase One

• Acquire Spatial Rift Data (complete)
• Acquire Static Space Data (awaiting control ship logs)
• Acquire Warp Drive Data (awaiting control ship logs)
• Acquire Wormhole Data (awaiting control ship logs)
• Acquire Stargate Data (awaiting control ship logs)
• Acquire Acceleration Gate Data (awaiting control ship logs)
• Acquire Jump Portal Data - mid August
• Acquire Jump Drive Data - mid August

Phase Two

• Analyze all sensor logs - late August
• Complete comparison - early September
• Publish results - early September

Budget

• Fuel for two Covert Cynosural Field generations
• Fuel for two Covert Jump Portal generations
• Fuel for four standard Cynosural Field generations
• Fuel for two Jump Drive activations
• Fuel for two standard Jump Portal generations (contingent on a Titan being available to the project)