The Chaos Manifesto

The method we are adopting. Not a culture statement: the rules that decide how a piece of work is sized, who owns it, what is written down before it starts, and who is allowed to change that writing once it exists.

In the author’s words

The rules of coding changed because of AI. One individual can now have much more impact on a product, and can even take on more roles. That allows us to have a more flexible framework, one that respects the skill, the motivation, the desires and the freedom of the developer.

It also means we can ask more transparency of them, maybe more than we used to ask for. Nothing is hidden. This is not to surveil and micromanage, it is to be able to know how far along we are without having to hold a full meeting for it. […]

It is also simply faster. Writing stories, slicing them, estimating them and moving them across a board is a large part of what a week costs, and an AI does not need the work pre-chewed in order to do it. What that ceremony used to buy us, we can now buy more cheaply.

We want to allow each individual to reach their full potential, and I believe that comes from granting them trust and freedom.

Joé, founder, 18 August 2026. Grammar fixed.

The rule

Agile stays the global structure. The unit of work is the trunk, not the ticket, and the price of that autonomy is transparency.

Each member owns bigger pieces of work than a sprint board would hand out, called trunks, with full freedom inside them. In exchange, we ask for transparency: every document a member works in is visible to every other member of the team. There are no secrets here, for anybody. A team of many, working as one.

That transparency is paid in artefacts, not in reports: everyone can open what everyone else is working on, all the time, without asking and without anybody writing a status update. What is never recorded is the person: no read receipts, no activity trail, no “last seen editing”, ever.

Two halves of one method

The manifesto is one text. On this site it is told in two halves, because it answers two different questions.

The prerequisite nobody can install

This method assumes a particular kind of person, and an organisation adopting it should decide that on purpose rather than discover it.

Every rule here trades supervision for trust: nobody is assigned work, everybody’s documents are open to everybody, and a spec is protected by agreement rather than by a gate. That works with people who are self-driven, who genuinely want to see something change, and who hold their own ideas firmly while respecting a colleague’s. With no ticket to arbitrate, a disagreement is settled between people or it is not settled at all.

And the stakes per person are higher than they used to be. AI means a team can be smaller for the same output, which does not dilute individual traits. It concentrates them. A mismatch that a twenty-person process would absorb is, at four people, most of the team.

How people think and work is a field of expertise of its own, and the manifesto is not written from inside it. What it asks is that a team think about it actively, before adopting the method and not after the first clash. A personality instrument can start that conversation. It is never a filter, a hiring gate, or a thing anyone is measured against.

Chaos, on purpose

The name is neither a joke nor an apology.

This method deliberately accepts more disorder than a board-and-ticket process does: work that runs in parallel and may collide, duplication that may turn out wasted, trunks that may be put back, decisions taken without a meeting, and a plan that is re-read from artefacts rather than reported.

It accepts that disorder consciously, as a strategy, never as a side effect. Every place the method allows chaos it says so, and says what the chaos buys: autonomy, speed, and answers that come from working code instead of from argument. The discipline is not in avoiding the mess. It is in choosing it each time, out loud, and knowing what you bought.

Chaos nobody chose is not this method. It is just an unmanaged project.