Where it goes | Vision

The order is not a wish list. Each phase exists because the next one is impossible without it, and each one ends on a condition that can be checked rather than felt.

The order, and the reason for it

Phase	What it establishes	Why it comes here
Foundations	the site framework reduced to its core, continuous integration, the brand	nothing can be judged while the repository still carries another project's shape
`deck`	the first real format, end to end	one format proves the model or breaks it; it is cheaper to be wrong once
Sites	the sites, written with Récit	a tool whose own showcase is not made with it has not been tried
The model	story, configuration, JSON twin, languages	the twin and the translations must exist before six formats depend on them
`motion`	the second format, from a separate project	the first test of the claim: a second renderer, same source, no fork of the model
Alpha	packages published under a prerelease tag	publishing early is how packaging mistakes are found while they are still cheap
Then	report, book, webtoon, roadmap, calendar, stories	each one adds a renderer, never a second model
After 1.0	forms, images, glossary, maps, the scenario tooling	accepted, specified, deliberately after — they are not what the project is judged on

Two formats are shipped, the model is in place, and the alpha has not been published yet. The detail lives in the repository's plan, which is written in French and kept honest: it records what is done, what is interrupted, and what was decided without the maintainer.

How the plan is allowed to change

An audit of the whole repository was run against its own plan. It produced 163 findings — three critical — and they are being worked through in priority order rather than filed away. That audit was itself wrong in places, and the corrections are recorded next to the findings: one recommendation would have broken every footnote link, another named a schema that does not exist.

That is the intended posture: the plan is a hypothesis with a date on it. A decision taken without the maintainer is written down as such, so it can be reversed by reading one table instead of archaeology. A colour scheme decided one day was replaced the next, and both decisions are in the file.

What "done" means here

A phase ends on measurements, not on a feeling:

the checks pass, everything builds and typechecks;
the tests pass, including the round-trip over every story in the repository — a story that escapes it fails the build;
the screenshots match, compared in the exact container the continuous integration uses, twice in a row, because a test that only passes on retry is a test that does not pass;
a change to a published package carries a version plan.

The part that is not technical

Récit says where its code comes from: every borrowed file, font and asset has its line in the notice, with its licence. The model packages import nothing from the private site framework. If this project ever becomes something people depend on, that discipline is what will make it safe to depend on.