customer workstation

Your box, your console, your evidence

Everything runs on your machine. The console opens in your browser, the panel sits on your desktop, and nothing leaves the box unless you export it.

The console

The full picture in your browser: agents, countries, live connections, incidents, receipts. Open it with your key — the address carries it once, then keeps it out of sight.

The desktop panel

A small always-on window: how many agents are on the box right now, how many confirmed, the graph of the watch, and the critic's verdict — visible proof something is watching.

The standing critic

A standing critic audits the work against your own rules, live, and shows his verdict on every surface. Cyan: all holds. Amber: a demand is open. He is never silent and never off.

Setup — ten minutes, one machine

  1. Place the estate. Put the zday-lab folder where it will live (for example C:\zday-lab). It needs Python 3.11+ and nothing else for the core watch — the panel's graph uses two common imaging libraries.
  2. Start the supervisor.
    cd C:\zday-lab
    python api.py 8788
    The API, the watcher and the overseeing eye come up together. The overseer seals a manifest of every organ and heartbeats each pass.
  3. Open the console. Browse to http://127.0.0.1:8788/console?key=YOUR-KEY — your key is issued with the install. The address bootstraps the key and strips it from the bar. Every keyed request after that is sealed into the audit chain.
  4. Start the desktop panel.
    pythonw desk_hud.py
    A small window docks on your desktop: agents on this box, the watch graph, the critic's verdict. It is the proof-of-watch you can glance at.
  5. Watch a normal day. The homepage answers the daily questions: how many agents are on the box, which countries they talk to, anything new, anything drifting. Quiet is normal — quiet with a heartbeat is the point.
  6. When something happens, open the dossier. An incident card names who, where and why, and links the sealed evidence rows. Mark it REAL or NOISE — your verdict is itself sealed and teaches the learners. Unsure is allowed; it is never treated as a signal.
  7. Export when someone asks. The export builds a zip: incident dossier, CSVs, receipts, manifest, public key. Hand it to an auditor, an insurer or a customer — they verify it without an account and without calling us.

What "good" looks like

The panel shows a living heartbeat. The overseer's receipts chain verifies. The critic is cyan. Nothing new is on the box that you didn't put there — and if there is, you're looking at its name, its country and its evidence within the minute.

What it never does

Never sends your machine's data anywhere. Never deletes or trims your evidence. Never closes an incident because the software "feels" it's fine — closures carry evidence, and your verdict outranks the machine's.

See the catch first Read how it works