The manifesto in practice

A principle earns its place when it helps someone make a difficult decision. It also needs to say where its advice ends. “Archive first, delete second” sounds sensible until the material is something you should no longer retain.

This guide puts the twelve synthesis principles to that test. Each chapter explains the problem a principle addresses, follows a concrete decision, and examines a case where applying the words literally could make the work worse. The scenarios are illustrations, not reports of measured results or accounts of a particular organization.

The manifesto is the short statement people sign. These pages are commentary on it. Three principles need more precise wording, and the wording and history page sets out those proposals beside the original text. Existing signatures are not endorsements of this guide or of those proposed changes.

What changes in the work

Imagine a team preparing a report with an AI assistant. The assistant has summarized the source material, produced a draft and announced that the report is ready. The team still has several decisions to make.

Someone checks whether the source supports the draft’s central claim. The team keeps the relevant evidence with the report, including the question that remains unanswered. If a required check of permission to distribute the report is unavailable, sending waits; authorized editing can continue. The next person can find the current draft and the decision about distribution without reconstructing a conversation.

That is the kind of work these principles ask for. The same team could misuse them. It could recheck every harmless detail until the report is late, retain private source material indefinitely, or demand approval for every sentence while calling that human judgment. Each chapter takes those costs seriously.

The practical aim is for people to understand the work well enough to direct it, assess it and continue it. Better tools can help. The responsibility for deciding what is worth doing remains with people, including those who will live with the consequences.

How to use the guide

Start with a decision you face. If the question is whether a result is ready, read about evidence and incomplete work. If you are handing work over or changing tools, read about continuity and portability. If two principles point in different directions, the conflicts page works through those choices.

The complete guide collects every chapter and the companion pages in one place, including a print view. You can read or share an individual principle without asking someone to study the whole system first.

Before signing, read the questions about support, independence and obligations. A useful conversation can end in a signature, a disagreement or a better explanation. None of those needs to be hurried.

Familiar practices, a shared discipline

Checking sources, leaving usable records and keeping people accountable are established practices. The manifesto brings them together around work that now crosses people, AI assistants, sessions and tools. Its paired values also draw on the form of the Manifesto for Agile Software Development.

The explanations here offer reasons to try these practices. They do not establish that adopting the whole manifesto improves every team’s results. On a real task, look for a concrete benefit: a mistake caught before release, a handoff someone can use, or a tool change that preserves enough context to continue. Count the effort required to achieve that benefit too. A practice that keeps producing paperwork without helping anyone decide deserves another look.