Skip to content

Retirement unit §A — amendment 2

What this is. The control-panel recon (REPORT-01) surfaced one live-infra-loss risk and two new residue items in the §A list. Tim ruled on the proxies in session. This amendment lands those corrections in the brief before the C-6 answer arrives, so nothing executes against a stale or ambiguous list. Paper only — the gate does not move.

1. Ruling recorded (Tim, 2026-07-03)

UCCA's own docs-proxy and knowledge-proxy stay. They are live UCCA infrastructure — they serve docs.ucca.online and knowledge.ucca.online, historically driven as the project's MkDocs-based knowledge/memory surface (used by GPT and a prior Claude session). They are not RTOpacks residue and are permanently out of retirement scope.

2. Changes to §A (apply each; cite this amendment in the brief)

  1. Disambiguate the proxies (the guardrail). Replace the bare "docs-proxy" entry with the explicit RTOpacks names: rtopacks-docs-proxy and rtopacks-proxy (both not deployed, per REPORT-01 Unit D). Add a NEVER-RETIRE note alongside: UCCA's docs-proxy and knowledge-proxy are live infra, out of scope per §1 above. The execution pass must match on the exact RTOpacks worker names, never on a substring.
  2. Add new residue: the rtopacks-docs Pages project (found in recon, absent from the original §A list). Same treatment as the rest of §A — retire on execution.
  3. Note, no action: ucca-backup-large Worker — deployed but SUSPENDED since 2026-04-09 (UCCA-CLEANUP-01; cron disabled, no databases in scope). Harmless; NOT added to §A (it is UCCA-named infra and its disposition belongs to a UCCA-side housekeeping pass, not the RTOpacks retirement). Record its existence in the brief's notes so the execution window doesn't rediscover it.
  4. Corroboration line (paper trail only): REPORT-01's ucca-backup-large finding corroborates the forensic position of the premise correction — the cross-account export pattern was removed 2026-04-09, consistent with "the DBs left at the 2026-04-08 migration, no later deletion." Add one line to the brief's forensic-context note citing the report. Nothing crosses the fence; the correction already carried this position.
  5. Worlds rider (context, no new scope): the world UI/API lives inside ops-v2 (app/w/catalog/worlds/, lib/worlds/rtopacks/) and dies with the already-ruled ops-v2 cut — no separate §A entry needed. The engine-repo fossil directories (worlds/usa_for_later/, the mis-filed moodle/ connector) are OUT of this brief's scope: yellow-tape + fossil-ledger candidates for a future CANON-CULL / cleanup lane, never touched by the retirement pass.

3. What does not change

  • The gate. Execution of §A waits on RTOpacks' C-6 answer, filed digest-verified in canon/received/. This amendment moves no gate.
  • ucca-backup stays OFF the list (live UCCA infra — unchanged from amendment 1).
  • The trust.rtopacks.com.au item stays coordinate-with-client, never unilateral.

4. Deliverable

Amend UCCA-RETIREMENT-UNIT-BRIEF-01 §A in place per §2 (the brief carries an amendment log; append this doc_id and date). File this amendment to ground/, update the register, report HEADs. No infrastructure command of any kind is authorised by this document.

Amendment. One ruling recorded (UCCA's own proxies live forever outside retirement scope), one guardrail hardened (exact RTOpacks names, never substring match), one residue added, one suspended Worker noted, one corroboration line for the paper trail. The C-6 gate stands exactly where it stood.