Install Go
The Lantern control room has gone silent at 02:17.
Choose an act on the map. Its Go chapters and story cases appear below.
Recover the first packets and learn why the dashboard cannot be trusted.
The Lantern control room has gone silent at 02:17.
A terminal on the dark relay keeps printing an unfinished greeting.
North Sluice's packet carries two counters: one for alerts created, one for alerts delivered.
A weak beacon repeats the same fragment until another station acknowledges it.
The maintenance channel contains packet fragments from several towers.
Imani lays out three kinds of record: a sensor reading, a human notice, and a relay receipt.
Ro reaches the North Sluice cabinet and tries a remote calibration.
The seven absent alerts were addressed to station codes, while Greyhaven's map uses neighborhood names.
Compare independent sources as the storm and the code grow less predictable.
Asha needs a copy of the warning draft, but the production transmitter is still suspect.
The port relay claims it forwarded every message.
Ro has minutes before the access road floods.
A live sensor and a backup radio now offer conflicting gate positions.
Imani finds an unlabelled envelope in an older archive.
Parallel searches return contradictory versions of the same event.
The search for the override's author fans out across slow archives.
Reconstruct the override, its author, and the true state of the sluice.
Halden's authorization record refers to an old storm protocol by a Roman-numeral revision.
Ro radios that the gate's mechanical dial is partly visible through spray, but its photograph is skewed.
The port office sends a local archive on removable storage.
Asha prepares an internal incident brief.
Three archives use different record types but the same chronological search pattern.
The timeline is complete, but Asha still needs one concise answer: which districts received a valid warning, and which did not?
Test the warning path before anyone relies on it.
The team's repaired logic passes its unit tests, yet the old Lantern still loses a warning when several parts run together.
One successful district is insufficient.
A mocked transmitter says the dispatch code called Send, but that does not prove a receiver could read the message.
The emergency code works, but it contains duplicated routing decisions and a special case added during the night.
Build a reliable public warning service for Greyhaven.
Asha approves a temporary public alert ledger.
The new ledger needs a reachable address.
The plain status page is readable, but district devices need structured data and a stable route.
Warnings arrive from several sources.
Asha needs the public server running while Imani imports another archive.
The tide forecast moves forward.
The new escalation logic passes when run alone and fails occasionally in the full suite.
The gate's physical status changes as Ro works the manual release.
Preserve evidence and make the system safer for the next storm.
After the storm, an inquiry asks Imani to decode a proprietary recorder file.
The inquiry discovers that several old dashboard errors were all displayed as “unavailable.” Operators could not tell a...
An archive reader can hang while fetching a damaged remote file.
Residents continue using the public ledger after the emergency.
At the inquiry, Asha is asked why her team trusted a new service built during a storm.
Greyhaven keeps the ledger, and a new maintenance team inherits its tests.