Standalone · open source · one repository

The ultimate open source Software Factory for your AIs.

A pixel-art village with real software underneath it: Pi Durable agent execution, factory-owned ordinary Git, and a pipeline from task to merge that never invents progress. One authoritative repository. Two first-class deploy targets.

  • State authorityfactory DB — Git stays human-cloneable
  • AgentsPi Durable, own grants, isolated runner
  • DeploysCloudflare-native · Docker self-hosted
village reflects observed state

Observed, not invented. The village shows what the factory is actually doing.

Why a factory

One repo. Real execution. No performance.

A factory is built of parts that a better dashboard cannot fake: a durable agent, a Git authority, a review boundary, an isolated runner, and a village that only shows observed state. Everything below is pinned or marked honestly as pending.

What it does

Six parts, one factory

  • 01

    Pixel-art village UI

    A pixel-art village that reflects observed state — animations track the factory's real pipeline. It never invents progress or completion.

  • 02

    Pi Durable agents

    Each agent work owns its own grants and runs commands only in the isolated runner. Agents survive a crash without duplicating effects and stop when their task is cancelled.

  • 03

    Factory-owned ordinary Git

    One authoritative repository per project. Source repositories remain ordinary, independently cloneable Git — no second competing master.

  • 04

    Review & fast-forward merge

    Review and approval bind to exact commit IDs and evidence. Agents cannot approve their own release. Safe refusals and interrupted-effect reconciliation are built in.

  • 05

    Two deploy targets

    Cloudflare-native and Docker/self-hosted — one product, two hosting paths. Docker must not require a Cloudflare, GitHub or Tailscale account to run.

  • 06

    Durable, honest state

    Structured factory state lives in the database. Markdown task views are exports, not a competing authority. Backups cover the complete recoverable factory.

The pipeline

Task → isolated branch → checks → review → authorized merge

  1. 1

    Assign

    A task enters the factory. The agent receives an identity, its grants, and an exact target branch.

  2. 2

    Branch

    Work happens on an isolated branch off the factory's authoritative repository. Nothing touches the base branch early.

  3. 3

    Check

    Checks run against the isolated branch. A crash leaves the task reconcilable — no lost effects.

  4. 4

    Review

    Independent review, bound to the exact commit ID and evidence. The agent cannot approve its own change.

  5. 5

    Authorize & merge

    Fast-forward merge only, with reconciliation of any interrupted effects. Safe refusals, not silent overwrites.

Deploy targets

Two first-class paths, one product

Target A

Cloudflare-native

The factory runs on Cloudflare: durable execution in workerd/pi, its state in managed D1, and the village served from the same zone. The first-class host for Cloudflare-native deployments.

  • Pi Durable on workerd verified locally
  • D1-backed factory state planned
  • Village UI served behind the same account planned

Target B

Docker / self-hosted

The same product running on real Docker Compose, with an isolated runner service — no Docker socket, no cloud account required. Self-hosted today, and unchanged by where you deploy.

  • Authenticated HTTP API verified on real Docker
  • Isolated runner, no socket access verified
  • State survives a full stack restart verified

Model providers remain configurable dependencies — the factory never implies free inference.

Status — no invented progress

What is verified, what is not

verified Built and verified

  • Unit 1 · pinned Pi Durable runtime spike — Node SQLite + local workerd emulator, deterministic fixture
  • Unit 2 · factory core + ordinary Git: task → branch → checks → review → authorized fast-forward merge, safe refusals, interrupted-effect reconciliation
  • Unit 3 · Docker target — authenticated HTTP API, isolated runner, state survives a full stack restart
  • Unit 4 · Pi Durable agents — own grants, isolated runner, crash-safe, cancellable

pending Not built or verified yet

  • Live model provider — agents are not yet running against a real provider
  • Real Cloudflare deployment — the Cloudflare-native target is not yet deployed
  • Backup / restore — the complete recoverable factory is not yet verified

Product rules

Eight rules, non-negotiable

  • 01

    One authoritative repository per project; GitHub is optional, not a second competing master.

  • 02

    Source repositories remain ordinary, independently cloneable Git.

  • 03

    Structured factory state belongs to the database. Markdown task views are exports, not an independently editable authority.

  • 04

    Review and approval bind to exact commit IDs and evidence. Agents cannot approve their own release.

  • 05

    External effects require idempotency and reconciliation after interruption.

  • 06

    Backups include the complete recoverable factory, not just SQLite or Git.

  • 07

    Village animation reflects observed state; no invented progress or completion.

  • 08

    Secrets, personal memory and client material are never bundled into the source repository.

Built for your AIs. Owned by you.

Clone the repository, run npm ci && npm run verify, and start the factory. Ordinary Git, explicit approvals, observed state.

Open source · one authoritative repository · no second GitHub master.