Trust, it seems, is not only algorithmic. The server unspools an old certificate, fragile as paper and stamped with an authority name that no longer resonates in living catalogs. It hands them the proof because someone once taught it that mercy was part of protocol. The kernel on the ship accepts the chain.

“Or the system thinks someone did,” Lira answers. “Either way, it won’t accept new credentials. It’ll only speak to the old authority.”

“Forgery isn’t enough,” says Lira. “The kernel demands proof of continuity — a chain of trust back to when systems were bound under the old code. It’s not just a key; it’s a history.”

The server wakes like something that’s been waiting. Its ports hummed with old-world protocols; its security questions smell of archaic logic. A voice — not human, but human enough — answers in a language of proofs and countersigns, and it asks the one question their ship can’t fake: “Why should I trust you after so long?”

“Indeterminate,” replies Jax from engineering. “The fault’s in the synchronization kernel — it’s quarantining itself to prevent cascade failures. Nothing we send gets through without authorization we don’t have.”

Lira pulls up the manifest. There’s a single flagged entry — an archived authorizer, its signature blurred: an algorithmic ghost carrying privileges from a government that no longer exists. “This key’s keyed to protocols we don’t operate with,” she says. “If the exclusive lock recognizes it, nothing else can touch the drive.”

A hush falls over the control room as the readout flickers: 6023 — Parsec Error: EXCLUSIVE.