# Egan v2 — Project Context --- ## Project **Project:** Egan v2 design exploration **Site:** egan.rizlabs.com (live v1) **Preview:** https://ux.rizlabs.com/projects/egan/ **What we're doing:** Design consultation. Wireframe a next-version UI to address gaps in the current frontend — visual register, IA coherence, and the under-utilized graph spine. **Role:** UX / design consultation (exploratory, just for Greg right now) **Project overview:** Egan is an enterprise knowledge graph + intelligence platform — the "Universal Baseline Authority" in the Rizlabs hero stack. PostgreSQL + Apache AGE (graph) + pgvector (semantic) feeding two consumer surfaces: veta (financial + metrics modeling — formerly Quanta, see ADR-016) and tomo (foundry substrate — formerly Piggie, see ADR-016). Positioned as a sovereign open-source alternative to Palantir. **Primary user assumed:** veta value-engineer (100% of validated usage). The wireframes prioritize their workflows; secondary users (direct Egan analysts, internal operators) are accommodated but not centered. **Current frontend status (v1):** Next.js 16 + React 19 + Tailwind v4 + custom CSS-var token system, teal/slate palette, dark-mode-first, ~65 components across 30+ routes. Functionally complete but reads as generic SaaS dashboard rather than gravitas knowledge tool. Radix UI + brand-token migration already on backlog (R1 #20). Graph visualization is the differentiator but presented as one feature among many. --- ## Navigation structure **No eyebrow / no top nav.** Egan is an authenticated tool, not a marketing site. The page shell is **left sidebar + main content**, not the kit-wireframe.html marketing scaffold. **Sidebar — 5 sections, intent-oriented:** - ◆ **Brief** — home; what changed, what to act on today - ◇ **Accounts** — target accounts, account intelligence, discovery, sales plans, solutions - ◇ **Knowledge** — Graph Explorer (anchor), Taxonomy, Compliance, Ontologies, Entities - ◇ **Analyze** — Notebook, Reports, Benchmarks, Assistant, Query - ◇ **Operate** — Pipelines, Import, Quality, Admin, Settings Sidebar footer: user identity / portal switcher / build id (matches v1 pattern). **Mobile:** Sidebar collapses to a top app bar with a section drawer. Same 5 sections, same hierarchy. --- ## Pages in scope | Page | Description | Status | |---|---|---| | Brief | Home / today view — replaces the v1 stats dashboard. Identity-defining page. | In Progress | | Graph Explorer | The spine. Reorganized so the graph anchors the Knowledge section instead of being one feature. | Planned | | Account Intelligence | Account `[id]` view. The primary veta workflow — the "money page." | Planned | | Compliance Browser | Reference-data browsing pattern. Frameworks → controls → gaps. | Planned | | Sales Plan | Workflow / document pattern. Building something inside Egan, not just browsing. | Planned | --- ## Wireframe / layout / design constraints - **Mood: Foundry-coded.** Institutional, analytical, panel-disciplined. Sits between "generic SaaS" (current) and "Bloomberg terminal" (too hostile). Match the "sovereign Palantir alternative" pitch without literal Palantir cosplay. - **Tokens only.** No hex / rgb / rgba in page CSS. All colors via `var(--*)` from `wireframe.css`. Wireframe stays mono — the Foundry mood is expressed through *structure, panel discipline, type hierarchy, and information density* — not color. - **Sidebar shell, not marketing shell.** `kit-wireframe.html`'s eyebrow+mainnav doesn't apply. Adapt the `.page` / `.doc-head` / `.review-layout` containers, build sidebar+main inside `.wf`. - **Information density.** Lean toward more, not less, on screen. Foundry tools assume users want signal, not whitespace meditation. - **Mobile is real.** Build it properly per kit rules — not a stub. --- ## Key decisions made - **5-section IA** (Brief / Accounts / Knowledge / Analyze / Operate). Locked. - **Brief replaces the stats dashboard** as the home page. The v1 page (10,000 nodes! 50,000 edges!) is a database admin panel, not a tool — replacing it is the single biggest mood-shift the v2 makes. - **Graph Explorer becomes the anchor of Knowledge**, not a parallel feature alongside Taxonomy / Compliance. - **Operate (admin) demotes** but doesn't hide — it's its own section, not interleaved with user workflows. - **Wireframes live in the kit, not in egan/web.** They're a separate artifact translated to real code after approval. - **Foundry-coded design direction.** Picked over Bloomberg / Linear-coded / Editorial alternatives. --- ## Open questions - **Primary user commitment.** Provisionally veta-consumer. If wireframes should explicitly design for the seam between value-engineer and direct analyst, flag that and we'll add a hand-off pattern. - **Brief commitment level.** Provisionally "commit to a real Brief" (not hybrid with stats). If we should hedge with stats below the fold, adjust before the wireframe is approved. - **4th anchor page expansion.** Both Compliance and Sales Plan are in scope (committed to 5 pages total). Sequence is open — building Brief first as the tone-setter. - **Brand color application.** Wireframes are mono. When we translate to real code, decide: keep v1 teal/slate, retire it for something more institutional, or layer a Foundry mood on top of teal. --- ## Feedback log **2026-05-23 — Consultation kickoff** - Direction: Foundry-coded (not Bloomberg, not Linear). - IA: 5 sections agreed. - IA scope: "Have an opinion on IA" (not just restyle). - 5 anchor pages committed. - Audience: just Greg, exploratory. - Preview infrastructure set up: ux.rizlabs.com, ip-restricted, TLS, ansible-managed vhost on droplet.