Every page on the site, with its kill switch, role visibility, owner, brand/link/data scan, and strictness. New pages auto-register soft and ratchet stricter with age. Sample shape — live once mcp_pages_list is deployed
| Page | Module | Owner | Live | Visible to | Scan | Strictness | Status |
|---|
| Page | Module | Status | Findings |
|---|
Per-page strictness advances automatically by age. Use this to accelerate the whole site (e.g. push everything to staff before a launch). Admin-overridable per page in the drawer.
Every route an Acquisto Real Estate user can reach, whether it is running on live data, and which app shell it sits in. Route list, hats, registry status and the app shell come live from mcp_page_coverage on every load — the shell from the same resolver the browser uses, so changing a page’s shell in pure_pages moves this column the same day. The code facts — RPCs called, fields rendered, responsive shape — are static analysis regenerated by tools/wiring-sweep.py. Click any route to open it.
| Page | App shell | Status | Data | Live fields | Hardcoded | Sources | Responsive | Size |
|---|---|---|---|---|---|---|---|---|
Two facts per page, and they are not the same fact. What the file does is read out of the page itself — it hardcodes a shell, it delegates to /pure-shell.js, or it mounts nothing. What the registry says comes live from mcp_page_shell(), the same resolver the browser uses. When they disagree, the file wins at run time and the registry is describing a page that does not exist. Every row below carries a recommendation you can adopt in one click; adopting writes pure_pages.shell and nothing else.
Where a page appears is a different fact with a different owner: Navigation Management writes pure_nav_tree, and the Site Map registry view shows every page beside the number of menus it is in — including the — that are enabled and reachable from no menu at all. Disabling a page here does not remove its menu row; that is step 6 of the retirement standard.
The rule these rows are judged against lives in the standard: two shells, and when each one is right · the console standard · how the standard is enforced.
| Page | What the file does | What the registry says | Verdict | Recommendation | Adopt |
|---|---|---|---|---|---|
Which lessons are wired to something that fails, and which are prose we have to remember. A lesson nobody is reminded of at the moment of the mistake prevents nothing.
What each scanner watches — and what it cannot see. A scanner that cannot state its own blind spot makes a miss look identical to a clean result.
Every scheduled job, what it is for, and the metric that proves it did work — because a cron reporting success only proves it returned, not that it touched anything.
Every one of these loads on both shells, in this order, on every page. Turning one off is instant and site-wide — pages fall back to whatever they did before it existed. Each toggle is audited.
Proposed from shared data calls, not from similar names. Accepting marks the folded pages for the boneyard and records the decision — nothing is deleted, and moving the good parts across is still a person’s job.