# @garuda/customer-view — the Customer Runtime view

A **data-driven** operational dashboard for the customer (Retailer A) — generated from a **live platform run**
(engine + event log + encoder + projections), not a mock.

## What the customer sees — and doesn't
Per **PRD-CFG-018**, the Customer Runtime shows **operations only**: the inbound shipment, cartons and their status,
inventory posted, and exceptions that need attention. It shows **no** Blueprint / pillars / config / Solution Studio —
those are i-TEK-internal. The UI vocabulary is the customer's: *Shipment, PO, Cartons, Items, Accepted / On Hold /
Rejected, Inventory, Exceptions.*

## How it's generated
`snapshot.js` runs a realistic inbound day (4 clean cartons + 2 exceptions: a short count and an unrecognised tag)
through the real platform, derives the customer model (cartons from the run, **inventory from the event-log
projection**), injects it into `template.html`, and writes `customer-view.html` (self-contained; safe to publish as an
Artifact).

```
node snapshot.js   # → snapshot.json + customer-view.html
```

## Files
- `snapshot.js` — runs the platform, builds the customer model, renders the page.
- `template.html` — the crafted, theme-aware dashboard (Artifact-ready; `"__SNAPSHOT__"` placeholder).
- `customer-view.html` / `snapshot.json` — generated output.