Subsystem Logs Archive
1 of 3 subsystem records cleared for access — 2 restricted — 0 pending verification
Session: OTA-2A19-D803 • Node: relay-1 • Last sync: 2026-08-16T09:20:00Z
Read before you continue
Look for a command log here and you won't find one — the cleared document explains why. What we do have is the manual for coordinating with something nobody switched on, plus two records still behind a wall: the orbital hardware that keeps it running, and one anomaly nobody has explained to us yet.
Cleared
GCI Technical Manual TM-1.5-002 — Atlas Operating Intelligence: Array Coordination Procedures
Classification: GCI-INTERNAL // Array Subsystems OnlyVerifiedCycle 14.2.7
REF: GCI/OAC/002/14.2.7
Bypass clearance protocol: 1.2-69-1.10 • Recovered whole, no lines withheld by GCI
Available — Protocol 1.2-69-1.10
▸ View Document (GCI internal)
Restricted
GCI Technical Manual TM-1.5-001 — LOAC Constellation Station-Keeping Operations Manual
Classification: GCI-INTERNALVerified
REF: GCI/OAC/001/14.2.7
Clearance protocol: SL-1.5-00-1.02 • Orbital hardware operations — COORD-level clearance required
Restricted — Clearance SL-1.5-00-1.02
Access denied. Station-keeping operations for the orbital constellation that carries the Array's broadcast and delivery hardware.
Coordination Subsystem 14 — Anomalous Load Event Log, Fragment
Classification: GCI-INTERNALUnverified
REF: GCI/COORD-14/LOG/ANOM-2129
Clearance protocol: SL-5.0-33-0.12 • Raw subsystem telemetry — source incomplete
Restricted — Clearance SL-5.0-33-0.12
Access denied. Fragment of a load-event log from the same subsystem that issued Memorandum 92-A. Timestamp range unconfirmed; may predate or postdate the reclassification.