13 // EVANGELIUM THE SPREADING · CONTENT STRATEGY
This project is content-shaped. Build in private and post once at the end, and you lose 90% of the reach. Document every phase as it happens and turn the build itself into a recurring cadence. The Phoenix algorithm rewards replies and dwell time — build threads, not single tweets.
X / Twitter cadence
- Day 1 (Phase 0 launch): a 6-tweet thread. Hero photo: donor Game Gear + reproduction shells, calipers visible. Headline: "I'm rebuilding a Game Gear into a local LLM coding oracle. Targeting 30-50 tok/s. 4-button UI. Offline-first. Build log starts now."
- Per phase: one anchor thread when a milestone hits (breadboard talks, PCB arrives, first boot in shell). Each thread: 4–8 tweets with photos.
- Weekly: a small "shop note" — one photo, one observation, one open question. Asking questions juices replies, which juice algorithm reach 75×.
- Reply-mode: spend 2× the time replying to people who reply to you than you spend posting. This is your authority loop.
YouTube approach
- Three videos. Not more, not less.
- VIDEO 1 · "Why I'm putting an AI inside a Game Gear" (Phase 0): 4–6 minutes. The thesis, the donor disassembly, shells on the bench. Hook: handheld + AI + retro is irresistible.
- VIDEO 2 · "The brain works (breadboard)" (end of Phase 1): 6–8 minutes. Live demo of breadboard talking, model running, button mapping working. The skeptic-converter.
- VIDEO 3 · "It boots." (end of Phase 5): 8–12 minutes. The full v1 launch. Cold boot → real coding task → close shut → walk outside → still working. The one that gets shared.
Personal site (evanhawkins.com or timechaintech.com)
- Dedicated build-log page. All phases, photos, schematics, STLs, dockerfiles open-sourced. Y2K chaos.
- RSS so the technical audience can follow without algorithm intermediation.
- One long write-up at the end (~3000 words). The canonical reference. What gets cited on Hacker News.