Add standalone design context prototype and WHAT spec.

Ship the browsable mosaic document as an isolated HTML file and document the build intent in WHAT.md so the categorization work has a concrete UI target.

Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
Abdul Wahab
2026-09-01 10:02:40 +05:00
co-authored by Cursor
parent c06bf3f558
commit bf8e3ee0c2
3 changed files with 2664 additions and 0 deletions
@@ -9,6 +9,7 @@ Source examples analyzed (local scratch runs, not tracked in this repo):
## Documents
- [`WHAT.md`](./WHAT.md) — first draft of what we're building: a visual, browsable rendering of this categorization on the live site.
- [`CONTENTS.md`](./CONTENTS.md) — what maps where, per category, with gaps and rationale.
- [`CONTENTS-TABLE.md`](./CONTENTS-TABLE.md) — the same mapping as lean per-category Value / Derived from / Source tables, no prose.
- [`MISSING.md`](./MISSING.md) — content gaps neither example run produces, regardless of category.