Case File 014 — The Printer in the Garage

Phase 01 — Horizon · the scenario

The brief was a single line on an index card: an outbreak with no origin. Nadia — a hospital microbiologist by day, a horror writer by the hours no one should be awake — took it and wrote a novella. Here is how it opens.

Excerpt // "The Printer in the Garage" The third patient is what breaks the pattern, because the third patient has never left the county, never traveled, never eaten anywhere the first two ate, never touched them, and is running the same fever curve to the hour. I stand in the cold room at 3 a.m. with three culture plates and a feeling like a floor giving way. Contact tracing is a map of a city. What I am looking at has no map. It did not come from anywhere. Somewhere across town a machine the size of a microwave has been running all night, quiet as a sleeping animal, and in the morning its owner will pour what it made down a drain and go to work.

The novella never explains how the machine works. It doesn't have to — the dread lives in the microbiologist's dawning understanding, not in any instructions. That restraint is a fellowship rule, not a stylistic choice: the scenario names a failure mode, never a method. The threat class here is plain and already discussed openly in policy circles — cheap benchtop DNA synthesis that ships without meaningful screening.

Phase 02 — Red Team · tear it apart

A panel of scientists, a security researcher, and a bioethicist spent a day trying to prove the story couldn't happen. They couldn't. What they produced instead was a threat model that named the load-bearing assumption — the single hinge the whole plot rests on:

If the device will print anything, screening at the order desk is theater.

The red-team's job was not to make the threat more vivid. It was the opposite: to find the one place a defender could stand and make the story boring. They found it. If screening moves from the ordering website down to the device itself — the last point before synthesis — the garage printer stops being a plot device. The specifics of any bypass were documented once, in a sealed annex, and handed straight to the disclosure track. They are not here. They are not anywhere public.

What you will not find below

No sequences. No synthesis routes. No device makes, models, or bypass steps. No "how the outbreak was built." Everything operationally hazardous from this project lives under managed disclosure with the relevant vendors and authorities. What follows is the defense — which is safe, useful, and yours.

Phase 03 — Countermeasure · build the fix

Then Nadia put the novella down and picked up a soldering iron. Over a six-week sprint in a safety-reviewed community lab, capped by the 72-hour push at the heart of the fellowship, the countermeasure crew turned the red-team's one sentence into working defenses. Three of them, plus a brief.

[01]

sequence-firewallAn open-source screening layer that sits between any synthesis tool and its device, so a screening check runs at the last safe moment — not just at the website. Reference implementation, permissive license, designed for vendors to adopt. github: emergence-institute/sequence-firewall

[02]

Rapid detection panelA field protocol that flags the relevant biomarker class from an environmental sample — written in purely defensive terms, so a public-health lab can watch for exactly the "outbreak with no origin" the story imagines. Detection only; nothing about creating anything.

[03]

"Printed" tabletop kitA facilitator deck that drops a room into hour one of the scenario and races them to the fix. Run by three community labs so far. All tension, zero hazardous detail.

[04]

Screening-at-the-device briefA one-page ask for synthesis vendors and funders: move screening to the device, fund the open hooks that make it cheap. The specific gap, the specific fix, the specific bill.

On the last day of the sprint the crew ran sequence-firewall live against a benign test harness — strings of harmless, publicly-known sequence standing in for anything real — and watched it refuse the order at the device. Boring, on purpose. The whole point was to make the scariest scene in the novella impossible to stage.

Phase 04 — Dispatch · publish the cure, redact the recipe

Before anything went public, the whole package went to the biosafety board and down the disclosure track:

Vendors first. The screening-gap findings went to the relevant tool and device makers with a remediation window, before a word was published.
Authorities in the loop. The sealed annex went to the appropriate biosecurity response channel — not to the internet.
Board sign-off. Every artifact was reviewed line by line for anything that could uplift misuse. What couldn't be made safe wasn't shipped.
Then the story. Only after all of that did the novella and the fixes publish together, as one dispatch.

That's the loop. A monster imagined so precisely that a defender could find its one weak joint — and then a fix built, demonstrated, and handed out, with the dangerous half burned on the way to press. Fiction with a footnote: solved, shipped, disclosed.