All runbooks
runbookuai-explorerredacted view

Operator Decision Brief

Synced UAI Explorer runbook documentation from docs/runbooks/operator-decision-brief.md.

Updated 2026-06-21·Freshness: Reference·Sensitive tokens or credentials were hidden before display.

Operator Decision Brief

Created: 2026-06-20
Updated: 2026-06-21

Status: superseded for public-safe v1. This brief is retained as historical decision lineage. Current generated state is: [REDACTED:high-entropy].md.

Purpose

Record how the pre-cutover operator decisions closed and define which future items belong to separate workstreams.

This brief is not an approval for external exposure, storage cleanup, raw content publication, node onboarding, or catalog import apply.

Current Result

  • Production CT 121 runs UAI Explorer 0.2.3 in public-safe mode.
  • Sandbox CT 126 remains the staging and verification lane on 0.2.3.
  • Production backup and rollback evidence are recorded in [REDACTED:high-entropy].md.
  • No DNS, TLS, firewall, reverse proxy, NetBird, cluster membership, or public-route changes were made.
  • No open UAI Explorer decisions remain for public-safe v1.

Closed Decisions

Production Cutover

Decision: approved and executed for internal production CT 121.

Evidence:

  • [REDACTED:high-entropy].md
  • [REDACTED:high-entropy].md

Future external exposure is a separate runbook and must include DNS, TLS, firewall, reverse proxy, route, rollback, and smoke-test evidence.

Zenbook Documentation Survey

Decision: closed for UAI Explorer documentation-survey scope.

Zenbook metadata survey and sanitized export exist. If Zenbook later becomes a lab node, handle that as separate infrastructure onboarding rather than a UAI Explorer blocker.

Dormant/Future Proxmox Node

Decision: closed for public-safe v1.

Future node work belongs to infrastructure onboarding. Before cluster join, disk reuse, or cleanup, identify hostname/IP, run a metadata-only documentation survey, generate a sanitized export, and record separate evidence.

Proxmox Storage Policy

Decision: backup-only cutover authority was used. No snapshot deletion, backup pruning, migration, or cleanup was performed.

Future storage maintenance must use:

  • [REDACTED:high-entropy].md
  • [REDACTED:high-entropy].md

Real Content Promotion

Decision: closed for public-safe v1 with no raw survey promotion. Production uses the curated CT 126 catalog data promoted during cutover.

Future promotion sequence:

  1. Select raw candidates explicitly in the private lane.
  2. Run tools/redact_selected_artifacts.py.
  3. Review generated artifacts.
  4. Assign tags, freshness, source lineage, and audience.
  5. Run tools/prepare_catalog_import.py with a private approval file.
  6. Run tools/stage_approved_catalog.py into a catalog data root.
  7. Dry-run tools/import_staged_catalog.py.
  8. Import only approved sanitized output with explicit --apply authority.

Future Workstreams

  • External public exposure.
  • Additional users, roles, tag grants, and onboarding UX.
  • Real-content promotion from MacBook, Devine, Cadence, and other standards material.
  • Private operator metadata and embedding lanes.
  • Proxmox storage maintenance.
  • Zenbook or dormant-device infrastructure onboarding.
  • Further UX polish and documentation taxonomy refinement.

Keep these as separate runbook-driven sessions. Do not mix production runtime changes, public exposure, storage cleanup, raw content promotion, and node onboarding in one implicit approval.