Root-level screens (the access layer)

File	What it is	What it is not
`login.html`	The single generic entry (default `/`). Username routes to a workbench; any password works.	Not a per-persona login; not real auth. The old per-persona logins are off-path.
`config-workbench.html`	Admin hub — two tiles: Admin → `admin/platform-configuration.html`, Business Admin → `business-admin/doa-config.html`.	Not itself a config screen; just a router hub.
`approver-workbench.html`	DoA Approver hub — tile → `doa-approver/home.html`.	Single-tile hub; no data.
`requestor-workbench.html`	Requestor hub — tile → `requestor/home.html`.	Single-tile hub; no data.
`executive-workbench.html`	Analytics hub — three tiles: APEX Committee · BU Executive · General 360.	Not analytics itself; a router.
`entity-selector.html` · `plant-function-selector.html`	The designed 4-step scope drill-down (A2/A3). Still clickable.	Not in the default route — workbench tiles jump straight to home.
`doa-login.html` · `requestor-login.html` · `business-admin-login.html`	Legacy per-persona logins.	Off-path — superseded by `login.html`. Reference only.
`agent-flow.html`	The shared 21-agent D3 engine every `*-agent.html` shim redirects into.	Not persona-specific — parameterised by `#persona/track/stage/batch`.
`master_design.html`	Design-system reference screen.	Read-only; not part of any flow.

Requestor (`requestor/`) — view-only dashboards

What this folder is: the Requestor's watch-only window on the full OPEX + CAPEX pipeline for their plant. What it is not: it has no validation queue and no agent screens — the Requestor cannot submit, approve, consolidate, or action anything.

File	Screen ID	What it is
`home.html`	R0-HOME	Landing — scope, recent activity, where-to-next
`opex-prr-dashboard.html`	RQ-PRR-DASH	Submitted PRRs (status, stage, budget consumption)
`opex-pr-dashboard.html`	RQ-PR-DASH	Raised PRs (consolidation, DoA routing)
`opex-po-dashboard.html`	RQ-PO-DASH	Issued POs (vendor, delivery milestones)
`capex-pr-dashboard.html`	RQ-CPX-PR	CAPEX Raised PRs (CER compliance, Year-2 budget)
`capex-po-dashboard.html`	RQ-CPX-PO	CAPEX Issued POs (vendor, payment terms)
`*-line-detail.html` (5 files)	RQ-*-LINE	Row-click drilldown — approval-stage tracker, documents (+upload), comment thread. `#id=<record>-<line>`

Persona: Priya Nair (PN) · Requestor · HZL.

DoA Approver (`doa-approver/`) — the full working pipeline

What this folder is: the only persona with the complete Dashboard → Validation → Agent → decision loop, across OPEX (PRR·PR·PO) and CAPEX (PR·PO). What it is not: it does no configuration and cannot create the original PRR.

Access: home.html (A4) · notifications.html (A7 inbox — returned PRRs, pending approvals).

OPEX track:

Stage	Dashboard	Validation	Agent (shim → `agent-flow.html`)
PRR	`opex-prr-dashboard.html` (+ `opex-prr-detail.html`)	`opex-prr-validation.html`	`opex-prr-agent.html` (17/21, PASS)
PR	`opex-pr-dashboard.html`	`opex-pr-validation.html`	`opex-pr-agent.html` (18/21, PASS)
PO	`opex-po-dashboard.html`	`opex-po-validation.html`	`opex-po-agent.html` (19/21, PASS)

CAPEX track (no PRR):

Stage	Dashboard	Validation	Agent
PR	`capex-pr-dashboard.html`	`capex-pr-validation.html`	`capex-pr-agent.html` (18/21, PASS WITH NOTES)
PO	`capex-po-dashboard.html`	`capex-po-validation.html`	`capex-po-agent.html` (19/21, PASS)

The 5 *-agent.html files are ~400-byte redirect shims — they carry no header/sidebar and forward to ../agent-flow.html. Persona: Rajiv Mehta / Anita (RM/AR).

Admin (`admin/`) — system configuration (Module H)

What this folder is: the Admin's system setup — entities, users, access, workflow, audit — plus a read-through mirror of the whole OPEX/CAPEX pipeline. What it is not: the Admin never approves transactions; the pipeline mirror is for visibility only.

File	Screen	What it is
`platform-configuration.html`	H1	Config hub / landing
`entity-mapping.html`	H2	Entity → Plant → Function map (via Platform Config, not sidebar)
`user-access-and-security.html`	H3+H4	Users tab + Access Matrix tab
`doa-matrix.html`	H5	DoA value-limit matrix (structural; direct link only)
`policy-engine.html`	H6	Read-only policy library (direct link only)
`workflow-routing.html`	H7	Routing / escalation / parallel lanes (via Platform Config)
`audit-logs.html`	H8	Immutable event trail
`work-in-progress.html`	—	WIP placeholder for System/Data/Report Governance
`opex-` / `capex-` (16 files)	—	Read-through pipeline mirror (shims into `agent-flow.html#persona=admin`)

Sidebar shows only Governance & Setup. Persona: Anita Rao (AR) · Admin · HZL.

Business Admin (`business-admin/`) — business-rule governance

What this folder is: the business perspective — DoA values, policy uploads, and the parameters that drive the agentic layer. What it is not: not system setup (no entity/user/RBAC/audit), and no approvals.

File	Screen	What it is
`doa-config.html`	BA-1	Editable DoA matrix — flip Y/– cells, Submit for Ratification
`policy-engine.html`	BA-2	Policy library + upload, with Doc Type (Policy · Rule · Guideline)
`parameterization.html`	BA-3	Rules · conditions · calculations as expressions
`operational-norms.html`	BA-4	Cycle/lead/compliance benchmarks — Target vs Current, RAG status
`thresholds.html`	BA-5	Value bands, tolerance limits, routing gates — Blocking/Advisory

Sidebar shows only the Business Admin group (5 items). Persona: Vikram Shah (VS) · Business Admin · HZL.

Analytical Reports (`analytics/`) — read-only dashboards

What this folder is: read-only executive & governance analytics across three audience views. What it is not: no create/approve/validate/config, and no links into the other persona folders. Built with Chart.js.

General 360 (whole-profile, scope "Vedanta Group"):

File	What it is
`general-home.html`	7 dashboard sections / 45 KPIs & charts (Exec Summary · Budget vs Actual · Category · Department · PRR→PO Lifecycle · Real-Time · Compliance)
`kpi-*.html` (6 files)	Individual KPI deep-dive screens feeding the above
`dashboards.html`	Dashboards index

APEX Committee (group-wide, "Vedanta Group"):

File	What it is
`apex-home.html`	Overview — KPI strip, OPEX-vs-CAPEX trend, where-to-next
`apex-group-spend.html`	Monthly line + spend-by-BU stacked bar + category doughnut + BU register
`apex-capex-portfolio.html`	PRG ladder strip + sanctioned-vs-committed bar + top projects
`apex-exceptions.html`	Exceptions by type (open vs closed) + RAG exception register

BU Executive (single BU — HZL, "Hindustan Zinc Limited"):

File	What it is
`bu-home.html`	Overview — BU KPI strip, spend trend, where-to-next
`bu-spend.html`	Monthly line + spend-by-plant + OPEX/CAPEX doughnut + plant register
`bu-plant-drilldown.html`	Interactive plant chips (`pick(key)`) → spend-by-function bar + cost-centre table
`bu-pipeline-health.html`	Stage funnel (PRR→PR→PO→Closed) + cycle-time bar + ageing records (RAG)

Persona: G. Ramesh (GR, APEX/General) · S. Desai (SD, BU).

What is deliberately NOT built (don't look for it)

Thing	Status
CAPEX PRR screens	Never built — CAPEX has no in-app PRR (Chapter 5).
GRN / Invoice / FICO / Cost-Center screens	Not built — all downstream Context (Chapter 2).
Requestor validation / agent screens	Not built — Requestor is view-only (Chapter 3).
Global Search & Trace (A8)	Not built — `#` placeholder. Lineage is followed via line-detail (Chapter 8).
System / Data / Report Governance (Admin)	WIP placeholders → `work-in-progress.html`.
Real authentication / real SAP data	Prototype only — any password, hard-coded rows.

The one thing to remember

Five persona folders, one shared login, one shared agent engine. requestor/ watches, doa-approver/ decides, admin/ wires the system, business-admin/ sets the rules, analytics/ observes — and every "agent screen" across them is a shim into the single agent-flow.html. If you can name which folder a screen lives in, you already know what it can and cannot do.

You've reached the end of Zero to Hero v2. Now open new_screens/login.html in a browser, type each username, and walk the folders — they'll read like old friends. That was the whole goal.