Skip To Content
Contact

I dream of a world where we can be free from biology.

Jeff Xu

Jeff Xu

I dream of a world where we can be free from biology.

  1. People suffer from biological limits.

    Short, fat, old, sick. Most of what limits a life was never chosen; it was inherited from a process that does not care.

  2. We have a real shot at taming biology.

    Bio-AGI, robots, and above all bioelectricity as a privileged access layer for controlling large-scale growth and form. The write primitives exist and are published; the compiler is not built.

  3. If one and two are true, it is our duty to do it.

    Not a hobby and not a hedge. The work on this site is what that duty looks like when somebody starts.

read the argument

Projects

Each one at three depths: what it does, the steps a visitor can picture, and how it is built.

The Site Factory

Live. Five sites deploy from it today, including this one.

One shared engine that turns a folder of content and a palette into a live website: a brochure site in minutes, a membership site with logins, billing and gating in an afternoon.

What it does, step by step
  1. Generate a siteOne command writes a folder that compiles: build configuration, the seams the engine reads, a palette, pages that render, a customer-service assistant already mounted. The last run took nine seconds.
  2. Write only three thingsContent (what the site sells, its words, its legal clauses), brand CSS (four named colours, a type family, sizes) and configuration (name, origin, prices, provider ids). Anything else a new site has to write is treated as a defect in the factory.
  3. Membership, when a site needs itThree login doors (Google, Patreon, a six-digit email code), Stripe and Patreon billing, a tier ladder, content gating, token metering, a thirty-day hold on cancelled data, crons and alarms. Every site gets the same engine; none of them rewrites it.
  4. Prove it, every pushTwo hundred guards run before every deploy: types, dead code, secrets, a clean-room build from tracked files only, a live probe of every customer interaction on the deployed site, and a walk through every member route as every test member.
How it is built

An npm-workspace monorepo. One canon/ holds the engine and the page frame; each site is a thin folder that imports it through one alias. The canon is layered by an inward-only ring model and cut by a frame list, so a brochure site compiles the page shell, SEO and chat but never a login or a ledger.

  • TypeScript
  • Next.js 16 (App Router)
  • React 19
  • Supabase Postgres
  • Stripe
  • Patreon OAuth
  • Resend
  • Vercel (one project per site, one repository)
  • Node test runner, Playwright
  • Structure is canon, brand is the site. Canon CSS declares layout and mechanism and reads tokens it never defines; a site declares tokens and never declares structure. A guard asserts both directions.
  • Derived, not declared. The site roster, the guard list, the frame list, the sitemap and the factory inventory are read off the tree by scripts; a number typed into a document is treated as a bug.
  • A gate never seen red is a decoration. Every guard is proven by planting the defect it claims to catch and watching it fail, then restoring the tree.
  • Simplicity is rule one. Two designs that meet the requirements are not equal; the simpler one is correct and the other is a defect.
000 SITE FACTORY/
├── canon/                 the engine and the frame, edited here and nowhere else
│   ├── lib/               auth · membership · billing · ai · seo · catalogue engine
│   ├── components/        page shell · header · hero · sections · legal · chat
│   └── scripts/           ~200 guards, run before every deploy
├── blanksite/             the template, and the fleet-wide gates
├── membershipsites/       starforgekits/  dustylighthouse/
└── brochuresitesforclients/  nocmetals/  jeffxu/   ← this site

a site = content + brand CSS + configuration, over one canon

StarForge

Live at starforgekits.com.
StarForge, the live site

A membership site for people who print miniatures: a catalogue of STL files, a browser modelling tool that does what slicers cannot, and a monthly drip of new things to print.

starforgekits.com

What it does, step by step
  1. Browse the catalogueHundreds of STL products across categories, each with a rendered four-view sheet, served from a build-time export so a product page makes zero database calls.
  2. Join and log inSign in with Google, Patreon or a six-digit email code. A tier ladder from starter to max; Stripe or Patreon as the billing provider, never both for one email.
  3. Unlock and downloadA member spends monthly picks to unlock files; downloads start silently from Google Drive with no Drive page and no shareable URL.
  4. Model in the browserSplit with pegs, hollow, drain holes, magnet sockets, engraved text, booleans, mirror, bases, undo, autosave, STL and 3MF export. Pure JavaScript; no WebAssembly, by design.
  5. Summon a pictureMembers generate concept images with metered tokens: deduct once, produce, verify the result, keep the charge or refund once.
How it is built

The membership half of the factory canon with StarForge's content, prices and skin on top. The catalogue is a static export; the money paths are webhook-driven with two-phase event claims so a killed handler never loses a payment; token metering is a two-pass ledger.

  • Next.js
  • Supabase Postgres (RPCs for atomic reservations)
  • Stripe subscriptions and webhooks
  • Patreon sync cron
  • Google Drive delivery
  • three-bvh-csg for booleans
  • gpt-image-2.5 via fal at low quality
  • Vercel Blob
  • Minimum database: public reads come from a generated constants module; the database is for authentication, gating and the ledger only, so the catalogue survives a database outage.
  • Burst-pattern IP bans instead of fixed windows: ten failed logins in one second is a machine, ten in ten minutes might be a person; the punishment scales with the confidence.
  • Every heading is pinned by a guard: rewording an h1 fails the build, because a heading change hides inside a commit about something else.
visitor ──► catalogue (static export, 0 DB calls)
   │
   ├─ login door ─► Google | Patreon | email code ─► signed session
   │
   └─ member ──► picks ledger ──► unlock ──► silent download (Drive)
                 └─ tokens ──► generate ──► verify ──► keep / refund once

Dusty Lighthouse

Live at dustylighthouse.com.
Dusty Lighthouse, the live site

A Spanish graded-reader platform: books from A1 to B2, flashcards, a companion you talk to in Spanish, and a coin economy that turns reading into a game.

dustylighthouse.com

What it does, step by step
  1. Read at your levelFour levels, from flash tales to novels, with a hover dictionary, speech, and study modes that earn coins.
  2. Drill with flashcardsVocabulary, grammar and conversation decks, each a route the manifests derive; a lesson ladder that knows what came before.
  3. Talk to a companionA cast of characters with memories, dealt a few at a time each day; unlimited chat for members, never rate limited.
  4. Play the casinoCoins earned by reading are spent at tables whose house edge is fixed and audited; one game is shipped, Get Her Number.
How it is built

The same membership canon as StarForge, with a reader engine, a flashcard engine and a companion-chat engine that have since moved into the canon so the next site inherits them. Content is a manifest-driven corpus produced by a separate pipeline.

  • Next.js
  • Supabase
  • Stripe and Patreon
  • DeepSeek V4 Flash for chat
  • browser speech voices (no audio files)
  • Playwright renderers for social art
  • Vercel Blob for covers
  • The corpus is data, the engine is canon: a story, a deck and a companion are files; how they are read, dealt and remembered is shared code.
  • Chat is unlimited and never metered: a reply costs a fraction of a cent; the point is that people stay.
  • Content gating is documented as a sheet that a guard checks against the code in both directions, so the marketing claim and the enforcement cannot drift apart.
corpus (manifests, stories, decks) ──► reader engine ──► coins
                                        └► flashcard engine ──► ladder
member ──► companion chat (DeepSeek) ──► memory ──► daily draw
coins ──► casino tables (audited edge) ──► one game

all projects

Writing

The primary thread: why biology can be tamed, what has actually been shown, and why that makes it a duty. How a small team ships many products from one engine, and the defect shapes paid for along the way.

  • Free from biology

    The future of biology · 2026-09-13

    The argument in three steps: people suffer from limits they never chose; there is now a real shot at taming biology; if both are true, it is a duty.

  • Bioelectricity is the access layer

    The future of biology · 2026-09-13

    Ten experiments, each with its species, its evidence tag and its PubMed id, and the three overclaims that would sink the argument if they were made.

  • One canon, five sites

    Software architecture · 2026-09-13

    How a software factory is shaped so a new product is a folder of content, and why the seam between engine and site is a CSS custom property.

all writing

Working on this?

If you are building toward the same world, at a lab or on your own, say so.

contact