Edom Terminal\Juridical: Difference between revisions
From Halopedia, the Halo wiki
(Ok that is article made. Can please someone error check for me. This article was not the easiest for me to make. Considering those Security logs were a pain.) |
m (→Sources) |
||
| Line 73: | Line 73: | ||
{{Forerunner|array}} | {{Forerunner|array}} | ||
[[Category:Forerunner buildings]] | [[Category:Forerunner buildings]] | ||
[[Category:Mars | [[Category:Mars Locations]] | ||
Revision as of 23:57, February 10, 2016
The Edom Terminal/Juridical, is a Forerunner Juridical listening post on Mars. This facility's AI is called 4096.[1]
History
Not long before the firing of the array in 97,445 BCE. The Domain was unable to be accessed by the facility so a local loop cache for this facility was approved by someone called the Conditor. Shortly after there was a containment failure at the Maginot line. This led to the facility losing connection to ecumene control, ecumene oversight, and quadrant oversight. Star road activity was then reported, leading to the Flood parasite in Mars airspace giving the facility an estimate 2 hours till it gets overrun. This leads to the local fleet assets being used up, making the Setinels have to engage the flood landing crafts em-route to Erde-Tyrene. The Flood then hold position. Leading to confusion. Command authority of the terminal is overridden by the Conditor for help involving the Knights. Connection is then lost to sector oversight. The array is then fired. Edom control is then recovered from it's archive. Though its integrity check failed.[1]
As some point there is an intrusion detected in site fractal. And later on physical intrusion was detected in the archival data center in the facility. Leading to the facility alerting, but failing too, Builder security. This leading to priority site emergency containment protocols needing approval by Builder authorities. Unauthorized constructs were detected in the archival data center and Cyber-intrusion response logged 9204 unauthorized constructs unraveled. The construct spoor was forwared to Builder Security. There was then an Physical intrusion detected in relay center rho. With Builder security alerted again, with that failing. This time emergency containment protocols were approved by the facility AI and someone called bugarii. This led to relay center rho self-destructing and becoming offline.[1]
It is then noted in the logs that Builder Security has failed to update the site for an unknown amount of cycles.[1]
Rogue processes are then detected in tertiary storage. And a trapdoor related to the facility AI is used.[1]
At some-point there was 782 priority maintenance requests awaiting to be done related to the facility. Things related to these maintenance requests was a critical plasma containment failure in secondary storage, the emergency slip stream space transportation conduits were offline, sentinel constructor cradles were inaccessible and sentinel control was not responding, and that there was field integrity failure in sublevel nine with there being structural failures reported.[1]
The lack of the plasma containment maintenance, in the storage area, led to failure in tertiary storage site alpha with an estimated data loss of 3.2 yotabytes, and failure in tertiary storage area beta with an estimated data loss of 0.6 yotabytes.[1]
This lack of maintenance ultimately led to 14819 overdue maintenance requests awaiting action.[1]
On November 18th 2552 terminal/Juricidal recorded an anomalous slip-space intrusion in Mars airspace.[2]
On March 3rd 2558 a Catalog unit after failing to contact the Domain contacted the terminal. Learning that there was an intrusion in site fractal. So it tried to alert Builder security. Though fearing the logic plague from a user on the Waypoint community, the Catalog Unit stops what it is doing to quarantines it.[2]
After clearing the quarantined info. The Catalog unit notes that it cant contact Builder security about the intruder. And the Facility AI reports acceptable conditions. Though the catalog queues a request for a low intensive military exploration of the facility. The Catalog unit is then locked out the Installation. And starts a query to get back into it.[3]
After the Catalog finished its query it then entered though node X.E8 in this facility. The Catalog then proceeded to go though the facility's security logs to the present day. The facility AI then proceeds to ignore the Catalog.[1]
Security Logs
This is a record of the security logs that the Catalog retrieved that the facility recorded.[1]
[BRANCH] [WARNING] \\sysdiag\security\log\[apparitor] [ALERT!] Critical reconciliation errors detected in security logs. [spurious-data/no_ref] X.E8> [in ordine] [ALERT!] Critical failure: Unable to access Domain [interlink]. Local loop [cache] approved by [conditor]. [ALERT!] Fleet command alert: Containment failure at [Maginot] line. [ALERT!] Connection lost to ecumene [control]. [ALERT!] Connection lost to [ecumene oversight]. [ALERT!] Connection lost to [quadrant oversight]. [ALERT!] [star road] loci activity flux reported [ERR,REGRESS] [hours] ago. [ALERT!] Parasite [classis] detected in Edom [airspace] [ERR,REGRESS] [hours] ago. Estimate position overrun in 2 [hours]. [ALERT!] Local fleet assets expended. Sentinel [fundibalarii] engaging landing craft en-route to Erde-Tyrene. [ALERT!] Parasite [classis] holding position. Threat dynamic analysis ongoing. [ALERT!] Override authority granted by [conditor] for [eques] and [auxilia] [suscitatio]. [ALERT!] Connection lost to [sector oversight]. [ALERT!] [slip stream space] activity de^()!(*#&////// <entry corrupted> [ALERT!] Edom [control] recovered from archive. Integrity check failed. [ALERT!] Intrusion detected in site [fractal]! Builder Security alerted. [ALERT!] Physical intrusion detected in archival [datacenter]. Builder Security alerted. [ALERT!] Builder Security [vigiles] cannot be contacted. [priority site] emergency containment protocols require approval by Builder authorities. [ALERT!] Unauthorized constructs detected in archival [datacenter]. [cyberintrusion] response logs 9204 unathorized constructs [unravelled]. Construct [spoor] forwarded to Builder Security. [ALERT!] Physical intrusion detected in relay center [rho]. Builder Security alerted. [ALERT!] Builder Security [vigiles] cannot be contacted. Emergency containment protocols approved by facility [AI] and [burgarii]. Relay center [rho] self-destruct successful. Relay center [rho] offline. [ALERT!] Builder Security has failed to [refresh] for [ERR,REGRESS] cycles. [WARNING] Rogue processes detected in tertiary storage. trapdoor.4096/non-auth [WARNING] [exemption error] Log errors: [fieri non potest] X.E8> break [WARNING] \\sysdiag\maintenance\log\[apparitor] [ALERT!] 782 priority maintenance requests awaiting [action]. [ALERT!] Critical [plasma] containment failure in secondary storage imminent. [ALERT!] Emergency [slip stream space] transportation conduits offline. [ALERT!] Sentinel Constructor cradles inaccessible. [ALERT!] Sentinel [control] not responding. [ALERT!] Field integrity failure in sublevel nine. [vix lumine] structural failures reported. [WARNING] [plasma] containment failure in tertiary storage site [alpha]. Data loss estimated at 3.2 [YB]. [WARNING] [plasma] containment failure in tertiary storage site [beta]. Data loss estimated at 0.6 [YB]. [WARNING] 14819 overdue maintenance requests awaiting [action]. \\sys\analysis\error : [error]
Sources
