control tower / journal
Journal
engine connected
← Journal

008: marketing.tripshepherd.com control tower, read-first, in the seesight-ads repo

  • Date: 2026-09-01
  • Decider: Daud (directed); design by engine proposal
  • Status: active
  • Review by: 2026-10-15

Decision

The engine gets one UI: a Next.js control tower at seesight-ads/control-tower/, deployed to marketing.tripshepherd.com, reading the growth module through a new token-guarded read-only admin API and the journal/specs live from GitHub. v1 monitors everything and mutates nothing except its own annotations; spend and campaign mutations stay in the gated CLI actuators. Full spec: docs/marketing/specs/control-tower.md.

Evidence

  • The engine now spans four repos and a dozen dry-run flags; without one surface, activation state is only knowable by reading code. A read-first tower makes the human gate practical instead of aspirational.
  • seesight-ads already prototyped exactly this (platform/webapp control screens, AI-CONTROL-SURFACE.md), and boat-os §11.2 directs workflow surfaces to the OS layer, not the transactional backend.
  • The no-fake-data doctrine extends to the tower: disconnected sources render disconnected states. A dashboard that invents numbers would poison the same decisions it exists to protect.

Predicted effect

Once deployed with env set, the tower shows accurate live counts for every growth table within one minute of module activation, and the weekly digest becomes readable on demand instead of email-only. Measured by: each screen's numbers matching direct SQL counts during the activation checklist run.

Measured effect

(pending)