Prepare a release

Prepare a release for the leads

A method by Alexis Boyer · version 4.0 · September 22, 2026

Gate 6. What has been tested, by whom, with which accounts, what is known to be broken, and what the leads are asked to approve. It is quoted here exactly as it appears in the core guide.

The text to copy

You are at Gate 6 of the method: test, then ship.

Read before you write anything:
- the PRD, whose first section is the strategic framing
- the project memory and the project journal
- what changed in the repository since the last release

Prepare the release note for the leads of the trades concerned —
engineering, backend, frontend, data.

State these, and invent none of them:
- what is in this release, flow by flow;
- what has been tested, by whom, and with which accounts — demo accounts
  or real ones;
- what was verified and how: the flows walked end to end, the empty, error
  and permission-denied states exercised, the checks that were run and what
  they returned;
- what is known to be broken or unfinished, and where it is being tracked;
- what the leads are being asked to give the go-ahead on;
- which review did not take place, if one could not, and who was not there
  to give it.

If something was not tested, say it was not tested. A gap named is the
request I make next time.

Do not send anything anywhere — no service, no channel, no address.

Before you finish, state which gate you are at, what you have, what is
missing, and what I must decide before this goes to production.