pixtuoid v0.23.0
▸ booting office… ok
▸ loading themes… ok
▸ 15 CLIs connected… ok
press any key to skiptap to skip

How we build

pixtuoid is written, reviewed and maintained by AI coding agents working for one owner, across a handful of repositories. This page maps who does what; each part links the file that holds it, which wins wherever the two disagree.

The repositories

RepositoryWhat it holds
pixtuoidThe CLI, the office engine and the pixtuoid.dev site
pixtuoid/apple (private)The App for iPhone and iPad
lofiThe procedural music the office plays
.githubWhat every repository shares, as its AGENTS.md lists

Who does what

  • The owner (AGENTS.md)

    Setting the bar and the Roadmap, reviewing every doc change, merging the release PR by hand

  • A session (Parallel sessions)

    Working one branch in its own worktree, through the arc when the work is non-trivial and always through the merge gate

  • A subagent (local review)

    Reviewing or verifying one scope for its session, then reporting

  • The CI review, an AI code review Claude Code runs

    Posting a verdict and its findings on the PR

  • Mergify

    Merging once the queue’s conditions hold

A change, end to end

Non-trivial work runs as the arc loop, from picking a Roadmap item to the wrap; any PR, an arc’s or not, lands through the merge gate, each finding at a terminal state dispositions defines.

A change's path to mainA Roadmap item goes, through the arc when the work is non-trivial, to a pull request; its checks must pass and every review finding must reach a terminal state before the merge queue lands it on main. Roadmap item The arc, for non-trivial work Pull request CI checks All green CI review, by Claude Code Every finding at a terminal state Merge queue main

What keeps it honest

  • One set of rules. The org rules are copied into each repository’s root agent guide (AGENTS.md), and CI fails when that copy drifts. Each of those repositories adds a REVIEW.md for what a review checks.
  • Evidence, not recall. Every external claim follows the org rules’ Evidence bullet.
  • Real CLIs, not mocks of them, as the hermetic tier runs them.
  • A lesson becomes a mechanism, as the arc’s Wrap step says.

Source of truth: docs/HOW-WE-BUILD.md — this page renders it verbatim (each figure is drawn from the table or Mermaid block GitHub shows).

~ pixtuoid docs · /how-we-build
★ 569