MODULES.md section 30's definition of done is circular as a promotion gate

architecture/MODULES.md §30's definition of done is used as the gate for deciding whether a path package becomes its own repository. One of its bullets requires:

the independent GitHub repository, README, CI workflow, generated coverage report, release tag, and tested-host compatibility evidence

Repository creation cannot be gated on already having a repository. As written, §30 can never be satisfied for a module that does not yet exist as a repo, which is precisely the case it is being consulted for.

How it was worked around downstream

ecommerce-laravel splits §30 at the point the repository exists:

• Promotion gate — everything the monorepo can prove: no App\ dependency, architecture tests green, the suite runs without a host, persistence contained, contracts versioned, coverage at its floor, no cross-boundary edit in the last N commits.
• Release gate — §30 in full, now answerable: repository, README, the three workflows, coverage report, tag, compatibility evidence, runbooks.

Written up at MODULE_DEVELOPMENT.md §6.

Ask

Split §30 upstream the same way, or state which subset is the promotion gate. Every product that reaches this point will otherwise invent its own split, and they will not agree.

Found while auditing ecommerce-laravel against the standards.

Read architecture/MODULES.md §30 first, then compare the downstream split described in docs/MODULE_DEVELOPMENT.md §6. Update the upstream documentation so the promotion gate is answerable before a repository exists and the release gate covers repository-level evidence. Done means the two stages and their evidence are stated without a circular requirement.