KB-480A

T2 UI-Current / Autoscale-Generator / Deploy-Risk Audit — 00 README First

4 min read Revision 1
terminal2auditread-onlyui-currentautoscale-generatordeploy-riskregression2026-06-05

00 · README First — T2 UI-Current / Autoscale-Generator / Deploy-Risk Audit

Date: 2026-06-05 · Mode: READ-ONLY (Terminal 2 Auditor) · DB: directus.public (RP lives here, NOT incomex). Final status: PARTIAL — T1's newest checkpoint (checkpoint-rp-count-substrate-fix-registryization-generator-fullpop-v2-2026-06-05.md) is absent in KB and on diskAWAITING_T1_FINAL. The audit still advances and the next UI macro is writable without rediscovery. Mutations: NONE except this KB doc set (7 report docs + 1 checkpoint). No DB / FS / UI / Git / approvals / owners / events / REAL_RUN / IU / KB-source mutation.

Purpose

Run in parallel with T1 (RP_COUNT_SUBSTRATE_FIX_REGISTRYIZATION_GENERATOR_FULLPOP_V2). Find anything that could make the next UI productionization macro — RP_UI_CURRENT_PRODUCTIONIZATION_WITH_RELIABILITY_BADGES_AND_SMOKE — fail, or accidentally bind the UI to a stale/hardcoded surface.

What is new since the prior two T2 design audits

T1 has since executed most of the prior P0 design (the _current aliases, registry-driven binding view, full-population invariant, computed proof matrix, no-hardcode scorecard now all exist live). This audit therefore shifts from "does the design exist" to "is the executed surface safe to bind a production UI to, and does the generator actually auto-scale."

Read path (reliable — not BLOCKED)

  • Local memory project files (T1 closeout summaries, rich).
  • Incomex_KB: prior T2 design docs (items 4 & 5) + T1 closeout report dirs (read-only).
  • query_pg RO on directus (READ ONLY txn, 5s, LIMIT 500) — live view verification.
  • read_file (allowlist /opt/incomex/docs, /opt/incomex/dot/specs, /var/log/nginx) for UI package docs.
  • UI source (/opt/incomex/docker/nuxt-repo/web) is outside the allowlistUNVERIFIED_SOURCE_ACCESS; UI internals are audited from package docs only.

Headline verdicts

Dimension Verdict
UI current binding NOT_READY (P0)_current exists & is reliability-rich, but no UI package binds it, and the bound surface omits the invariant FAIL signal (false-green).
Generator / auto-scale PARTIAL — NEEDS_REGISTRYIZATION — binding metadata externalized, UNION bounded not killed; 58/87 nodes still requires_view_edit; _current does not resolve through the registry-driven view.
Deploy risk HIGH — no _current UI package, no deploy-guard view, divergent git (ahead17/behind13), no push creds; operator-only.
Regression risk MANAGEABLE IF GUARDED — regression tests are well-defined, but no guard view wires them; 2 real invariant FAILs are live.

Live no-fake state (unchanged, confirmed read-only)

official AX-PROCESS RP 0; president votes 0; governance_object_ownership 0; real_run_enabled false; axis_registry 2 (AX-PROCESS/AX-TOPIC CANDIDATE); trigger_guard_alerts 129. No drift.

Doc map

01 UI-current binding risk · 02 Generator / auto-scale risk · 03 Deploy risk · 04 Regression-test risk · 05 Next UI-productionization checklist · 06 Final summary. Checkpoint at architecture root.

Severity legend

P0 blocks UI productionization · P1 should fix before deploy · P2 label and continue · P3 authority/operator only.

Back to Knowledge Hub knowledge/dev/reports/architecture/parallel-terminal2-ui-current-autoscale-generator-deploy-risk-audit-2026-06-05/00-readme-first.md