The Night Watcher Who Stopped Rewinding
On a cold harbor balcony, a lighthouse keeper watches fog swallow the water. A ship shows up, then slips away. The keeper can’t hold the whole scene in mind, so a small logbook stays open on the rail. Takeaway, a steady little log can beat trying to stare at everything at once.
DNA feels like that foggy water, only longer. It’s a chain written with four letters, and it can run for millions. Many DNA readers act like a keeper who keeps looking back and comparing every ship to every other ship. That works for short nights, then slows down and gets shaky on longer ones.
Caduceus and Hawk try the logbook style. Each new DNA letter is like the next ship passing the light, and the reader updates the same fixed-size “log” instead of rewinding. The stream is the ships, the compact memory is the logbook, and carrying it forward keeps the reader oriented. Takeaway, reusable memory can stay steady as the line gets longer.
When they lined these readers up on the same DNA prediction jobs, the logbook style didn’t lose at normal lengths. Around twelve thousand letters, Caduceus often matched or beat a common rewind-heavy reader on several tasks. Hawk lagged on some tasks, so it wasn’t a clean sweep, just a different design staying competitive.
Then they stretched the input far past that usual length without special tuning. Caduceus could go from about twelve thousand letters to about one hundred twenty thousand with only small changes on several tasks. Hawk kept its variant-effect scores steady even as the input grew. The rewind-heavy reader tended to fall apart past its comfort zone, even with patches.
For ultralong DNA, they chopped the strand into chunks that fit, then carried the final logbook state into the next chunk, like one keeper handing the same log to the next shift. With that handoff, Hawk handled up to about a million letters on one high-end chip and stayed roughly steady on variant effects. The extra horizon didn’t automatically make answers much better yet.