# parity-audit

A reproducible comparison between the **Navagoo 2.0 React mockup** (the design and
behaviour baseline) and the **Yii2 portal** as deployed to staging, covering the shop
and admin portals.

Self-contained: nothing here modifies or depends on `ai_specs/`.

## Layout

Work runs **Admin portal first, then Shop portal**, and the deliverables are separated so
the admin backlog is independently handover-ready while the shop audit is still running.

| Path | Contents |
|---|---|
| `00_SPEC/` | Design spec — scope, rubric, severity model, method |
| `01_BASELINE/{admin,shop}/` | Extracted mockup contracts, screen/modal inventory, demo-artifact exclusions |
| `02_EVIDENCE/{admin,shop}/` | Screenshots, probe transcripts, worked examples, test-data log |
| `03_FINDINGS/{admin,shop}/` | Per-area findings with verification records |
| `REPORT_ADMIN.md` · `REPORT_SHOP.md` | The verdict, per portal |
| `BOARD_ADMIN.html` · `BOARD_SHOP.html` | Side-by-side visual evidence board, per portal |
| `BACKLOG_ADMIN.md` · `BACKLOG_SHOP.md` | Ticket-ready remediation items, per portal |
| `REPORT.md` | Cross-portal summary, written last |

## Baselines

| Side | Ref |
|---|---|
| Mockup | `Navagoo 2.0` · `dev` @ `cb48c8d` (v0.28.0) |
| Portal | `NavagooBackend` · `tailwind-poc` @ `5efbafc9` |
| Staging | captured at audit start, recorded in `REPORT.md` |

## Conventions

Findings state **observed state versus baseline** and are classified by cause
(deviation / gap / drift) and by cause of absence (not built / built-not-configured /
built-not-working). Findings are never attributed to a person. See
[`00_SPEC/PARITY_AUDIT_SPEC.md`](00_SPEC/PARITY_AUDIT_SPEC.md) §11.

Credentials are held outside the repository and are never committed here.

## Re-running

See `00_SPEC/PARITY_AUDIT_SPEC.md` §15.