The Umbrella, Flipped.

§1 · Why the umbrella is upside-down

A traditional umbrella has one job: keep one person dry. The user stands under the canopy, the rain runs off the edges, and nothing is captured.

That's the wrong shape for this system. CircularOS isn't here to shelter the operator — it's here to catch what falls and count it. So the umbrella is inverted: bowl-up, rim-up, pole pointing down to the platform below.

What this means literally

Same doctrine as Build #32 · OP / Overstood Platform

The OP brand was chosen for the same reason: platform-not-shelter, bowl-up, black silhouettes. MD-450 is the doctrine that explains why. Overstood = you stand over the platform, the platform stands under you, but the platform's job is to catch the rain — not block it.

§2 · The three builds — the rim of the bowl

Every drop that falls into the bowl is caught by exactly one of these three rim arcs. No drop is lost. No drop is double-counted.

§3 · Every route in this umbrella

§4 · API contracts

§5 · Database DDL — the two new tables

op_ledger · Build #33

CREATE TABLE IF NOT EXISTS op_ledger (
  id            SERIAL PRIMARY KEY,
  type          TEXT NOT NULL,            -- page · doc · fix · section · api · agent-bug · deploy · decision · ping · test
  title         TEXT NOT NULL,
  summary       TEXT,
  route         TEXT,
  duplicate_in  TEXT,
  source        TEXT DEFAULT 'sovereign',
  severity      TEXT,
  window_start  TIMESTAMPTZ NOT NULL,    -- 1pm UTC anchor; auto-rolls when now < 1pm
  created_at    TIMESTAMPTZ DEFAULT NOW()
);

qr_tracker · Build #34

CREATE TABLE IF NOT EXISTS qr_tracker (
  id            SERIAL PRIMARY KEY,
  slug          TEXT UNIQUE NOT NULL,
  label         TEXT NOT NULL,
  target_url    TEXT NOT NULL,
  location      TEXT,
  purpose       TEXT DEFAULT 'other',
  status        TEXT DEFAULT 'active',
  notes         TEXT,
  scan_count    INTEGER DEFAULT 0,
  last_scan_at  TIMESTAMPTZ,
  created_at    TIMESTAMPTZ DEFAULT NOW(),
  updated_at    TIMESTAMPTZ DEFAULT NOW()
);

§6 · File map — what changed, where

§7 · Cross-build interlock — how they pass the catch

The three rim arcs don't operate in isolation — every catch flows down into the same bowl (the database) and pops up on the OP analytics card via /api/op-tracker/analytics. One pulse, three feeds.

§8 · Verification log — sealed 02 May 2026

§9 · Connected master documents