Skip to content

title: UCCA — RTOpacks Legacy Cleanup Brief — Tier-4 execution doc_id: UCCA-RTOPACKS-CLEANUP-BRIEF-01 type: execution brief — per-item config audit, repoint/retire verdicts, live redeploys. Scoped strictly to Tier 4 of UCCA-RTOPACKS-CLEANUP-RECON-01. layer: ground canonical: false status: DRAFT — executable on filing. Tier-3 gate RESOLVED 2026-07-03 (Tim, confirmed with RTOpacks: they self-manage their own domain now). §2 records the ruling and its ripple. authored: 2026-07-03 NYC (UCCA session, against the recon of the same date) relates_to: UCCA-RTOPACKS-CLEANUP-RECON-01 (the inventory this executes) · ADR-0002 · ADR-0003 · UCCA-INPUT-PATH-BUILD-BRIEF-01 §Step-5 (owns Tier 2) · CANON-CULL-SPEC-2026-07-01 (owns docs) discipline: no blanket rm. Every item: verify live state → verdict → apply → redeploy → Full Cycle (Infrastructure-State snapshot + referencing docs). One worker at a time, verified healthy before the next. Account e5a98302 confirmed before every command; f95d4537 never touched.

UCCA — RTOpacks Legacy Cleanup Brief (Tier 4)

What this is. The execution brief the recon called for. It covers Tier 4 only. Explicitly out of scope: Tier 1 (done 2026-07-03), Tier 2 (worlds/ + tga_data/ — owned by the build brief's re-source-then-sever Step 5; a delete here breaks the live generator), and the 170 rtopacks-referencing docs (owned by the staged CANON-CULL banner sweep — reframe, don't delete). If execution surfaces anything that looks like it belongs to those, stop and report; do not fold it in.

1. Standing rules for every item

  1. Verify before verdict. The recon is a day old and says so — confirm each path, binding, and worker's live state before acting. If live state contradicts the recon, the live state wins; note the divergence.
  2. Three verdicts per item: KEEP / REPOINT / RETIRE. Recorded in the completion report with one line of "how we know" each.
  3. One live redeploy at a time. Deploy, verify the worker healthy, then move to the next. No batched redeploys.
  4. Full Cycle per item. Any applied change updates the Infrastructure-State snapshot and any doc that names the worker/binding, in the same pass.
  5. Retired ≠ erased. A retired worker's config is removed from deploy surface; its final wrangler config is captured in the completion report before removal (cheap, and it keeps the fossil discipline).

2. Tier-3 ruling — RESOLVED — and what it downgrades to

Ruling (Tim, 2026-07-03, confirmed with RTOpacks): RTOpacks self-manages its own domain now. UCCA does not operate rtopacks.com.au.

Consequence: the recon's Tier-3 framing is stale — it read UCCA's Terraform declarations as declaring the client's live site. If the ruling is right, those declarations are fossils: .tf files (and possibly state entries) pointing at a zone UCCA no longer runs. Tier 3 downgrades from "a decision that could drop a live site" to Terraform state hygiene — still not a blanket delete, still its own small paper, because the failure mode changes shape rather than vanishing (destroy against stale state can still do damage if state and reality disagree in the other direction).

Item 0 (this brief, read-only, first): ground the ruling in bytes before anything relies on it — - list zones in e5a98302 and confirm rtopacks.com.au is absent; - terraform state list in infra/ucca-infra and record what it still claims; - report the pair. Ruling confirmed by live state → recon Tier 3 gets a dated correction note (yellow-tape: what it claimed, how we now know otherwise). Live state contradicts the ruling → stop, report, nothing proceeds on Tier 3 or 4.5/4.6 until the contradiction is resolved.

Follow-on (not this brief): on a confirmed item 0, the state-hygiene job — state rm (never destroy) of the stale entries, then the .tf files removed as one reviewed diff — files as its own short brief. Nothing in infra/ucca-infra/ is touched by this brief regardless.

All items 4.1–4.6 may execute on filing (4.5/4.6 sequenced after item 0 confirms); 4.7 remains deliberately deferred per its own section.

3. The stale-binding facts (context, from the recon)

The DBs rtopacks-db, rto-nrt-db, abs-db migrated to the RTOpacks account on 2026-04-08 (MIGRATE-02). Any UCCA-side worker still binding them is binding a database that is no longer in this account — the bindings are presumed broken, but presumed is not verified (rule 1).

4. Work orders

4.1 surfaces/ucca-surfaces/apps/ops-v2/wrangler.jsonc — rtopacks-db binding

  • Verify: does ops-v2 code actually call this binding? Grep call sites, not just config.
  • If no live call sites → RETIRE the binding (edit wrangler, redeploy ops-v2).
  • If call sites exist → report them; they are either dead code (retire both) or a genuine dependency that should have died at untangle (escalate, do not repoint silently).

4.2 workers/stats-cache — stale binding

4.3 workers/qual-enrichment — stale binding

4.4 workers/backup — stale binding

4.4a workers/cricos-sync — stale binding

For each (same procedure): - Verify which of rtopacks-db / rto-nrt-db / abs-db it binds (recon lists the set, not the per-worker mapping — establish it). - Verify whether the worker does any remaining UCCA work: - UCCA work remains → REPOINT or strip the stale binding; redeploy. - No UCCA work (worker existed for the client) → RETIRE the worker entirely: capture final config, remove from deploy surface, delete the deployed worker. - Note: names like cricos-sync and qual-enrichment are VET-domain-shaped. If a worker turns out to be doing engine work under a VET name, that is an ADR-0002 drift finding — report it, don't just rename it.

4.5 workers/rtopacks-proxy — ungated (sequenced after item 0 confirms)

4.6 workers/rtopacks-docs-proxy — ungated (sequenced after item 0 confirms)

  • With UCCA no longer operating the client's domain (§2), the presumption flips to RETIRE — but presumption is not verdict. Audit first: what each proxies, whether traffic still flows (tail/analytics), and what breaks if it stops.
  • Live traffic found → stop and report before retiring (something still routes through UCCA that the ruling says shouldn't — that is a finding, possibly a fence item, not a silent keep).
  • No traffic, nothing breaks → RETIRE per rule 5.

4.7 ops-v2 RTOpacks world code — audit now, verdict deferred

Paths: apps/ops-v2/lib/worlds/rtopacks · app/api/worlds/rtopacks · app/w/catalog/**/rtopacks* - The recon flags this may be by design (L2 ops manages worlds; four-layer plane). It is also downstream of Tier 2: when the build brief's Step 5 severs engine/.../worlds/, this surface code either becomes dead or becomes the client-side face of the adapter pattern. - This brief's scope: audit and report only. What does the world code do today, is any of it reachable, what does it import from Tier-2 paths (those imports are the severance coupling Step 5 needs to know about anyway). - The keep-or-cut verdict is taken with or after Tier-2 severance, not here. Cutting it first risks cutting the pattern the adapter needs; cutting it blind risks the same mistake as a naive worlds/ rm, one layer up.

5. Completion report (what closes this brief)

One report, filed to ground/, containing: - Item 0's zone + state findings, and confirmation the recon's Tier-3 correction note was applied (or the stop-report if live state contradicted the ruling). - Per-item: live-state verification, verdict, "how we know," action taken, redeploy confirmation (or audit findings for 4.7). - The per-worker DB-binding map established in 4.2–4.4a. - Final configs of anything retired. - Divergences from the recon, if any. - Confirmation the Infrastructure-State snapshot and referencing docs were updated (Full Cycle), with the snapshot's new date. - Anything surfaced that belongs to Tier 2, Tier 3, or the docs sweep — reported, untouched.

On filing of the completion report: the recon's Tier-4 section is marked executed (dated pointer to the report), and this brief flips DRAFT → EXECUTED.

6. What this brief must not do

  • Touch engine/ucca-engine/worlds/, tga_data/, tga_pdfs/ (Tier 2 — build brief).
  • Touch anything in infra/ucca-infra/ (Tier-3 state hygiene — its own follow-on brief, only after item 0 confirms).
  • Delete or edit any of the 170 rtopacks-referencing docs (CANON-CULL's sweep).
  • Batch-redeploy, blanket-rm, or act on a binding without verifying its call sites.
  • Touch account f95d4537 in any way.

Execution brief. Tier 4 only: verify, verdict, apply, redeploy, Full Cycle — one item at a time, dangerous edges fenced per the recon. The Tier-3 gate resolved (RTOpacks self-manages its domain) — item 0 grounds that in bytes first; one item waits on Tier-2 severance; everything else moves now.