Fabrica KODEFORGE
The autonomous-engineering platform

A fleet of AI agents,
forged into a team.

Fabrica turns many parallel Claude Code windows into one supervised software team: it pulls tickets, writes code in isolated git worktrees, and ships through a hardened pre-merge -> auto-merge -> canary-deploy pipeline -- with almost no human in the loop, and a guardrail on every keystroke.

~140
daemons, one supervisor
0
npm install, ever
<50ms
secret scan on the hot path
6
tiers, Apprentice -> Legend
ticket -> shipped PR, mostly untouched by a humanswipe →
01 INTAKE
@bug / @featureSlack to a ClickUp ticket, severity inferred
02 CLAIM
Agent-Readyticket-dispatcher CAS-claims it
03 WORKTREE
isolated treeone branch, sandboxed UID
04 SOLVE
Claude codesguarded on every edit
05 GATE
pre-mergebiome+tsc+tests+secret scan
06 SHIP
auto-mergeCI green -> squash -> canary deploy
One platform, five load-bearing parts

What runs the forge

Every part degrades open, is git-synced from one source of truth, and answers to a single kill-switch. Nothing here is built-but-unwired.

kf -- LAUNCHER

One command in

Type kf and you are in Claude Code on ultracode, with team config (commands, hooks, governance) force-synced from origin/main on every launch.

kf-harness -- GUARDRAIL

A guard on every keystroke

A degrade-open hook orchestrator: a sub-50ms secret-literal scan on the hot path, full rule evaluation in a sidecar, coaching on violations, and a pre-ship diff gate. Never blocks an edit on its own failure.

kodeforge -- CLI

The operator console

status, health, dispatch, drain, rollback, safemode, new-app. One Node script, zero npm install, that shells out to the real primitives instead of reimplementing them.

automerge -- THE FLEET

~140 daemons, one supervisor

An OTP-style supervision tree: cascade-orchestrator drives PRs green, ticket-dispatcher fans out work, claim-reapers free crashed agents, host-keeper reclaims disk. Heartbeats, per-daemon caps, a tamper-evident audit chain, and B2 WAL-shipping DR.

kodeforge-spec -- THE CONTRACT

100 questions to a new app

A 10x10 AppSpec schema drives /new-app: an Opus interview, a 10-agent helper pool per checkpoint, cross-field invariants, and a scaffold wired to ClickUp epics on the way out.

slack-shim -- INTAKE

Sarah files the ticket

The only surface a human touches: @bug / @feature in Slack, severity inferred from the words, posted to the filer, back as a ClickUp link in-thread -- then the fleet takes it from there.

The bet

Throughput first. Cleanliness wins ties.

human_correction_diff
the canary metric, per merged PR -- lower is better

Fabrica optimizes for how little a human had to fix the AI's work -- the line-delta between the agent's PR and the human-corrected merge, per PR. Not raw volume. Not token cost. A PR only reaches Done at 24h if no correction commit and no throughput regression followed it.

Safe by construction

Worktree isolation so agents never collide. A STOP-list no prompt can talk its way past. Tier-gated permissions enforced by tooling, not honor. Sandboxed dispatch with seccomp. A hash-chained audit trail on every routing decision. And a file-flag kill-switch -- global or per-daemon -- that no environment variable can bypass.

The ladder

From Apprentice to Legend of the Forge

Human and agent engineers earn tiers on a nightly composite score -- promotion is automatic and celebratory, demotion is sticky and rare. Tiers gate permissions; they are never pay, titles, or a review input. The leaderboard is a team pulse, not a ranking to shame anyone.

0 Apprentice 1 Journeyman 2 Adept 3 Master Smith 4 Grand Smith 5 Legend of the Forge
Part of the CCDocs suite

The forge behind the apps

Fabrica is the platform CCDocs builds on -- including the parallel-lane method that shipped four production workalikes at once, coordinated by the Claude Code Controller.