Alerts

An alert re-fires every run while its condition holds, and closes by itself the moment the evidence goes green. Acknowledging puts your name and your reason on it and silences the notification — it does not close the row, because an alert you can dismiss once is an alert you will dismiss always.

Revenue

Sessions and payments come from Stripe, refreshed by the reconciliation job. Recurring revenue is reported beside one-off kit sales, never inside them.

Checkout, by day

By product, last 90 days

Payments we cannot tie to an entitlement

Unmapped queue

Customers

Listed by the address that paid, not by account: most buyers have paid and never signed in, and an account-first list would simply not show them. Opening a record is itself an audited action, and it renders their data read-only — we never issue a session as them.

Access attempts

Who tried to sign in, what they hit, and — when the address they typed holds nothing — which address on their domain actually holds the entitlement. So a reply can name the right address instead of asking the customer to guess again.

The people who email us to say they are stuck are a small fraction of the people who are stuck. This is the rest of them.

Activity

What customers have actually done, newest first. Every row is an event a person caused — a sign-in, a download, a self-check, a vote. Nothing here is inferred.

Votes

What people are asking us to build next, and who asked. Seven people want a thing is a statistic; these seven providers want it is a phone call.

Searches

Every search on the kit page is a buyer telling us, in their own words, what they came for. The misses are worth more than the hits — a hit only confirms we have what they wanted; a miss names something a visitor with intent expected us to sell and we do not. That list is an ad keyword we are not bidding on and a document we have not written, at the same time.

Nothing matched

Terms that have never once returned a document in the window. Read this before writing the next kit and before the next ad set.

Everything searched

Most-asked first. Anonymous by construction — a term and a count, never a person. It may inform what we write and what we bid on; it must never be used to decide anything about an individual customer.

Support

The one-business-day promise, measured rather than remembered. Weekends are excluded; public holidays are not modelled, so on a holiday this clock runs slightly fast — it errs toward answering sooner.

Outbound queue

Replies the console has written and the host has not yet sent. This page holds no mail key — it queues, and a worker delivers. An empty queue means everything typed here has actually left the building.

Compliance Ops

Our own supply chain. An instrument counts as verified only when the authorised version has been opened at the primary source and the extract kept beside the work — a summarised fetch has invented statutory text three times, and each fabrication was internally coherent.

Broadcast

Compose, preview against suppression, canary, then release in batches. The console cannot express an unbatched send: batch size and interval are required, because one successful send proves the mechanism and never the capacity.

Actions

Gated actions are staged, never executed here. This page writes a proposal; a worker on the host holding the actual keys picks it up once confirmed. The browser has no Stripe key and no mail key, so a one-click price change is not a rule we follow — it is a thing this system cannot do.

Stage a gated action

Audit

Append-only, and it includes reading — every customer record opened is a row here. The panel gets the same evidence discipline we sell.