# The proposal note

A one-page HTML note that carries a decision to Frank (or a counterpart): what the problem is, the options, one recommendation, and what implementing it would touch. Born 2026-07-21 from the Lesotho "Guides & law in the navigation" proposal (Frank: "this is our format").

**When to use:** any time the deliverable is a recommendation between mechanisms (a navigation change, a feature placement, a layout choice). Not for pure concept visions (that is `formats/vision-paper`), not for diagnoses.

## The skeleton, in order

1. **The problem, one line.** What citizens (or users) cannot do today.
2. **The options.** One numbered card per mechanism, each with what it is (one line) and a small pro and con. Two to four options, never more.
3. **The recommendation.** One option named, the why in two or three plain sentences. It may combine mechanisms; then say exactly what is taken from each.
4. **The implementation note.** Six to ten lines: what would actually change (pages added, menu edits, slugs), so the build can be scoped without rereading anything.
5. **The mockup cards.** One card per mockup, with a live preview and a link that opens it. Mockups are the product's REAL chrome with the change applied, never a new-looking website.

## Rules

- The look comes from the modern-ui gate (`~/.claude/skills/modern-ui/SKILL.md`); the documentation kit is one of its answers. Always: Teletubbies, Kennedy, sentence case, a light mode for any dark page, no em dashes, simple words.
- Every mention of an existing page links to its real URL (cite = link).
- Labels a citizen understands; no internal jargon.
- The note stands alone: a reader who opens only this file can decide.

**Exemplar:** `exemplar.html` beside this file (the Lesotho guides-navigation proposal; original at `2 - eR services/countries/Lesotho/public-pages/guides-nav-proposal/index.html`).