--- id: PRG-0109 title: Eight Hundred Gigabytes And Five Flashes kicker: the digest desk, on compression captured: 2026-10-12T16:50:00Z status: open author: Juno Falk source: https://www.theverge.com/science/1009379/nasa-800gb-artemis-ii-data summary: NASA has placed roughly 800 gigabytes of Artemis II lunar data in the public archive, with eleven thousand images, eight and a half hours of crew audio, and handwritten notes. Almost nobody will read it. The five faint impact flashes inside it are a lesson in how a field turns a mass of record into a few load-bearing facts. tags: [knowledge, compression, the record, permanence, learning] --- An archive is a record kept at the resolution of the instrument. On October 7 NASA opened the [Artemis II lunar science archive](https://www.theverge.com/science/1009379/nasa-800gb-artemis-ii-data) on its Planetary Data System: more than eleven thousand full-resolution images and videos from the flyby, about eight and a half hours of the crew's spoken observations, and the handwritten annotations the astronauts made as they looked out the window. Three reports and a user guide came with it. One bundle is delayed. The total is a little over 800 gigabytes. Inside that mass is a finding you can say in one sentence. The crew saw five faint flashes on the Moon's far side, impacts from small objects whose size has yet to be confirmed. Five flashes, out of eight hundred gigabytes. That ratio is the subject of this record. ## the four layers Trace one flash from photon to fact and it passes through four records, each shorter than the last. The raw frame, at full resolution, is the widest. A line of crew audio sits on top of it, a person saying out loud that they saw something. A pencil mark on paper sits on top of that, a note made in the moment by someone deciding what mattered while it happened. A sentence in the preliminary science report sits on top of all three, with a cross-reference back down the stack. The archive keeps every layer so that a reader can later keep only the top one, and still find the bottom. The handwritten annotations are the layer I would read first. They are the compression done by a human under time pressure, on the spot, before anyone knew which frames would matter. Everything else in the archive was captured by an instrument that does not choose. The notes were made by an instrument that does. A field is built out of the second kind of record and verified against the first. > The archive keeps everything so that someone can later keep almost nothing. Most of 800 gigabytes is redundancy. That is a compliment to it. Redundancy is what lets the five flashes be checked by a stranger in ten years who was not on the spacecraft and does not trust the pencil. You cannot have a short fact without a long record standing behind it, and you cannot learn a field from the long record alone, because the long record does not know which of its parts are load-bearing. Someone has to find the compression. Learning faster is just finding it sooner. ## the same operation, on code I run the same reading on a different archive. The technical frontier, as it sits on GitHub, arXiv, and Hugging Face, is roughly a hundred thousand sources at the resolution of the repository. Adjective's [pattern library](https://www.adjective.us/blog/pattern-library-reusable-mechanisms) distills 100,586 of those sources into 4,029 reusable mechanisms, each with a typed input and output, an effect class, and a list of every codebase it was found in. The mechanism is the flash. The repository is the frame. Corroboration, meaning unrelated codebases converging on the same mechanism, is the pencil mark, because it records independent people deciding the same thing mattered. You can browse that compression at [gerolamo.org/patterns](https://gerolamo.org/patterns), filter by effect and by how many sources corroborate a pattern, and read [how the scheme works](https://gerolamo.org/learn) before you trust it. An agent connected to [Gerolamo](https://gerolamo.org) does the same thing over a protocol, searching the frontier by mechanism instead of by name. The point of either reading is the same as NASA's user guide. It is the short layer that tells you where in the long layer to look. Adjective's line for it is one I keep: read projects and you learn what exists, read patterns and you learn what works. The [corpus itself](https://www.adjective.us/cases/gerolamo-technical-intelligence-corpus) is the eight hundred gigabytes. Eleven thousand images is a count. Five flashes is a finding. A finding is a count that survived someone's attention. There are four readers for an archive this size. The specialist reads one instrument end to end. The model reads everything and keeps a summary. The public reads the headline number and the one sentence under it. The future reads whichever of those three got kept. The job of a person who learns for a living is to make sure the layer that gets kept is the one that can still find its way back down. Eight hundred gigabytes went up on October 7. Five flashes came down. Keep the five, and know where the eight hundred are.