● Batch status Bonfire 1.0.1 · shipping · 4 in oven México · CDMX ● Open for engagements
CandyFactory

AI, built with engineering discipline.

Open-source tools (Bonfire and CandyFactory OS) and custom AI systems for the businesses that run on them.

See what we make → building for a business? → the shop
QUEUE SCHEMA BILLING AUTH PAYMENTS MIGRATIONS REFUTES VERIFIES BUILDS TESTS MIGRATES
INTAKE → COMPREHEND → DISPATCH → RETRIEVE → RETURN
§01

Method

The Line · The Mirror · agentic discipline
● Shipping now
Entry 01 / 06

Bonfire

v1.0.1 · PyPI · Apache-2.0 · public

Your Claude Code, opinionated. Pip-install a runtime and a Claude Code skill; run /bonfire scan to wire a nine-role cadre around your project.

$ pip install bonfire-ai
bonfire-ai · install READY
$ pip install bonfire-ai
  Downloading bonfire_ai-1.0.1-py3-none-any.whl (412 kB)
  Installing collected packages: bonfire-ai
Successfully installed bonfire-ai-1.0.1
$ cd ~/projects/your-thing && /bonfire scan
Reading repo · 247 files indexed
Drafting nine-role cadre · cadre.toml
Cadre wired. Run /bonfire build to start a batch.
$

CandyFactory OS

Pop!_OS fork · COSMIC · in the factory

A trademark-clean, reproducibly-built Linux distribution tuned to be the substrate our agents run on: branding now, kernel-level levers next.

The Constable

project manager · plugin · in the oven

An ops-drift detector for the whole surface: it watches the project the way a project manager would and flags what slipped. A Bonfire-substrate plugin.

The Prophet

build-in-public engine · plugin · in the oven

A build-in-public engine for solo founders: it mines your build log for moments and drafts platform-shaped posts under your own voice. A Bonfire-substrate plugin.

CandyCane

review surface · plugin · in the oven

A review-acceleration surface: review the running program at claim and architecture altitude, flow over diff, where glow means heat means risk. A Bonfire-substrate plugin.

§02

Custom work

Engagements · the method, sold custom
Your stack, your infrastructure, your choices

It doesn't matter what you have on the other side. We attach to it, and we build in it.

You keep what you already have: repos somebody else wrote, a backend nobody fully remembers, infrastructure that has to keep serving while the new thing goes in. No rewrite, no migration onto our stack, no "first, replace everything." We attach to what is running and treat comprehension as an engineering job, with its own tools and its own gates. The new work is built inside that comprehension, with those gates running the whole time. At the end you keep what the contract names, and our engine leaves with us.

The industry insists on a rewrite because understanding someone else's system costs more than rebuilding it. Our method goes at that cost directly. We practice it on our own work, continuously, which is what produced Bonfire on PyPI, the open repos and the gates. The discipline is the method, not the headcount.

attach · comprehend · build · detach