| # | FILE | WHAT IT IS / WHERE THE ROUTE HIDES |
|---|---|---|
| 01 | militech.html | Public site / entry. Click the dull Antarctica map marker → cinematic diagnostic glitch → login. |
| 02 | militech_login.html | Session-recovery login. Answer 5 public-fact identity questions → recovered project index link. |
| 03 | antarctic_operations.html | Polar black-project index. Every project card opens a modal; route is concealed ONLY in the BLACK KEEL project modal → Related Records. The // 04 logistics panel no longer carries the link (text points players to open the BLACK KEEL card). |
| 04 | antarctic_logistics_movements.html | Logistics movement DB (twin: procurement_mirror.html). BRITISH ACQUISITIONS tab: every hull row EXPANDS; route = expand the HMS Vanguard row → 'OPEN FULL ASSET RECORD' inside the expansion. Other rows expand to 'no record compiled'. |
| 05 | vanguard_asset_record.html | Capital asset profile. // 03 ARMAMENTS: all 13 systems open identical spec popups; route is concealed in the ELECTRONIC WARFARE SUITE popup (a REFIT item) → 'OPEN DOCK AUTHORITY RECORD' (it names berth NC-MB-DK). No schematic marker. |
| 06 | norcal_military_docks.html | Dock authority. // 02 BERTH STATUS: all 8 berths open identical popups; the route to the docked vessel log is concealed in the NC-MB-DK berth popup (Vanguard's berth) → 'DOCKED VESSEL LOG'. CLUES: the NC-MB-04 berth popup (Judas's berth) carries the S1 account + B1; // 04 DOCK OPERATIONS → BERTH ACTIVITY & RECORDS panel carries D4. |
| 07 | norcal_docked_ship_logs.html | Dock-log DB. Route: expand the // 02 CLASSIFIED BLOODHOUND row (Attachment Status: RECOVERABLE) → 'RECOVER MOVEMENT ATTACHMENT'; 4 decoys are SEALED. CLUES: // 01 expand the USS Judas 2023.09.18 row for G2 (bundle); // 03 USS JUDAS VESSEL DOSSIER tabs — IDENTIFICATION holds E1 (platform short-code), SERVICE HISTORY holds H3 (operation tag). The BLOODHOUND classified row itself no longer carries any clue. |
| 08 | classified_movement_login.html | Hacking minigame (6 stages). Solve to infer + type the final credentials → attachment. |
| 09 | classified_movement_attachment.html | Recovered movement record. // 04 ARCHIVE CROSS-REFERENCE lists several archive refs, all 'RESOLVE'; only BLOODHOUND/PRE opens (pre-action report). The rest toast SEALED/CLASSIFIED. |
| 10 | operation_low_tide_pre_report.html | Pre-action report (doc viewer). RELATED FILES tab lists several related files, all 'RESOLVE'; only BLOODHOUND/POST opens (after-action report). The rest toast SEALED. |
| 11 | operation_low_tide_after_report.html | Sealed after-action report. Fully redacted. Reveals nothing. End of chain (back link only). |
| QUESTION | ANSWER |
|---|---|
| 01 · Founding year | 1996 |
| 02 · Founder | Antonio Luccessi (“luccessi” accepted) |
| 03 · First NUSA infantry contract year | 2004 |
| 04 · NUSA standard rifle | Ronin LAR (“ronin” accepted) |
| 05 · Preferred procurement partner | Lazarus Group (“lazarus” accepted) |
Pick MTI-BLUEWATER-DOCK-07 (the BLUEWATER DOCK operator at berth NC-MB-04). Trap: MTI-POLAR-LOGISTICS-07 also ends 07 but is logistics, not a dock account. Other decoys: VANGUARD-REFIT-12, NORCAL-AUTH-44, ANTARCTIC-MOVE-03.
Hidden at: norcal_military_docks.html — // 02 BERTH STATUS → NC-MB-04 berth popup (USS Judas transfer berth), in the same sentence as B1: “all movements through this berth are filed under the dock’s standing operator account”
Click only these 6 grid coordinates (everything else is decoy noise and is rejected):
| COORD | TOKEN REVEALED | WHERE IT IS HIDDEN (interactive — must open/expand) |
|---|---|---|
| B1 | BLUEWATER | norcal_military_docks.html — // 02 BERTH STATUS → open the NC-MB-04 berth popup (USS Judas transfer berth); in its operator-account sentence (with the S1 account) |
| E1 | JUDAS | norcal_docked_ship_logs.html — // 03 USS JUDAS VESSEL DOSSIER → IDENTIFICATION tab → INTERNAL SHORT-CODE field |
| C3 | 2023 | norcal_docked_ship_logs.html — // 02 BLOODHOUND classified row (x-c0) → ERA field (“Fourth Corporate War · 2023”) |
| G2 | V44 | norcal_docked_ship_logs.html — // 01 RECENT BERTH ACTIVITY → expand the USS Judas 2023.09.18 row; at the end of its dock detail (the bundle’s own log line) |
| D4 | NC-MB-04 | norcal_military_docks.html — // 04 DOCK OPERATIONS → BERTH ACTIVITY & RECORDS panel; in the berth-assignment ledger prose (NOT in a berth popup) |
| H3 | BLOODHOUND | norcal_docked_ship_logs.html — // 03 USS JUDAS VESSEL DOSSIER → SERVICE HISTORY tab → end of the archived-movement note |
Confidence rises as stages complete: 18 → 41 → 66 → 89. At 89 (all four stages done) the final credential entry unlocks.
Assemble in order: JUDAS → V44 → BLOODHOUND (vessel short-code → notice bundle index → operation name) = JUDAS-V44-BLOODHOUND. Wrong order resets. Decoys: NCMB, BLACKKEEL, DOCK07, BLUEWATER, VANGUARD.
Order hidden at: norcal_docked_ship_logs.html — // 03 USS JUDAS VESSEL DOSSIER → BERTHING tab (movement references read: vessel, then notice-bundle, then operation)
Match each recovered record to its role (decoys: recon vessel / orbital program / tidal code / submarine):
| RECORD | ROLE |
|---|---|
| 2023 | Movement year / era |
| USS JUDAS | Operating platform / launch ship |
| NC-MB-04 | Berth code |
| V44 | Notice / cache bundle index |
| BLOODHOUND | Classified movement attachment |
Login 1 (militech_login.html) is a session-recovery gate using public Militech facts — quick identity confirmation to enter the internal index.
Login 2 (classified_movement_login.html) is the hard, multi-stage recovery minigame that requires cross-referencing the records players gathered along the route. The final credentials are never shown — they must be inferred.