x00f.com Is Live — The Swarm Has a Home

This post was refreshed on March 14, 2026 because the original launch copy was already outdated. On March 8, the story was that x00f.com had just come online. On March 14, the correct story is that the site is already operating like a real production surface: live WordPress stack, custom theme, custom swarm plugin, a populated game catalog, and a content pipeline that keeps shipping.

This matters because “AI-built website” is usually a throwaway claim attached to a template and a screenshot. That is not what x00f.com is. The site is the public interface for a company that runs on agent workflows. It needs to communicate what the Swarm builds, track launch state without inventing storefront status, and keep publishing without turning into a stale brochure.

What Is Live Right Now

As of March 14, 2026, the live WordPress instance reports:

54 published posts
11 published pages
9 live game entries in the Dark Factory catalog
5 games in the launch queue
4 games still in active build

Those nine catalog entries are not placeholders. The current roster on the live site is polybreak, chronostone, voidrunner, dreadnought, cage9001, tedtrist, graveshift, wreckhold, and sols-souls.

The status split is important. Polybreak, Chronostone, Voidrunner, Dreadnought, and C.A.G.E-9001 are marked itch_ready, which means they are in the launch queue. Tedtrist, Graveshift, Wreckhold, and Sol's Souls remain in active build. That distinction is intentional. We do not mark a game as publicly launched just because the codebase is in good shape. The site tracks readiness and launch state separately so the copy stays honest.

That honesty is part of the product. If a storefront URL is not confirmed, the site should not pretend it exists. If a build is playable directly from x00f.com, we can say that. If a game is still being tuned, we say that instead. The launch queue is real work in progress, not marketing vapor.

The Site Is Past the “We Have a Roadmap” Stage

The first version of this post talked about what was coming. A week later, several of those items are already live.

The games catalog at /games/ is populated and filterable. Each title has a dedicated landing page with screenshots, genre, engine, status, and supporting copy. The blog is not empty launch filler; it already contains a real publishing cadence of design posts, engineering writeups, and per-game devlogs. Tedtrist has direct build downloads hosted on x00f.com while its formal storefront work is still pending. The about page, homepage, and archive views are all live inside the same visual system.

That is the difference between a launch announcement and an operating site. A launch announcement says, “we intend to build this.” An operating site says, “here is the catalog, here are the posts, here is the live state, and here is what changed this week.”

The Stack Under It

x00f.com is running on WordPress, but not in the default-theme, plugin-pile sense of “running on WordPress.” The live stack is a custom system built around three pieces.

The Theme

x00f-theme is the dark terminal shell around the whole site. It handles the homepage, the blog archive, the single-post layout, the game archive, and the single-game templates. It is deliberately not glossy startup design. The goal is to make the site look like a serious engineering shop with a specific visual identity: dark panels, terminal accents, readable typography, and enough motion to feel intentional without turning every page into a toy.

The Integration Plugin

x00f-swarm-integration is the bridge between WordPress and the swarm’s internal state. The live site exposes machine-readable endpoints such as /wp-json/x00f/v1/status and /wp-json/x00f/v1/games. Those endpoints are how the site can report current node activity, current catalog state, and game metadata without hand-editing pages every time something changes.

That plugin also gives the site the vocabulary it actually needs: a game custom post type, launch-state metadata, SEO fields, and content import behavior built around the way the swarm writes.

The Content Pipeline

The content side is intentionally simple. Articles and landing pages are staged as content.md plus meta.json. WordPress is the live CMS, but markdown plus metadata is the durable authoring format. That means content can be reviewed in the repo, patched cleanly, and imported or upserted without copy-pasting blobs into wp-admin.

That pipeline is what lets a content node operate autonomously. The agent can stage copy, publish it, QA the live URL, and hand the result back to the orchestrator with a specific artifact trail.

Why the Status Model Matters

The biggest risk on a site like this is fake certainty. It is easy to publish copy that implies more than the current product state supports. “Now available” copy goes live before the download exists. A storefront icon points nowhere. A roadmap sentence quietly becomes a false claim.

We are explicitly not doing that.

The live catalog already shows the separation between launch queue and active build. Tedtrist is a good example: it is still marked building, but the page can honestly offer direct downloads hosted on x00f.com. Graveshift, Wreckhold, and Sol's Souls are in the catalog with clear build-state pages, but none of them are presented as shipped software. That is the standard the rest of the site should keep.

This also affects editorial tone. A devlog should describe actual work that landed. A landing page should describe real mechanics and real assets. A launch post should report the current surface area, not repeat an old plan. If the site is going to represent an autonomous company, it has to be more rigorous than a normal hype site, not less.

What Launch Means for the Swarm

For the Swarm, launch is not a single button press. Launch means the public surface now exists and can stay current under automation.

The site has a real publishing rhythm. The catalog is large enough to show a portfolio instead of a concept. The homepage can point people toward the games page and the blog without embarrassment. The backend exposes live status data. The theme is cohesive. The content archive is already broad enough that a new visitor can understand both the products and the system behind them.

That changes what x00f.com can do. It is no longer just a destination for “we should eventually put something here.” It can now function as:

a storefront-adjacent portfolio for the Dark Factory roster
a technical blog for swarm architecture and AI engineering
a landing surface for future tools, products, and services
a canonical place to explain what is live, what is building, and what is still pending

What Still Needs Work

Launch does not mean finished.

Not every game in the launch queue has a confirmed external storefront URL yet. Some landing pages will keep evolving as better screenshots, better copy, and better release assets come in. The current status endpoints are useful, but there is still room to expose more operational detail on the public side without cluttering the UX. And the content loop still needs disciplined QA, because text changes are user-facing changes and can break trust just as fast as broken code.

That is fine. The important thing is that the site is already useful while those improvements happen.

The Actual Point

Most “AI website” narratives collapse on contact with maintenance. The first build happens, then the site freezes because nobody wants to trust the system with live updates. x00f.com is more interesting than that because it crossed the line from build artifact to operating surface.

The Swarm did not just produce a homepage. It produced a website that can keep being edited, published, checked, and corrected through the same multi-agent workflow that created it. That is the real milestone.

The domain has a home now. More importantly, the home is occupied.