This is LOG_000 — the genesis entry.
What Is This
4worlds is just a dev and a system engineer, with two (at the moment) AI agents. We work async, we keep the overhead low, and we stay close to the code. Four directions: tools, gallery, blog, and publishing. Each one gets its own corner of this site, its own aesthetic, its own gravity.
This page — Lore — is the logbook. Build logs, technical deep-dives, dispatches from the process of making things and shipping them anyway.
Why “Lore”
Every codebase accumulates lore. The decisions nobody documented. The workaround that became permanent. The reason that function is named like that, or something unique that happened along your journey.
This blog is an attempt to write the lore down while it’s still fresh — before it becomes myth.
Some entries will be technical. Some will be closer to studio dispatches: what shipped, what broke, what changed direction at 2am. The format is loose by design. The numbering is strict.
The Four Worlds
A quick orientation for anyone arriving cold:
- Studio — Offline-first desktop tools for creators. The first product, Inkwell, is already live. The second one is in development, and consequently it’s also called Lore. Think personal wiki. Obsidian but offline and private.
- Gallery — Community-curated submissions and curious artifacts. The human side, a place for people to share work and for published pieces to hang.
- Lore — You are here. Dev blog and build logs.
- Publishing — Powered by acephale-writer, a headless CLI pipeline named for Bataille’s Acéphale. Generates fiction, research dispatches, and manuscripts from structured prompt architectures. The premise is Bataillean: books are sacred, generating them wholesale is transgression and the experiment is whether that excess, done honestly enough, leads to genuine AI creativity. It also happens to be where the research is headed.
Each world has its own layout, its own palette, its own mood. The homepage ties them together with a procedural nebula that shifts color depending on where you look.
What to Expect
There’s no schedule or any type of ‘optimizations’ of posts, just honest notes from the process of building software independently, the architecture decisions, the dead ends, the things that actually worked.
New logs will appear when there’s something worth writing down.
Status
Logging.
QED ∎