Skip to content
← PARAM BAHIA

SYSTEM — THE ENGINE ROOM

The Framework.

Every project this month shipped absurdly fast. None of them are the interesting part. This is.

Look at the timeline and the pattern is hard to miss: a game in five days, a rental-intelligence product in one, a commercialisation run in three. The projects didn’t get easier — the system underneath them got real. The framework is that system: a spec-driven, orchestrated way of building where every project starts from the same scaffold — a briefing for any fresh session, a prioritised backlog, atomic numbered specs, an architecture map, decision records, runbooks — so no session ever starts from zero and nothing durable lives only in a chat window. Sessions are disposable; the framework is the memory.

It grew the way tools should: out of necessity, one project at a time. It started here, on this site, as a discipline for not losing decisions between sessions. Then it learned parallelism — an orchestrator terminal that writes the specs, makes the calls, and merges; worker terminals that each take one spec into an isolated worktree, build it, and hand back a completion brief; me as the relay between them. Work moves in waves: a batch of specs fans out, lands, gets adversarially reviewed, merges, and the next wave goes. The game ran twelve waves and fifty specs in five days. The day-job cockpit took over three hundred commits in ten. Every one of those commits traces back to a written spec with acceptance criteria.

The unreasonable effectiveness comes from what the structure does to speed. Specs make work parallelisable — five terminals can build five things at once without colliding. Decision records make it resumable — any session can pick up exactly where the last one stopped. Reviews make it trustworthy — nothing merges on vibes. The result is that the gap between an idea and a working thing collapsed to an afternoon, and the constraint moved from “can I build it?” to “what’s worth building?” That question turned out to have its own answer: once building stopped being the bottleneck, turning the builds into businesses became it — so the framework’s first descendant is a platform for exactly that.

→ APCP — the platform built on it

→ The timeline — the burst it produced

No screenshots — the framework is markdown, terminals, and discipline. The projects it shipped are the gallery.