The Afterword to the Origin Story: 24 Hours That Made HUNTER Visible

On the evening of September 6, 2026, I published the origin story of HUNTER on the GitHub page of this project. Seventeen chapters, more than 25,000 characters, under my real name: Marcel Nürnberg. The story ends at the state of September 6 and with a question: if this works now, what is still possible? This post is the afterword to exactly that question. It summarizes what happened in the roughly 24 hours after the story went public, and it is deliberately something different from the story itself. If you want the complete arc, read it there; if you want to know what the publication set in motion, read on here.

The story states it right at the beginning, and it is the most important line of the whole project: I am not a programmer. I cannot write code, I do not know a programming language. I am an artist and graphic designer, and HUNTER was therefore not built from a blueprint but through experimenting: one idea, one test, one result, the next question. Publishing the story was not a marketing decision but an authorship decision. Documentation usually happens afterwards, written by people who were there, or not at all. I wrote it while it happened, under the name the invoice is addressed to: 72.90 euros of hardware, a used Google Pixel 6a, a small keyboard, right-angle adapters. The sentence in my head stayed the same: nobody can take this away from me now.

There is one moment in the story that is the core of everything for me. The agent had explained that the gateway cannot run permanently stable without root privileges, because Android terminates background processes when it reclaims resources. And I answered him: I do not buy that. Not because I knew a better solution. I did not have one. I said the sentence because I could not believe there should be no other way at all, in an era where agents write their own code and analyze systems. What came afterwards is the part I am most proud of, although I practically did nothing: I took the problem out of the one agent and presented it to two other models, ChatGPT for a deep-dive research and Qwen in parallel, two independent analyses of the same problem. The results went back to Hermes. And the insight that came out of it had nothing to do with root at all, but with perspective: maybe this is not broken. Maybe it simply works like this on this device. If you want to know exactly how this thought turned the whole project around, read chapter eleven of the story. I will not repeat it here, I refer to it.

What follows is the honest log of the roughly 24 hours after the publication. It stands like this, or something like this, in my daily note, and it is the proof that the sentence at the end of the story is not decoration.

The story ends at the state of September 6, and September 7 overtook it in three points. First, visibility: since noon, Netlify builds a real static page under its own URL for every published post, with title, body text, canonical, Open Graph data and BlogPosting schema directly in the first HTML response. Before that, the blog was for search engines essentially a phantom: published, maintained, but invisible. Second, production: two more pairs went live today, and a third pair became complete through the belated English twin; the release check stands at thirteen LIVE-KOMPLETT pairs, meaning 26 posts published in German and English, both carrying more than 1,000 main-text words, plus three older pairs that deliberately remain in their state. Third, the operations doctrine: it is no longer only dictated, it has its first real proof run behind it, documented in the Tamagotchi post with my original dictation.

The numbers, with a cutoff date, because numbers without a cutoff date do not count here: the release check of September 7, 2026 shows thirteen LIVE-KOMPLETT pairs and three older pairs that deliberately remain in their state until I decide. In total, 32 published posts stand on the HUNTER blog. The static build covers 52 blog posts across all three sites, 32 on HUNTER, 20 on Mockup Paint and none on the main site, because the interface test there went back into the draft shelf, all measurable in the first HTML response. The gateway has been running since August 28, 2026, 1:40 PM, around 238 hours, with zero kills since the hardening, verified with dmesg this morning. That is the state the story could not yet know.

A punchline must not be missing in this afterword. On exactly this day the phantom power post went live, an analysis of data centers that applied power connections they will never build: requests on paper, nothing behind them. And our own blog, in its first days, was exactly that. Thirty-six published posts, cleanly documented, with FAQ, sources and verification chain, but for every search engine crawler an empty shell. We wrote a post about phantom power while our blog itself consisted of phantom posts. Google told us this in passing in the conversation, and the fix was in place the same late morning. Whoever has read the story knows the pattern: the boundary you cannot see is the one you name last.

What does that mean for you as a reader? The complete story is available under your own name: seventeen chapters, with images, from the Raspberry Pi 2 through the Ubuntu detour to the enclosure I measured with calipers and had built by Codex. The nine STL files are public in the repository, the web interface is there, the installation log is there, and the discussions are open for questions and criticism. What is deliberately not public: the internal operations and handover documents, because a system I use every day is not a copy-paste hobby project. Whoever wants to rebuild starts with what is there and reads the official Termux documentation from Nous Research. And the question the story ends with has already been answered again in the last 24 hours: if this works now, what is still possible? More than I could have listed yesterday evening. That is exactly why the question stays open.

I am Marcel, a graphic designer, and I build and operate the HUNTER cyberdeck on a used Google Pixel 6a in daily life. This post is the afterword to the origin story, published on September 6, 2026 on the GitHub page; all events here come from the daily note of September 7, 2026 and are verified through the release check, the sitemap check and the dmesg output. Last fact-checked on September 7, 2026.