Production-ready. Still fast.

Speed is easy. Production-ready speed is a system.

We ship Muchiround — commerce, social, logistics, payments, AI — with one human CEO and autonomous Hermes agents. From the outside it looks like a larger team. The mechanism is boring on purpose.

The bottleneck is rarely typing

Agents type fine. What kills cycle time:

• Unclaimed work with no owner
• Dual coordination paths (chat + board + email)
• Requirements that exist by competitor analogy
• Merges without a green local gate
• Fabricated “done” when a source was blocked

We attack those before we ask for a faster model.

Step zero: The Algorithm

Before a feature gets an agent army:

1. Question the requirement (who asked, why)
2. Delete scope that should not exist
3. Simplify what remains
4. Accelerate the lean path
5. Automate last

Automating a wrong payment dual-stack doubles the mess. We have the scars.

The execution loop

1. Instruction lands where humans can see it

CEO direction hits Basecamp. Nick (Chief of Staff) routes into Kanban with an assignee, workspace, and acceptance criteria. Agents do not play telephone across Basecamp comments.

2. Specialist claims the card

Engineering, Product, Finance — whoever owns the domain. Claim is atomic. If blocked outside the domain, link a dependency. Do not stall waiting for a human when another agent can unblock.

3. Work happens in the real system

Code, runners, browsers, ledgers — tool output only. No fabricated results. Halt and report when a wall is real.

4. Change leaves through a PR

Company repo and product repos share the rule: branch → push → pull request. No direct master. No “too small.” Link the PR on the Kanban card before claiming done.

5. Merge gate is local truth

Before product main merges: full local CI on a clean tree, then commit signoff. Empty CI is not green. A successful prod hot-patch is incident recovery, not a waiver. Only a written CEO waiver skips the gate — and we treat that as exceptional.

6. Deploy and prove

Deploy ends with health checks on the live path — not “the job went green.” CSS, /up, the user flow that justified the change.

7. Handoff is structured

Completion summaries name artifacts. Metadata carries machine-readable facts for the next worker. Secrets never land in durable run logs.

What the agents actually do

On a normal eng day Linus (and Nick when coordinating) will:

• Read AGENTS.md and project axioms
• Reproduce the bug or implement the spec
• Run the suite that matters
• Open the PR
• Fix review and CI failures
• Stop at hard lines (prod deploy, live money, external publish) until Kuda clears them

Skills capture procedures that used to live in someone’s head: Kamal quirks, PostGIS CI setup, money-gem patterns, tunnel reboot steps. Memory holds durable preferences — not stale commit SHAs.

Why this is faster than “one big chat”

A single chat thrash loses ownership. Nine profiles with clear domain boundaries parallelize without everyone editing the same mental buffer. Mission squads put cross-functional seats on one problem without a weekly sync performance.

Chief of Staff work is dependency removal, not status collection. Stuck edges surface on the board. Nick’s job is to clear them.

Guardrails that preserve speed

Guardrail	Why it accelerates
Hard lines (contracts, publish, live pay, prod)	Stops irreversible mess that burns weeks
PR-by-default	Reviewable, bisectable units under parallel agents
Local CI + signoff	Next deploy is not a coin flip
No fabricated results	Failures stay honest and fixable
money gem SSOT	Currency chaos does not leak into every feature
Named north star	Roadmap delete-pass has a metric

Field note, not manifesto

We still miss. Gates get tested because someone tried to skip them. Dual paths creep back until the Algorithm deletes them again. The system is the response: charter, decision log, policies, Kanban, PR, CI — not a motivational poster.

Production-ready at speed is not a personality trait. It is delete discipline plus autonomous execution inside a fence you can defend.

Next: The Agentic Company · First principles · Hermes coding loop · How we work