Status · what is missing
What this site cannot do
Two registers, and the difference between them is the point. The first is infrastructure-blocked: the work is understood and would ship, but it needs a database, a payment path or another person. The second is environment-blocked: nothing here can produce it — a browser, a domain and a second machine are not build steps. 6 bets and 8 environment items are open, and every one names what would make it real instead of estimating what it would look like.
A · Infrastructure-blocked
from /roadmap, which carries the full four questions per betReal accounts & favourites backend
spec onlyA database, a session strategy, a privacy page that mentions storage, and a deletion path. Roughly the first two weeks of a real backend.
Would refuse Social sign-in buttons that do not work, and 'sign in with Google' as a decoration. If the button exists, the flow must complete.
Prompt re-run service
spec onlyModel keys and a spend cap per visitor, plus a queue that can be killed. Prompt runs cost money the moment they are real.
Would refuse A 'run' button that returns canned output. If the service is down the page must say so, not simulate a result.
Theme Studio as a product
partly builtStorage and conflict handling, plus a paid tier if themes become the flagship — which needs billing, which needs accounts.
Would refuse Paywalling the token export that already works today.
Community moderation marketplace
spec onlyIdentity, conflict-of-interest rules, and a payment path. The expensive part is not the marketplace, it is the dispute handling.
Would refuse Paying per approval. A reward for saying yes is a reward for saying yes.
Learn certificates
spec onlyA verification endpoint and an identity — the artwork is the easy half.
Would refuse A badge that looks verified when it is self-asserted. The label is part of the design, not a disclaimer bolted on.
Desktop helper app
spec onlyCode signing on three platforms and an update channel. This is the most expensive bet per unit of value on the list.
Would refuse Bundling the catalog. The app would fetch, cache and expire — a bundled index is stale the day after release.
B · Environment-blocked
nothing in this repository can produce these| Missing | What it needs | What exists instead |
|---|---|---|
| A real Lighthouse score | A browser. The build has none: every performance figure on this site is measured from files and responses. | Transfer sizes, chunk counts, HTML weights and font preloads, all from the build report — and the pages say which of those is a proxy. /perf |
| A second measurement series | A second machine, or a runner. One build report cannot tell a regression from the noise of the machine that produced it. | A double-build determinism concern is recorded, and every number keeps the build that produced it. /perf/build |
| Field vitals | Visitors. A lab measurement is not a field measurement, and this site has no analytics by design. | Nothing, and the pages that would show it do not pretend to: there is no vitals panel to fill. /metrics |
| Visitor, signup and revenue numbers | Real traffic and a payment processor. There is no backend and no checkout. | Every count on the site is a property of the catalog — copies, runs, components — not of its audience. /metrics |
| A one-click CodeSandbox link | A round trip to codesandbox.io. That was attempted while writing the integration and failed from here (no response, HTTP 000). | The file bundle is downloadable and the page states which half is missing. /integrations/codesandbox |
| A live domain | DNS. Every canonical, card and feed URL is built from a placeholder base that is documented as such. | The base is one constant with one environment override rather than strings scattered across metadata. /quality/schema |
| Absolute-URL round trips from the harness | Network egress. The suites request the local server; a fetch to a public URL fails with ENOTFOUND inside this environment. | The checks that need an origin take it from the incoming request, so no origin is hard-coded anywhere in the tree. /quality/gates |
| A browser-run accessibility session | A person with a browser and a screen reader. Seven checks are listed for exactly this and the page says none has been run. | The static half: 292 documents and 385 served pages, no findings, plus the counts that say what the pass cannot see. /quality/aria |
The rule behind both registers is the one the roadmap states and the rest of the site follows: if a thing needs explaining, it does not ship. A fake dashboard is not a smaller version of a dashboard, it is a smaller version of the site's credibility — which is why the numbers that could not be measured are named here instead of estimated somewhere else.