Every card on the Modules page carries a status word and sometimes a percentage. This page explains exactly what those mean, where they come from, and what stops them from quietly going stale — so you can judge how much weight to put on them.
Applies to /modules/ and every /modules/* detail page · system introduced 2026-07-12
Module and roadmap status used to live in several places at once — the homepage, a prototype modules page, and six individually hand-written detail pages. They drifted. Several still said WARMING, LOCKED or COMING SOON for systems that had already fully shipped: the Burn Center, Governance, Community Events and the Transparency Center.
That is the failure this system exists to prevent. There is now one registry that every surface reads from, a fixed vocabulary it must use, and an automated check that fails if the registry contradicts itself.
A module can only ever carry one of these ten values — never a vague word like "warming", "soon", "almost" or "in build".
| Status | What it means |
|---|---|
live | Shipped, working, publicly reachable today. |
beta | Working but not fully validated or rolled out — for example an Android beta, or an iOS build that has not been verified. |
partial | Some real, documented sub-items are done and others are not. The card lists which. |
ongoing | Not a software deliverable at all — a recurring activity. |
planned | Named in the roadmap, not started. |
deferred | Named in the roadmap, intentionally not scheduled. Not cancelled — see the Bridge section below. |
blocked | Waiting on an external dependency that does not exist yet. |
retired | Was live, deliberately taken down. |
historical | An early concept superseded by something real. Kept as a record, not an active roadmap item. |
internal | Real and live, but architecture rather than a place you can visit. No card is shown for these. |
A module's status describes the software. A separate flag marks whether the activity it enables is a recurring programme that never reaches "100%".
Governance is the clearest example: the voting software is fully shipped, so its status is live — while individual proposals and votes are an ongoing programme, so it also carries an ongoing-operation flag. The Burn Center is the same shape: the software is finished, the burns continue.
live module with ongoing activity is not an incomplete module. Conflating the two would let us either overstate finished software or understate a finished system because its programme continues — so the registry keeps them as separate fields.Every phase of the original roadmap is reconciled, item by item, against what is real today. Each item is stated independently and linked to its module where one exists.
A phase is never flattened to "complete" while any of its items are not. Phase 5 is deliberately marked ongoing rather than complete, because the Cross-Chain Bridge is deferred and Platform v2 enhancements are not started — even though Governance v1, inside that same phase, is fully complete.
The Bridge is deferred. That word is doing precise work, so here is exactly what it means and does not mean.
On record, 2026-07-12: the Cross-Chain Bridge commitment is retained on the original roadmap. The commitment remains accepted, and implementation is intentionally postponed while WinLEW completes and operates its current community, governance, reward and transparency systems.
A validation step runs against the registry as part of the test suite. It fails — loudly, blocking the change — when any of the following is true:
live has no route;That third-from-last check is the one that matters most to a reader: a module cannot claim to be live and link somewhere that does not exist.
The Modules page and the homepage's roadmap grid both fetch the same computed status payload at load time and render entirely from it — the same approach the Governance, Partners and Events pages already use. Nothing is rewritten at runtime; the registry is only ever edited by a person, in source control, and every edit goes through the validation above.
The individual detail pages own their own longer explanations, screenshots and narrative. What they are not allowed to own is status, progress, route or dates — those come from the registry alone, so the same claim cannot say two different things in two places.