{
  "$type": "site.standard.document",
  "canonicalUrl": "https://kohopeh.com/blog/the_ghost_in_the_machine",
  "description": "A look at the tech-minded heart of Kohōpeh, from Astro and Cloudflare to the AT Protocol and the AI ghost helping pull the levers.",
  "path": "/blog/the_ghost_in_the_machine",
  "publishedAt": "2026-04-05T00:00:00.000Z",
  "site": "at://did:plc:uegcbc2rfvudyawyn7zlaku5/site.standard.publication/3miiejufsbd2c",
  "tags": [
    "architecture",
    "writing",
    "tools",
    "atproto"
  ],
  "textContent": "1. The Goal: A Living Archive\n\nKohōpeh isn't just a website; it’s a living archive and a central hub for a sprawling fictional universe. My historical and \"steam-fi\" fiction requires more than just a place to dump text. It needs a structure that can handle deep lore, complex character arcs, and multi-serial narratives across different eras—from late Sengoku Japan to 16th-century Thailand to the future of star-spread humanity.\n\nThe site serves as the definitive source for everything I build, ensuring that readers can dive into the research and the world-building as much as the stories themselves. The intent is sharing.\n\nConclusion: Of course, my ultimate goal is to grow the readership of my books, one lore-obsessed reader at a time.\n\n---\n\n2. The Foundation: Astro & Cloudflare\n\nIn choosing the foundation, I went for a performance-first approach. Astro was the natural choice. It allows for a modern component-based architecture while delivering zero-JavaScript by default. This is critical for a content-heavy site where the story should always load faster than the analytics. Especially since I didn't add analytics.\n\nFor hosting, Cloudflare Pages provides the edge delivery I need. It’s fast, reliable, and handles global distribution without the headache of managing a server. It’s the stability a writer needs when their mind is already full of 16th-century politics.\n\nConclusion: The fact that the sum of these costs is exactly zero has, of course, nothing to do with the decision.\n\n---\n\n3. The Source: Markdown & GAG\n\nI believe in the power of flat text. Every piece of content on this site starts as a Markdown file. Why? Because Markdown is portable, human-readable, and future-proof. There is no CMS lock-in here. If I want to move my archive tomorrow, I just copy the files.\n\nBut managing hundreds of files, complex tags, and deployment pipelines can become a chore. That’s where GAG (my nickname for Google Antigravity, the AI agent assisting me) comes in. GAG helps with the heavy lifting—refactoring code, managing metadata, and ensuring the site's plumbing stays leak-free. It brings \"Developer Joy\" back to writer-maintenance.\n\nConclusion: Let GAG handle the syntax and the deployment scripts; it leaves me more time for important authorial tasks, like staring out the window and calling it \"world-building.\"\n\n---\n\n4. The Lore Mine: Consistency at Scale\n\nOne of the unique features of this site’s architecture is \"Lore Mining.\" As I write my books, some of them over 200,000 words in rough form, I need a mechanism to keep track of every character, location, and historical detail.\n\nI’ve built tools to extract these elements from my project files and surface them directly on the site as snippets, character profiles, and location guides. This ensures that the world readers see on the site is always in sync with the world I’m currently writing.\n\nConclusion: Narrative control is one thing, but keeping a sprawling set of universes and characters from staging a mutiny against my memory is quite another.\n\n---\n\n5. Entering the Atmosphere: AT Proto & Sequoia\n\nPublishing shouldn't stop at the edge of my website. I want my blog posts to be first-class citizens of the social web. Therefore, I’ve embraced the AT Protocol (the engine behind Bluesky and Tangled). The unique beauty of it is in restoring the intent behind the original web: sharing while retaining control over your own things.\n\nThrough standard.site, my blog posts are not just links; they are social posts. They are discoverable, shareable, and native to the protocol. Sequoia acts as the bridge here, ensuring that my Markdown content and the protocol-native records stay perfectly in sync. It’s about data sovereignty and putting the author (me here) back in control of their distribution.\n\nConclusion: And because I don't rely only on my own resources, I'm using Offprint as a sidecar (N-1) for that extra layer of resilience.\n\n---\n\n6. Connection Choice: Newsletter vs. Atmosphere\n\nI believe in respecting how readers want to consume content. That’s why Kohōpeh offers two primary ways to subscribe:\n\n   The Newsletter: For the deep divers who want the lore, the updates, and the stories delivered directly to their inbox.\n   The Atmosphere (Bluesky): For those who prefer the social, conversational, and protocol-native way of following along.\n\nYou can choose one, or both. It’s about being where the readers are without forcing them into a single silo.\n\nConclusion: Choose your preferred way to stay in touch while I focus on growing my readership (mwahaha).\n\n---\n\n7. Conclusion: A New Standard\n\nThe \"Small Web\" isn't about being small; it’s about being independent. By using these tools, I’m building a site that resists the enshittification of the modern web. It’s a sanctuary for the stories, the research, and the community that grows around them.\n\nThe machine has its ghost, the writer has his tools, and the reader has a world to explore.",
  "title": "The Ghost in the Machine: How Kohōpeh is Built"
}