Scope: version control for design

Choice: Babul is redrawn from a blank page, one screen at a time, each approved by the owner: Capture → Journey → Pages → Components → Styles, Analysis of the live product, AI, a CLI and an MCP server, and every change a commit on a branch that merges to main as a version. The screens in .context/designs/web/ are the spec; the app is rebuilt to them, zero legacy. Rules: .claude/rules/simplicity.md.

• No component kit of its own: components come from a capture, an imported design system, or are made in Babul.

Why: the owner, 2026-10-22: the product had been over-engineered. A 66-component kit with its own releases and update conflicts is a second product.

Rejected: the 2026-10-16 to 10-21 editor (branch page, drawn elements, Figma-like component sets, schemas 0020 and 0024, settings placement), all replaced by the redesign · packages/kit.