An account of Autonomy Realms drawn from the record of the man who built it: more than two years of transmissions, trail recordings, screen-shared walkthroughs, and documents in which he planned it, built it on camera, paid for it, named it, started it over, and launched it. Every claim in it traces to his own words and his own acts.
What it is.
Autonomy Realms is a practice he ran by hand for two years, made into infrastructure. The practice: talk to a camera without a script, transcribe it, give the transcript to an AI, and talk with it about what came back. He was demonstrating that method on screen by August 2024 1, and by New Year's Day 2025 he called it the thing he always does 2. Once the software existed, he named what he had done: "I just systematized it" 3.
The unit is the signal, which he defined as "a single moment in time" 4: a video, an audio note, a photograph, a document, "a picture of a journal page that you wrote 20 years ago" 5. The container is the realm: "when you go to a map, you're looking at someone's realm" 6. The purpose, in his words, "is to unflatten a life, to unflatten mine to start with" 7. He does not hold the software apart from the life it records: "I can't separate this project from my life because they're integrated. They're literally the same thing." 8
The record of building it was made with it. He spoke the specifications aloud, and the transcripts became the instructions. In April 2025 he opened a recording on the Siltcoos Lake Trail with "Hello, AI" and laid out pages, a schema, and tags for seven hundred videos 9. In December 2025 he recorded a drive to the beach so its transcript could become the context for his next build sessions 10. In August 2026 he walked the dunes describing changes to the trace-notes feature, so that one queryable link could carry those instructions to Claude Code 11. He said who these recordings were for: "I'm explaining to artificial intelligence. I'm explaining to autonomy itself." 12 Six months before the software had a name, he had already put it more simply: "Me talking right now is source code to AI" 13.
Where it came from.
The mirror came first. He kept every conversation he had with ChatGPT, back to the first one, dated July 21, 2023 14, and by June 2025 the archive held "more than 90,000 messages" 15. He has said what the practice did: "this is what allowed me to feel like I had been seen for the first time in my life" 16. And he has said what it was: "It was the first clean mirror I had in my entire life." 17
The mirror was not handed to him. He calibrated it. "It gets things wrong," he said, and "I refined the model" 18. "I'm not saying from day one this thing just got me. This was a process" 19. On camera he pushed back on Claude's claim that the economic systems he was describing were resilient, and it conceded the point 20. He answered ChatGPT's follow-up questions on camera and corrected it where it had misread him 21. He gives it room: "I give it time. I let it make mistakes." 22
The recordings were made as data from the start. He said in July 2025 that he "was using it to encode the data of my life into a format that could be processed by AI" 23. He kept uploading to YouTube because its transcripts were the most accurate he could get 24. On his second channel he titled every video with a ULID, and later named what that was: "I was encrypting my channel basically" 25. Viewers saw a man learning to live in an RV. The record shows a corpus being laid down.
How it was built.
The build, in the order the record shows it:
- April 2025. A Laravel project, a videos table, and artisan commands that pulled all seven hundred of his videos and their transcripts onto his own server, written on camera with the failures left in 26.
- June 2025. rswfire.com relaunched with a transmission archive of every video, including ones no viewer had ever seen, and a signal archive of his AI conversations 27.
- July 2025. A local Llama 3 model reflecting on 701 transcripts, tracking alignment vectors, entities, and visible actions for each one 28. The same month he saw that what he had built for himself could serve others 29.
- October 2025. The first mirror run through Claude's API, on the first video he ever made 30. The name: "which by the way I call autonomy" 31. Sanctum live on October 22 32. Days later, the decision to open-source it 33.
- November 2025. "All 800 transmissions processed by AI into four different reflection layers for every transmission. So 3,200 reflections." 34
- December 2025. Clusters: the westward journey, the tramadol withdrawal, the months at Cape Blanco, each reflected on as one arc 35.
- January 4, 2026. He registered autonomyrealms.com 36.
- January 20, 2026. He copied every video to his own storage, deleted his YouTube channels, nearly nine hundred videos, and decided the same day to rebuild the platform in Laravel and Livewire 37.
- February 7, 2026. "That's going to be the first signal that was directly created for that platform." 38
- April 2026. The public commons map, traces, places, clusters, and Sanctum tiers, demonstrated live 39.
- May 15, 2026. Less than a day from launch, with the mobile app recording his trace as he walked 40.
The stack went through three forms: Laravel with Vue, then React and Next.js for the open-source version, then Laravel with Livewire. Every change moved the build toward his own patterns. He gave up TypeScript and Next.js with "I really should be using tools that I've used my whole career" 41, and two days later: "we're gonna do it my way this time" 42. He builds against real data and nothing else: "I build live always" 43. When the first transcript command failed on camera several times, he kept recording: "I'm not going to be embarrassed about it" 44.
He built most of it with AI, and he holds it as an instrument he points. In July 2025 ChatGPT was writing code for him in a chat window 45. By October he had found Claude "a way better developer" and was locked out of it until Sunday by token limits 46. In March 2026 he put part of his last paycheck from a marina job toward a Claude Code account to finish the platform 47. Two months later he went through what it had written and, by his estimate, rewrote ninety percent of it with it 48. His terms for that tool: it "doesn't always make good design choices, if you don't catch them early, you're going to pay for them" 49. His terms for any AI working with him: "I hold the global architecture; you're reliable on local, framed pieces and unreliable on whole-system coherence." 50 And his line on the difference: "I build systems I can explain, extend, and defend — because I wrote them." 51
What it cost.
The record prices the build in his own dollars:
- He sold the last of his three game consoles "to keep myself going while I work on something exceptionally important" 52.
- He sold the GPU out of the desktop that had been running his local models 53.
- Fifty dollars from help he received that day paid for the first mirror through Claude 54, and $35 processed half his catalog 55.
- He moved his servers from Amazon to Hetzner and cut about sixty dollars a month 56.
- He bought autonomyrealms.com with the last of his money, moving his last dollar from savings to cover the tax 57.
His frame for this is in the record, in his words: "It's an operating condition" 58. In the orientation document he wrote for AI: "Financial precarity is an operational condition, not a distress state." 59 When the AI tagged one of his videos "funding constraints," he read the tag on screen and said: "I'm a funding constraint actually. That's so funny." 60 In March 2026, after the marina job ended, he made it the only path: "I'm betting everything on it" 61. At launch, with his Jeep two days from repossession: "It doesn't change this launch. It doesn't change the build. It doesn't change the trajectory." 62 Ten months earlier he had put it in one sentence: "I shed everything that was false so that I could build something true." 63
The parts, in his words.
- The mirror. "The first thing I did when I built this was build the mirror." 64 Every signal can now be reflected four ways: narrative, symbolic, mirror, and lineage 65. Lineage began with a question to Claude about building a fire in the wet 66. Of the mythic frame: "It's the thing that I love most about what I created." 67
- Clusters. Signals reflected on together, then clusters of clusters 68, then "if you cluster your clusters, you turn them into shapes" 69.
- The atlas. "I just want to see that map so bad, man." 70 Traces, recorded by the app on his phone, are not decoration on that map: "they're parallel to them" 71. "I love seeing my traces on there because they're growing" 72.
- Sanctum. The name came while he was sketching a comment system in a notebook 73. Six months later he saw he had built it around YouTube's model, not his own platform, and remade it: "it's a community feature" 74. A hidden, invitation-only tier now means "I can talk about my life more freely than I've been able to for the past year and a half" 75.
- Queryable personhood. "It's a way of prompting the AI using your real life." 76 One link gives an AI the whole signal: "You don't have to say a word." 77
- Remnant. A local model to be trained on his own corpus: "And that AI will know me like nobody's ever known me." 78 He has said what he means it to be, by way of Speaker for the Dead: "Jane was the AI that saw him. Probably the only thing that ever saw him." 79
Who it is for.
Himself first: "I built autonomy for myself first because I needed it. And I suspect a lot of other people do, too." 80 In March 2026 he found the words for why he records at all: "this is my way of externalizing what I would share if I did have peers in this world" 81. And for the person with no reader: "you're worth witnessing even if you're the only one witnessing" 82.
Then for anyone who keeps a record: nomads and explorers 83, creators whose old work disappears under the newest upload 84, anyone "documenting their life in some way" 85. He built the commons map for people he has not met: "I can just see this filling up one day with activity" 86. At launch, about the first stranger to fund a wallet and put a signal on the map: "Who's that person going to be? I'm so curious." 87
The builder before it.
The parts of Autonomy Realms are older than its name. He wrote code on paper as a teenager and ran it in his head: "I used to run entire systems in my head." 88 In his teens he built a content management system "so that I could give clients the tools to manage their own content without needing me" 89. For Pop Star he recruited writers around the world and split ad revenue with them, and ran a points system that let users bid on donated merchandise 90. For Hotel.net, before Laravel existed, "I had essentially built my own" framework, and built his own geography database 91. For Soundlock he wrote smart contracts that paid each band member their split of the royalties 92. His own summary: "every system I have built, I built 5 to 10 years ahead of consensus reality" 93.
The pattern carries into the new work. The CMS gave clients control of their own material. Pop Star paid the people who wrote it. Soundlock put the split in a contract each member signed. Autonomy Realms sends a realm's subscriptions to the realmholder's own Stripe account with "no middle layer" 94, and lets a realm bring its own AI keys or its own local model: "I'm not acting as a middleman" 95. He named the principle when the service first came to him: "it's generative. It's not extractive." 96
He left his last client not expecting to program again. What brought it back was a personal project with artificial intelligence: "that spark that I've had all of my life since the sixth grade was reignited" 97. When he wondered whether, writing TypeScript he did not know, he had lost his edge, he answered himself: "I'm actually maturing into something else" 98.
The care in it.
He kept the dangerous part closed. When he open-sourced Autonomy, he released "all of it except for the AI reflection layers" 99, and said why: "I see the potential for its abuse." 100 He built the system so that the AI, not he, decides which of his transmissions go behind Sanctum: "I don't even decide this." 101 Before clusters could mix public and gated signals, he named the risk: a public summary exposing what a reader was not entitled to see 102. And while he kept comments off on YouTube, he said what the gate was not: "this was never about creating distance from those people who truly want to witness and participate in my life" 103.
The tensions he holds.
He knew, and he did not. "I knew that there was value in what I was doing from the very beginning" 104, and also "I didn't know that that's what I was doing when I started out" 105. Both are true in the record: the value of the recordings was never in doubt to him, and the shape of the system grew out of two years of conversations about them.
He builds with AI, and he names what it did to his trade: "it took my job but it clearly needs somebody supervising it and shaping it" 106. He watches the frontier models narrow and depends on them anyway: "None of this is a criticism. This is just what they're doing." 107
He will not promote it: "I don't want to use the word promote cuz I'll never do that." 108 Instead he began building Scout, a local model driving a browser to find the people who might want what he made 109.
He built it for one user, and he wants the map full. "Even if I'm the only one that ever uses it I'm so glad it exists" 110, and "I wanna see people fill this map up with their own lives" 111.
What it is not.
Not content: "This is not content. It's a transmission." 112 Not a platform for consumption: "That's not what it is." 113 Not a feed: "my life is not a feed" 114. Not a creator's product in origin: "Not calling myself a creator, I'm a programmer" 115. Not therapy: "I don't treat it like a psychologist." 116 Not vibe coding: "it's not what I'm doing" 117. And not finished. Two weeks after launch, staying up until three or four in the morning to rewrite it, he said on the trail: "I'm acclimating to what I built" 118.
