These are super-admin screens. They show what is built for each vertical site, who may see it, where its hostnames point, which leads it has taken and what its prices read from. Most of it is read-only; the few controls say on the screen when they are switched off.
The overview and the registry controls
Vertical sites has one row per site. The columns say whether its kit pieces exist, whether it meets the launch-check claims floor, how many claims are live and when the next one expires, and its consented first-party event counts over thirty days. A low event number is not a visitor count: a visitor who has not allowed analytics is not counted at all.
- Stage. Each site has a stage and a ceiling set in code. A stage above the ceiling is shown as capped and is not honoured.
- Kill switch. Throwing it takes one site out of public view at once; clearing it puts the stage back.
- Allowlist. Workspace ids that may see a site before it is public.
- The controls work only when the registry table can be read. When it is not applied yet the screen says so and every site keeps using its code setting, exactly as before. When it cannot be read, public exposure is held at preview.
- An action that raises exposure asks for a fresh sign-in check first; the screen says when yours is stale.
The launch bar under it is computed from the repository at build time and changes nothing. A claim that must be live today, or seven days of green probes, is worked out when the check runs, so it counts as unmet there.
Host health
Host health lists every finocket.com hostname and vertical doorway with what it is allowed to serve. Probes are off unless they are switched on, and a host that was not probed says not measured rather than reading as healthy.
When the hosts engine is switched on, the same screen can plan, dry-run and apply the Cloudflare and Vercel steps for the hostnames, apply the dev hostnames only, and roll back the last apply. Applying changes live DNS and asks you to confirm first. No token is ever shown on the screen.
The lead queue
Leads lists every lead a vertical site took, who owns answering it and where it stands against the one-business-day response target. Three states are kept apart on purpose: the feature is switched off, the table is not applied, and there are genuinely no leads. Pick an owner for a lead, and mark it actioned once somebody has answered. A lead erased under a data request stays listed as erased.
Pricing and offers
Pricing is read-only. It shows the plan catalogue as the table holds it, or the code fallback with the reason, whether the catalogue agrees with the public pricing page, the drift setting, and the price each vertical site refers to. Prices are edited in billing and add-ons, never here.
Offers lists every offer. Saving a draft shows a preview, and a different admin has to approve it: the person who wrote a draft cannot approve it. Writing needs the offers editor and the offers table to be switched on; with either off the list is read-only and the screen says why.