Overview | Operator Shell

/overview

Shell foundation

Route ownership, shared navigation, and truthful module boundaries live here.

Shared shell live

Overview

Operator shell foundation before workflow wiring

Production route target

This Worker owns the target shared control plane at dashboard.spot-scraper.com. OPR-01 classified the prior dashboard path as STATE C, so this shell is a fresh minimal Worker surface rather than a salvage path, and the current live dashboard still migrates from chaos.spot-scraper.com.

Locked routes

/overview, /chaos, /outreach, /activity, /settings

Every route is registered directly in the Worker. No hidden client-side route tree owns shell correctness.

Health contract

/api/healthz

The health endpoint remains schema-locked for route validation, dry runs, and deployment checks.

Access wall

One Worker, one shell, one control plane

Chaos and Outreach share one Access boundary in the target shell. The migration goal is to move the current live dashboard from chaos.spot-scraper.com into dashboard.spot-scraper.com.

Live modules

Chaos, Outreach

Chaos stays artifact-backed. Outreach is now hardened as a read-only foundation before browser actions land.

Next lane

OPR-07

Action wiring begins only after recovery classification, shell hardening, hostname migration, and Chaos rehab have already locked the shared foundation.

Trust boundary

Cloudflare Access at the edge, truthful modules in the Worker

Edge-first

Access model

Cloudflare Access protects the target application perimeter at dashboard.spot-scraper.com. The Worker does not invent browser session logic in this lane.

Expected headers remain CF-Access-Authenticated-User-Email and CF-Access-Jwt-Assertion.
The Worker stays focused on route ownership, rendering, and validation contracts under one shared shell.

Reserved routes

Activity and Settings remain visible so operators can orient to the full shell without guessing what is live.

Those routes stay factual and non-interactive until their owning lanes land.