---

title: Registries-Pivot — UI Review Log date: 2026-05-31

Registries-Pivot — UI Review Log

date	event	surface	status	by
2026-05-31	v1 static preview deployed	/ui-preview/registries-pivot/v1/	deployed · pending_user_review	claude-code
2026-05-31	v2 connected preview deployed (live read snapshot, 11 sections, COMMIT_FORBIDDEN banner)	/ui-preview/registries-pivot/v2/	deployed · pending_user_review	claude-code (Macro 2+3)
2026-05-31	Access verification + fix pass — user reported "cannot access"; verified preview is LIVE and healthy, NOT broken; root cause = URL confusion (production route ≠ preview)	/ui-preview/registries-pivot/v2/	VERIFIED ACCESSIBLE · no fix needed	claude-code (access-verify macro)

v2 notes

• HTTP 200 (index.html 22,531 B + data.json 12,100 B); zero DB/Nuxt/Directus mutation; rollback = rm -rf …/v2/.
• Approval state at deploy: COMMIT_FORBIDDEN_NO_APPROVAL — all six views / pivot bundle / parent_code / display_policy / registry_pin are REHEARSED ONLY, not committed; banners say so.
• Pins shown are rehearsal pilots (not persisted).

Access verification (2026-05-31)

Preview URL — the one the user should open: https://vps.incomexsaigoncorp.vn/ui-preview/registries-pivot/v2/

check	result
…/v2/	HTTP 200, text/html, 22,531 B — OK
…/v2/index.html	HTTP 200, text/html, 22,531 B — OK
…/v2/data.json	HTTP 200, application/json, 12,100 B — valid JSON, 13 top-level keys (meta, root_summary, count_integrity, drift_rows, missing_pivots, drilldown_example, label_grouping, pins, orphan_phantom, substrate_examples, api_endpoints, legacy_violations, good_pattern) — OK
…/v2 (no trailing slash)	HTTP 301 → …/v2/ (normal nginx dir redirect; browsers follow automatically) — OK
…/v1/	HTTP 200, 11,337 B — OK (untouched)
TLS cert	valid — Let's Encrypt E7, CN=vps.incomexsaigoncorp.vn, valid 2026-05-01 → 2026-07-30, ssl_verify_result:0. No browser security block.
Self-containment	Fully self-contained — inline <style> + inline <script>; only external asset is ./data.json (relative). No localhost, no absolute paths, no production /api/ dependency.
Fetch logic	fetch('./data.json').then(...).catch(()=>render(INLINE)) — hard inline fallback: page renders correctly even if data.json fails.
Site health	/ (homepage) HTTP 200, 256,361 B — production app untouched.

Verdict: preview v2 is LIVE, healthy, and was never broken. No static fix was required.

Production route status

Route: https://vps.incomexsaigoncorp.vn/knowledge/registries-pivot

• Returns HTTP 200, ~1.75 MB, title Knowledge Document - Incomex AI Portal.
• Classification: CATCH-ALL /knowledge/[…slug] generic knowledge-document renderer, NOT a dedicated interactive Registries-Pivot surface.
  • Proof: a nonexistent slug (/knowledge/this-route-does-not-exist-xyz123) ALSO returns 200 with the same shell (soft-404 inside the SPA).
  • The real slug resolves a stored KB document (knowledge-registries-pivot data key present; pivot/integrity terms in payload), so it shows a document, not the OS-agency pivot UI.
• The interactive Registries-Pivot surface is NOT implemented in production Nuxt. No production route implementation was done in this pass (forbidden).

User-facing note

To view the Registries-Pivot information now, open the preview: https://vps.incomexsaigoncorp.vn/ui-preview/registries-pivot/v2/ (include the trailing slash). The production address /knowledge/registries-pivot currently shows only a generic knowledge document, not the interactive pivot surface — that surface awaits a future macro (RG7/RG8: API endpoints + Nuxt shell), which itself is gated on RG1+RG2 approval to commit the view layer.

Open review questions for the user

1. Approve RG1+RG2 (six-object foundation) to commit the view layer? (unlocks everything)
2. Approve RG5/RG6 (display_policy / registry_pin) tables?
3. Convene council on RG4 phantom law (source_model-aware definition)?
4. Confirm canonical route /knowledge/registries-pivot and convergence of /knowledge/registries?

No approvals recorded

No self-approval. No human/council sign-off exists for any Registries-Pivot scope (only S178 DOT-repair approvals exist, out of scope).