# veta — Project Context > **Naming history (per ADR-016, 2026-05-23):** this product was named **Quanta** through 2026-05-22. It was renamed **veta** when the new umbrella product `quanta` (opportunity portfolio) took the parent slot. The kit project folder was renamed from `projects/quanta/` to `projects/veta/` on 2026-05-26. *Site / repo / code-import propagation is sequenced in ADR-016 phases A–H and is partial as of this writing.* --- ## Project **Project:** veta — financial + metrics modeling tool (design exploration) **Site:** veta.rizlabs.com (forward canonical; legacy quanta.rizlabs.com may still serve) **Preview:** https://ux.rizlabs.com/projects/veta/ **What we're doing:** Design consultation. Same Foundry-coded direction as Egan v2. **Role:** UX / design consultation, exploratory **Project overview:** **veta** is the **financial + metrics modeling tool** in the Rizlabs stack. It is the layer that turns business hypotheses into modeled economics: - **Scenario planning** — As-Is / To-Be / multi-future modeling - **Current-state cost transparency** — multi-dimensional cost allocation (GL → Pool → Tower → App → BU), TBM-aligned - **ROI projections** — NPV / IRR / payback at notional-first-pass *and* detailed levels (the level of rigor is matched to risk + complexity, not applied uniformly) - **Value realization** — verifies projections post-deployment; modeled → measured tracking - **Investment rationalization** — translates capability bets into financial frames the CFO can defend Replaces error-prone Google-Sheets-based IT cost modeling with a purpose-built web app. Primary users: IT finance analysts, IT directors, CFOs, FinOps engineers — and the engagement leads who need to land a financial story alongside a capability story. **Primary user (this consultation):** Greg's IT finance analyst — the same archetype who is the primary Egan v2 user, since the value-engineering workflow flows Egan → veta. Their day involves grid editing, scenario comparison, and producing decision-ready briefs. **Relationship to quanta (umbrella):** veta is one of three engines that the new top-level **quanta** (opportunity portfolio) product consumes. quanta surfaces *which* hypotheses to test; veta models *what they cost and what they return*. veta is the financial layer beneath quanta's portfolio view. **Relationship to Egan:** veta consumes Egan's `/api/v1/*` graph endpoints for value streams, taxonomy, and process models. One-way flow: veta ← Egan. The Knowledge / Value Streams pages in veta surface Egan content. The two products should *feel related but distinct* — same design system idioms, different palette emphasis (veta is more financial/grid-heavy; Egan is more analytical/graph-heavy). **Current state (v1):** Next 15 + React 19 + TanStack Query + Zustand + AG Grid Enterprise + Recharts + Tailwind + custom @brand/tokens + (legacy-named) `@quanta/ui` package. 18 pages, 13-item flat sidebar, teal/slate palette (same family as Egan v1). Scenario selector buried at sidebar bottom. Dashboard is a stats page. *Legacy `@quanta/*` package names persist until ADR-016 phase C propagates.* --- ## Navigation structure **No eyebrow / no top nav.** Authenticated tool, sidebar shell (same as Egan v2). **Sidebar — 5 sections, intent-organized (collapses v1's 13-item flat list):** - ◆ **Brief** — home; scenarios in flight, open VE work, what changed - ◇ **Model** — workspace context: models list/switcher, scenarios, Key Data Inputs, settings - ◇ **Cost** — Current State TCO, Future State TCO, Comparison, Cost Elements, Reference Data - ◇ **Value** — Value Streams (Egan-fed), VE Portfolio, Implementation Plan, ROI Analysis, Value Realization - ◇ **Share** — Export center, Reports, Briefs / presentations Sidebar header carries the **active model + scenario** as primary context, not buried at the bottom. --- ## Pages in scope | Page | Description | Status | |---|---|---| | Brief | Home — replaces v1 stats dashboard. Identity-defining page. | Planned | | Cost Grid | Current State TCO grid — AG-Grid-styled but Foundry-coded. Daily-driver. | Planned | | ROI Analysis | Panel-driven financial view, NPV/IRR/payback, dark-canvas charts. Notional + detailed modes. | Planned | | Value Streams | Egan-integrated page. Proves the two products feel related but distinct. | Planned | --- ## Wireframe / layout / design constraints - **Mood: Foundry-coded** — institutional, panel-disciplined, analytical. - **Tokens only** — no hex/rgb in page CSS. Wireframes stay mono. - **Sidebar shell** with active model + scenario in the header. - **Density on the high side**. - **Grids must read as grids** — daily-driver is a spreadsheet, lean in. - **Charts use the dark-canvas pattern** from Egan. - **Notional vs. detailed levels of rigor** are first-class UI states, not a hidden mode — the analyst should always know which level of rigor they're operating at. --- ## Key decisions made - 5-section IA: Brief / Model / Cost / Value / Share. - Brief replaces stats dashboard. - Active model + scenario in sidebar header. - Foundry-coded direction. - Pattern reuse from Egan kit. - **2026-05-26:** Renamed from Quanta → veta per ADR-016. New top-level product `quanta` (opportunity portfolio) now sits one layer above veta. --- ## Open questions - Multi-model navigation: dropdown vs ⌘K palette. Provisionally both. - Brand color differentiation from Egan: same family for v1; eventually deeper/different. - Grid library: AG-Grid stays for wireframe purposes. - Value Realization page shape — separate from ROI Analysis, or a tab inside it? (Decision deferred to Phase 2 of the showcase work.) --- ## Feedback log **2026-05-23 — Consultation kickoff** - Foundry-coded direction. 5 sections agreed. 4 anchor wireframes. **2026-05-26 — Rename to veta** - ADR-016 product naming canon: financial-modeling tool = veta; opportunity portfolio = new quanta. - Kit project folder renamed `projects/quanta/` → `projects/veta/`. - In-wireframe product labels updated (Quanta → veta). - Legacy `quanta.rizlabs.com` / `@quanta/ui` artifacts persist pending ADR-016 propagation.