PRODUCT DEVELOPMENT FOR THE AGE OF AI
Calm the chaos with CalmChaos.
Your product is your growth engine. CalmChaos orchestrates everyone who builds it, people and AI Agents alike, so you can build at the speed of opportunity.
01 · THE SHIFT
The software team just became an ecosystem.
The people building your product no longer look like a team of developers. They work at different speeds, with different skills, different responsibilities and very different levels of autonomy. Some of them never sleep. Some of them aren't people.
- PACE · DELIBERATE
Software architects
Set the shape everything else depends on.
Needs: decisions that stay decided
- PACE · STEADY
Professional developers
Build the hard, load-bearing parts.
Needs: clear scope and fewer interruptions
- PACE · BURSTY
Vibe coders and domain experts
Build close to the problem, fast.
Needs: guardrails and a real path to production
- PACE · 24/7
Autonomous AI Agents
Work in parallel, around the clock.
Needs: a scope, a Claim through IceBerg and a Definition of Done
- PACE · ON DEMAND
Human and AI reviewers
Judge whether the work is right.
Needs: evidence instead of vibes
- PACE · ASYNC
Distributed teams
Hand work across time zones.
Needs: a record instead of another meeting
- PACE · STRATEGIC
Product leaders and founders
Decide what is worth building.
Needs: to see delivery without asking for a status update
The question is no longer how to manage developers. It's how to orchestrate an entirely new way of building software.
02 · THE GROWTH ENGINE
Your product is your growth engine.
It isn't a technology asset sitting on a balance sheet. How quickly you can build, evolve and deliver it decides how quickly you can answer customers, enter markets, launch capabilities and say yes to opportunities. Slow the product and you slow the business.
OPTIMIZATION
Do the same work for less.
Fewer hours, lower cost, tidier timesheets. Worth doing. Not why CalmChaos exists.
GROWTH · WHERE CALMCHAOS LIVES
Do more of the work that matters.
Turn every new builder, human or AI, into more product: more capabilities, more launches, more answers to customers, without the chaos that usually comes with scale.
More builders ≠ more progress.
Every contributor you add multiplies the coordination. Without a shared way of working, capacity turns into collisions.
More AI Agents ≠ more valuable software.
AI Agents produce volume. Value needs direction, review and a Definition of Done that someone actually agreed to.
Acceleration − orchestration = chaos.
Speed is only an advantage if it is pointed somewhere. CalmChaos is how you point it.
03 · THE BOTTLENECK
Don't let your growth engine become your bottleneck.
More builders. More AI. More opportunity. More chaos. Three agents open pull requests before lunch, a domain expert ships a prototype, decisions live in a thread nobody can find. Code gets faster; knowing what's true, what's next and what's shippable gets slower.
- HTD-F19Who approved this?
- HTD-F23AI Agent rewrote auth.ts. Why?
- ADR-006Decision lives in a thread
- HTD-D4Tests pass. Feature wrong.
- HTD-C83 AI Agents, 1 branch
- HTD-D12Idea dropped in chat at 3am
- HTD-F14“Who's on this?”
- StageZerospec_v4_FINAL_final.md
- HTD-F27Done (ish)
More builders than owners
Work gets started by whoever is awake, human or not. Nobody is sure who finishes it.
Five tools, no truth
The plan is in one place, the code in another, the decision in a chat. They disagree.
Right tests, wrong Feature
Everything is green. It is just not what anyone asked for.
Approval by vibe
“Looks good” from someone, about something, at some point.
04 · THE INSIGHT
AI accelerates coding. CalmChaos orchestrates delivery.
Writing code was never the hard part of growing a product. Deciding what to build, coordinating who builds it and knowing when it's truly done is. CalmChaos is the orchestration layer for that: a product and a method that hold at any speed and any number of builders.
05 · PHILOSOPHY
Orchestration, not bureaucracy.
The point isn't to slow anyone down. It's to let more builders build more, safely. Three rules make that possible.
Everything has an owner.
Every Capability, Feature and decision has a name next to it. Sometimes the name is an AI Agent. It is never “the team”.
Round avatars for people, square for AI Agents.
Nothing moves without a gate.
Work moves on only when its gates pass: approval into PCDS, Prerequisites met, review passed, publication confirmed. A gate passes on evidence, not enthusiasm.
Approval · Prerequisite · Review · Publication
Every decision leaves a record.
Approvals, Claims, reviews and changes to the rules are written to an append-only audit trail.
Read-only. Searchable. Exportable. Boring on purpose.
06 · THE METHOD
StageZero, Drafts, then PCDS.
Before any work starts, a Workspace agrees its ground rules in StageZero. Proposed work waits in Drafts until it is approved into PCDS. From there every Feature moves through the same four States, and it counts as Published only when publication is confirmed. The five notches in our logo are the gates: conditions work must meet before it moves on.
StageZeroPrepare the ground
What happens
The Workspace agrees its setup, Members, ADRs and API Contracts before work is proposed.
Gate: it passes when
Setup is complete and every open decision has an owner.
DraftsPropose the work
What happens
Proposed Capabilities and Features are written down and assessed by Priority, Complexity and Dependency. No score decides for you.
Gate: it passes when
Someone authorised chooses what to put forward.
PromotionApprove into PCDS
What happens
Approved Drafts become Features in PCDS, each in one Product, grouped under a Workspace Capability.
Gate: it passes when
The Workspace's required approvals are in and the Product Owner promotes it. AI Agents never count toward approval.
DO → DOINGStart the work
What happens
People move a Feature to DOING. AI Agents claim it through IceBerg, CalmChaos's MCP Server. Any Prerequisite must be met first.
Gate: it passes when
The Feature is in DOING, with an owner and a scope.
In ReviewCheck the work
What happens
Reviewers read the work and its evidence. AI Agents can review as a second opinion. Review is not approval.
Gate: it passes when
The review passes and the Feature moves to DONE, Status Waiting.
PublishedConfirm publication
What happens
Publication is reported through IceBerg. A merge or a deploy alone does not count.
Gate: it passes when
Clarity confirms the report, the Status becomes Published, and the trail lands in Audit.
Every piece of work has a State and a Status
- DO
- DOING
- DONE
- DEFER
- Queued
- Active
- In Review
- Blocked
- Waiting
- Published
State says where the work sits. Status says how it's moving. A Feature with a Prerequisite waits until that Feature is DONE or Published; Features without one run in parallel. Nobody builds on sand, however enthusiastic they are.
07 · EVERY KIND OF BUILDER
One way of working for every kind of builder.
We gave AI a keyboard. CalmChaos gives it a process. AI Agents are first-class builders here: named, scoped and accountable. So are vibe coders and domain experts. People decide what's worth building and whether it's ready to ship; everyone else gets a clear path to contribute.
| Who does what | People | AI Agents |
|---|---|---|
| Set the ground rulesStageZero: setup, Members, ADRs, API Contracts | Yes | Suggests |
| Propose the workCapabilities and Features, as Drafts | Yes | Suggests |
| Start a FeatureWhen its Prerequisites are met | Move to DOING | Claim through IceBerg |
| Build and testInside an agreed scope | Yes | Yes |
| Attach evidenceFrom whoever did the work | Yes | Yes |
| Report publicationThrough IceBerg | Yes | Yes |
| ReviewRead the work and the evidence | Yes | Second opinion |
| Approve and governSign-off, ADRs, gate rules | Yes | Never |
AI Agents never approve.
They can request, build and review. Approval is human, always, and the interface never pretends otherwise.
DONE isn't Published.
A merge isn't publication, and neither is a deploy. A Feature is Published only when its publication is reported through IceBerg and confirmed by Clarity.
Round means human. Square means AI Agent.
Everywhere in the product you can tell at a glance who did a thing. It sounds small until it's 2am and it isn't.
08 · IN PRACTICE
The orchestration layer, in practice.
Capabilities in Sequence. Features by State.
Open a Capability to see its Features as a list or as a board with four lanes: DO, DOING, DONE and DEFER.
A Prerequisite says which Feature it waits for.
Proposed work waits in Drafts.
Each Draft carries its Priority, Complexity and Dependency. Filters narrow the list; no score ranks it. Approved Drafts are promoted into PCDS.
AI Agents never count toward approval.
The receipt for everything.
A read-only record of actions and decisions by people and AI Agents. Search it, filter it and export it.
Round for people. Square for AI Agents.
09 · WHY IT'S DIFFERENT
Not a tracker. An orchestration layer.
THE OLD WAYAdding builders adds coordination overhead.
IN CALMCHAOSEvery builder, human or AI Agent, joins the same workflow, so capacity grows without the collisions.
THE OLD WAYAI makes code faster, so review becomes the bottleneck.
IN CALMCHAOSAI Agents build and attach evidence. People review proof, not guesswork, and decide faster.
THE OLD WAYSpeed and governance are a trade-off.
IN CALMCHAOSGovernance is the reason you can go fast: owners, gates and a record make it safe to say yes.
THE OLD WAYThe roadmap depends on who remembers what.
IN CALMCHAOSCapabilities run in an agreed Sequence, and every Feature knows which Prerequisite it is waiting for.
10 · WHO IT'S FOR
For teams whose roadmap just got bigger than their process.
Founders
Turn a small team plus AI Agents into a product engine that can chase every opportunity.
CTOs and engineering leaders
Adopt AI at scale and still answer “who decided this?” without a séance.
Product leaders
Say what done means once, then watch more of the roadmap actually land.
Architects and developers
Keep the hard parts sound while everyone else moves fast around them.
Domain experts and vibe coders
Build what you understand best, with a path to production instead of a pat on the head.
EARLY ACCESS
Are you ready for the new world of software development?
Calm the chaos. Accelerate product growth. We'll open CalmChaos to a small number of teams already building with AI Agents. When sign-ups open, tell us where to write; we'll reply like humans.