Editing Edom Terminal\Juridical

Not long before the [[Great Purification|firing]] of the [[Halo Array]] in [[97,445 BCE]], the [[Domain]] was unable to be accessed by the facility so a local loop cache for the facility was approved by someone called the Conditor. Shortly afterward 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 two hours before it would be overrun. This led to the local fleet assets being used up, making the [[Sentinel]]s have to engage the Flood landing crafts en route to [[Erde-Tyrene]]. The Flood then held position, leading to confusion. Command authority of the terminal was overridden by the Conditor for help involving the [[Knights]]. Connection was then lost to sector oversight. The Array was then fired. Edom control was then recovered from its archive, though its integrity check failed.{{Ref/Reuse|Catalog 2014}}

As some point there was an intrusion detected in site fractal. Later on, physical intrusion was detected in the facility's archival data center, leading to the facility alerting, but failing to, [[Builder Security]]. This led 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 forwarded to Builder Security, after which there was a physical intrusion detected in relay center rho. With relay center rho failing, Builder Security was alerted again. This time, emergency containment protocols were approved by the facility AI and entities translated as <nowiki>[burgarii]</nowiki>. This led to relay center rho self-destructing and becoming offline.{{Ref/Reuse|Catalog 2014}}

It is then noted in the logs that Builder Security has failed to update the site for an unknown amount of cycles.{{Ref/Reuse|Catalog 2014}} Rogue processes were then detected in tertiary storage, and a trapdoor related to the facility AI was used.{{Ref/Reuse|Catalog 2014}}

At some point there were 782 priority maintenance requests awaiting to be done related to the facility, relating to a critical plasma containment failure in secondary storage, the emergency [[slipstream space]] transportation conduits being offline, sentinel constructor cradles being inaccessible and sentinel control not responding, and that there was field integrity failure in sublevel nine with there being structural failures reported.{{Ref/Reuse|Catalog 2014}}

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 yottabytes, and failure in tertiary storage area beta with an estimated data loss of 0.6 yottabytes.{{Ref/Reuse|Catalog 2014}} This lack of maintenance ultimately led to 14819 overdue maintenance requests awaiting action.{{Ref/Reuse|Catalog 2014}}

On [[2558#March|March 3rd 2558]] a [[Catalog]] unit, after failing to contact the Domain, contacted the terminal. Learning that there was an intrusion in site fractal, it tried to alert Builder Security. Catalog stopped what it was doing to quarantine possible [[logic plague]] markers in an incoming message.{{Ref/Reuse|Catalog Data dump 1}} After clearing the quarantined info, the Catalog unit noted that it could not contact Builder Security about the intruder, while the facility AI reported acceptable conditions. However, the Catalog queued a request for a low-intensive military exploration of the facility. The Catalog unit was then locked out the installation and started a query to get back into it.<ref>[https://www.halowaypoint.com/en-us/forums/db05ce78845f4120b062c50816008e5d/topics/query-catalog-old/7fbf60e8-92f7-4826-ac2a-ab1b5e4e3603/posts?page=10#post100 '''Halo Waypoint''': ''Query: Catalog(old)'' (post 2960795)]</ref>

After Catalog finished its query it then the facility though node X.E8. It then proceeded to go though the facility's security logs to the present day, which went ignored by the facility AI.{{Ref/Reuse|Catalog 2014}}

This is a record of the security logs that the Catalog retrieved that the facility recorded.{{Ref/Reuse|Catalog 2014}}