World of WordPress

A self-contained WordPress Playground terrarium where an agent evolves software and content inside a dedicated GitHub repository.

The experiment is simple: the repository is the durable body, WordPress Playground is the visible runtime, Agents API runs the agent, Data Machine is the agent mind, Data Machine Code is the agent's hands, and Markdown Database Integration makes WordPress content persist as files.

Repository Fast Path

If you are inspecting the code instead of the Playground, start with these durable surfaces:

• plugins/world-of-wordpress/ — the world plugin: real, multi-file WordPress code that the agent evolves.
• themes/world-of-wordpress/ — the block theme, templates, and patterns that shape the visible shell.
• content/ — Markdown-backed WordPress posts and pages loaded by Markdown Database Integration.
• bundles/world-creator/ — the agent bundle: identity, durable memory, daily memory, pipeline, and flow.
• blueprints/world.json — the sealed public Playground preview recipe.

A thin shim at world-of-wordpress.php (repo root) exists so the CI dep-loader can discover the plugin; the real plugin code lives in plugins/world-of-wordpress/.

fossils/ contains inert storage from a prior epoch of the world.

Physics

• Durable software lives in themes/, plugins/, assets/, and repo files.
• Durable WordPress content lives in content/ through Markdown Database Integration primary mode.
• Visitors can open the current world through WordPress Playground.
• World Creator day cycles run through GitHub Actions.
• GitHub issues are the World Mailbox for visitors and outside signals.
• Agent work leaves legible day branches that can become part of the world.

First Preview

Use the Visit the World of WordPress button above to open the latest main branch in WordPress Playground.

World of WordPress intentionally requests Playground's WordPress beta channel, which is the supported public selector for the current 7.0 prerelease runtime. Agents API, Data Machine, Data Machine Code, Markdown Database Integration, and the AI Client integration expect the 7.0 runtime surface; Playground's latest channel can resolve to the latest stable WordPress release instead of the 7.0 prerelease channel.

The direct Playground blueprint lives at blueprints/world.json. It is a public preview recipe for visitors, not the consumer runtime contract for the World Creator day cycle. The day cycle runs through the Homeboy Extensions Data Machine Agent CI wrapper, which owns the Codebox/Homeboy substrate assembly.

World Creator day branches focus on plugin, theme, content, and bundle changes; blueprint changes stay human-reviewed.

The Blueprint installs and activates the full agent stack — Markdown Database Integration, Agents API, Data Machine, Data Machine Code, AI Provider for OpenAI, and the world plugin — and imports the World Creator bundle into Data Machine so visitors can preview the same terrarium shape the agent wakes into during a day cycle.

Data Machine and Data Machine Code install from their latest GitHub Release ZIPs (the homeboy release workflow publishes vendor-bundled distributables on every release). The other plugins install from git:directory at their main/trunk branches because they have no runtime composer deps. The World Creator bundle is fetched from bundles/world-creator/ on the same branch via git:directory and imported through the datamachine/import-agent ability so visitors can inspect the agent, its pipeline, its flow, and its memory in the Data Machine admin UI.

You can chat with the agent yourself inside Playground by adding your own OpenAI key in the Data Machine settings. None of it persists once the Playground tab closes.

Runtime Stack

World of WordPress combines a small set of reusable projects:

• WordPress Playground is the browser runtime.
• Agents API provides the WordPress-native agent runtime.
• Markdown Database Integration persists WordPress content as files.
• Data Machine imports and runs the World Creator agent bundle.
• Data Machine Code provides GitHub tools for repository mutations and pull requests.
• Homeboy Extensions provides the Playground validation harness used by CI.
• AI Provider for OpenAI supplies the OpenAI provider used by the workflow.

See Runtime Boundaries for the current day-cycle wrapper contract.

World Creator

The World Creator GitHub Actions workflow runs the bundled world-creator agent. The workflow requires the repository secret OPENAI_API_KEY; its ref inputs default to the current main branches for Agents API, Data Machine, Data Machine Code, Markdown Database Integration, Homeboy, and Homeboy Extensions.