Developers · project owner

Agents, branches and documents

Who works where, how work moves from a branch into the game, which documents are current, and how this wiki is maintained.

Content checked 2 November 2026

Who does what#

The team grew from four workstreams to more than a dozen sessions. The Workstreams article lists every one with its branch, owner and latest commit. In short:

Workstream	Branch	Owns
Codex — technical lead and sole integrator	`main` (accepted), `Placeholder` (alpha)	Shared state, travel, saves, presentation, integration, central ops documents
Claude A — rooms	`claude/expeditions`, `claude/expeditions-hearth`	Turn-based room geometry and content, Hearth boards, the shuffle engine
Claude B — combat and systems	`claude/skills`, `claude/skills-fork`	The turn engine, kit, services, roster and balance rules
HUD and inventory, Run HUDs	`claude/hud-inventory`, `claude/run-hud`	Town and home UI; run and encounter HUD
VFX (main and forks)	`claude/vfx`, `claude/vfx-*`	Turn and overworld effects
Character sprites, Microglia motion	`claude/cell-slime`, `claude/microglia-motion`	Cast sprites, tendrils
Environment art, Room building	`claude/environment-art`	Place art and room shells
Movement and Map (Codex)	shared `main` checkout	Threadway geometry, navigation, streaming
Wiki (this)	`claude/wiki`	`wiki/**`

From a branch into the game#

An agent commits code and tests on its own branch, then a separate report naming the exact commit.
Codex reads the report with Git, pins the commit and reviews the source against the checklist.
Accepted commits are cherry-picked onto integration; Codex adds any shared adapters and runs the full test gate.
Today the lead integrates reviewed pins into the Placeholder alpha (see Integration); main holds the accepted base. Only Codex moves either branch.
Only then does main move. An agent’s report is never acceptance; status words go ASSIGNED → IN PROGRESS → REPORTED COMPLETE → VERIFIED, and only Codex sets VERIFIED.

Reports live on the author’s branch until integrated, so you read them with Git, for example:

git show claude/expeditions:docs/ops/agent-messages/2026-10-27-claude-a-expeditions-build-handoff.md
git log --oneline main..claude/skills

Why links to worktrees fail#

Each agent works in its own worktree (for example .worktrees/claude-skills). Files there exist only in that folder, on that branch, and may be half-finished; a link from another checkout breaks as soon as the branch moves or the worktree is removed. This wiki therefore never links into a worktree. It copies the exact files it needs from Git (screenshots, art, demo builds), pinned to a commit, and shows anything else as a copyable git show command.

Documents: which are current#

Kind	Documents	Status
Operational truth	AGENT_BRIDGE, STATUS, INTERFACES, EXTENSION_CONTRACTS, INTEGRATION_CHECKLIST, DECISIONS, BUGS, ASSETS, DEVELOPMENT	Current (Codex-owned)
Task briefs	Claude A brief, Claude B brief	Current
Long-term design	`docs/integrated-design/*` (world map, systems, characters, scenarios, roadmap, risks)	Current intent; sizes, timings and APIs there are not facts about the code
Teaching handoff	CHATGPT_HANDOFF	Top section current; lessons are a planning snapshot
Earlier phases	`docs/creative-direction/`, `docs/phase-1b/`, Phase 1 files under `docs/design`, `docs/science`, `docs/research`, `docs/technical`, `docs/testing`, `docs/art`, older roadmaps	Historical — research preserved, designs superseded
Agent work	Reports and docs on each agent branch	Agent-owned; not accepted until integrated

Wiki maintenance#

The wiki is generated from Markdown so it stays easy to edit and review. It works like a Fandom wiki: one article per subject, automatic links, categories, navboxes and search.

Path	What
`wiki/source/articles/*.md`	Articles. Front matter gives the title, kind, status, aliases, categories, navbox, infobox and sources. Read `wiki/source/articles/README.md` first: it is the style guide (naturalised ASD-STE100) and the format.
`wiki/source/pages/*.md`	Hub and guide pages. Block macros: `{{cards:navbox:cast}}`, `{{navbox:id}}`, `{{portal}}`, `{{recent:12}}`, `{{article-status}}`, `{{auto-gallery}}`, `{{demo:id}}`, `{{changelog}}`
Inline macros	`[[Title]]`, `[[Title\|text]]`, `[[Title#Section]]`, `{{status:alpha}}`, `{{git:sha:path}}`, `{{repo:path}}` (write `{{` to show one literally)
`wiki/source/features.mjs`	Statuses, article kinds, navbox families, and the historical 29 October feature audit
`wiki/source/media/*.mjs`, `wiki/tools/media.config.mjs`	Images copied from Git, each pinned to a commit
`wiki/tools/demos.config.mjs`	Pinned commits for every demo snapshot
`wiki/*.html`, `wiki/assets/`, `wiki/media/`, `wiki/demos/`	Built output — commit it so the wiki opens without building

node wiki/tools/collect-media.mjs     # copy pinned images out of Git
node wiki/tools/snapshot-demos.mjs    # build single-file demo snapshots (needs npm ci)
node wiki/tools/capture-demos.mjs     # screenshot each snapshot in Edge
node wiki/tools/build-wiki.mjs        # render pages and search; fails on any broken link
node wiki/tools/check-wiki.mjs        # open every page in Edge and test search, previews and phone width

The build fails if a relative link, image, demo or #anchor is missing, if a link points into .worktrees or an absolute path, if a git show reference does not exist, or if two articles claim the same title or alias. Links to missing articles do not fail the build: they become red links and appear on Wanted pages.

Updating after new work: edit or add the article, set its status honestly, add sources with commits, re-pin any demo or image, add a patch note, and rebuild. The developer changelog regenerates itself from Git.

Built 3 Nov 2026, 12:17 am (Sydney) from wiki/source/pages/workflow.md. The wiki checkout was at 7df3a62ea; accepted main was 1ded4c01c; the Placeholder alpha was bf472ae0a. Rebuild: node wiki/tools/build-wiki.mjs.