The whole of PCI World, drawn before launch.
Community rooms, an open forum, verified careers, contributor publishing and the operator's launch board are built, tested and deliberately switched off until the moderation, legal and editorial decisions land. These pages walk the entire surface anyway — every screen, every rule, every refusal — so nobody has to imagine what launches.
- Five areas, twelve screens
- Every rule quoted from the real server
- Static pages — no flag can hide them, no API can 404 them
Community
Short-lived topical rooms, open to guests, where every message is reviewed before anyone sees it.
- Rooms
- Inside a room
Forum
Project controls practice, discussed in the open — readable by anyone, crawlable by search engines, held before publication.
- Discussions
- A thread
- The composer
Careers
Roles from employers a person at PCI has verified, applied to with recorded consent that the applicant can withdraw.
- Job board
- A job page
- Employer portal
- My applications
Publishing
A contributor desk with declared interests, and an editor’s queue where nobody — however senior — can approve their own work.
- Contributor desk
- Editor’s queue
Operations
The operator’s launch board: every feature ships off, each has a switch, and some refuse to move until real policy text is published.
- World Admin
What already runs
The daily challenge, the challenge library, Writing and the Passport are live now — the tour covers only what comes next.
Go to PCI WorldLaunch is a decision, not a deployment
Each of these surfaces sits behind a feature switch that ships off, and the ones that touch people hardest refuse to run until a prerequisite is recorded: a contracted moderation provider for the rooms, an applicant privacy notice for careers, contributor terms for publishing. That refusal lives in the endpoint, not the interface — so these pages can show you everything while the deployed routes honestly answer 404. When the decisions land, an operator turns each surface on from the launch board. Nothing here requires a redeploy.
How to read this tour
The amber registers are real
Every screen opens with the rules the real server enforces. Those sentences are quoted from the system, not invented for the page — the drawing cannot enforce them, the endpoints do.
Nothing here is wired
These are plain static pages: no API calls, no database, no feature flag. Buttons answer with the words the product uses, and nothing you type is stored, sent or checked.
The endpoints already exist
Each screen lists the API calls it needs under “What this screen calls”. Almost all of them are built and tested today — the tour is the map for whoever wires the last mile.