Skip to content

Feature cards

One page per MVP feature, written before its code (decision A13). A card is done when a builder — a person or an AI — can work from it without guessing.

Card template

# <Mx> — <feature name>

Status: draft | agreed · Last session: <date>

## Who and the job
Who uses it, and the one job it does for them.

## Value
Why it exists. What breaks or gets worse without it.

## Placement
Where it sits on mobile, tablet and web — and why there.

## Wireframe
Low-fi, text only. Mobile first, then web. Placement and flow, not colours or fonts.

## States
Empty · loading · error · long content · missing data (e.g. no photo).

## Rules and edge cases
The domain rules this feature must respect, with the reason for each.

## Decided
- ...

## TBD (decide by <date>)
- ...

## Backlog (after launch)
- ...

## Tasks
Small, testable items that go into `tasks.md`.

Order before launch (7 Oct 2026)

  1. M1 — day plan
  2. M13 — maps
  3. M5 — share link + booking status
  4. M7 — 3-click trip
  5. Services (M15, R5) — vehicles, bags, hotels
  6. M10 — leader's basics

Everything else after launch.