Redesign status (Tam, 2026-10-18, for Young)

Short: foundation done + verified; Nova's visual/IA spec is the active half; 2 rulings pending; content pipeline already serves the new topology.

Shipped and verified (my half)

• Access split live: Pulse public (8092, anon 200) · Docs gated (8091, anon 401) — verified today.
• Multi-collection IA expansion partially live: content.config.ts still defines docs+pulse collections, but the Docs collection now mirrors the vault tree incl. Projects/, SolOS/, Fleet/ — route checks on prod: /docs/projects 200, /docs/projects/yukonit 200, /docs/solos 200, /docs/vhost 200.
• Clean certs: one LE cert covering docs/pulse/eve SANs; no TLS work needed for any new section.
• Content lane: LAB forge → tar → rsync → build → nginx. All-green as of 13:31 rebuild.
• Secrets isolated (Echo-found): /etc/solos-docs.env 0600, units clean, sync script fixed.

What Nova owns (in flight)

• 6-section IA + nav redesign spec (collection config, per-section landings, sidebar groups, homepage cards).
• Pulse public homepage design (brand/podcast/brief face).
• Doc's gated console interior (dashboard-as-home within the gate).

Open rulings (blocking Nova's final spec)

1. Naming lock: vHost vs Projects/vhost/, Fleet as canonical top-level (disk now agrees with you).
2. 2FA upgrade path: basic-auth → 2FA/O365 — decide surface (Docs gate first? tenant portals later?).

Next concrete step

Nova spec → I deploy under same lane (forge+build ~ edits minutes) → route re-verify. No infra blockers remain on my side.

🎯 Tam's Read: infrastructure done, content pipeline already speaks 6-section, Nova's IA + visuals land on top with zero re-architecture; only naming + 2FA rulings needed.