---
**date:** 2026-01-01
**description:** Example ticket roadmap , an ordered backlog used to deliver the product incrementally, with a visible acceptance criterion per ticket. This roadmap is written by the user; it is shipped only as an example.
**tags:** roadmap, tickets, mvp, planning
---

# Tickets (example)

> This is an example roadmap shipped by the Living Documentation starter. Replace the tickets below with the project's real backlog. AI agents must rely on this roadmap to decide which ticket to pick up next.

## Checking convention

- `[ ]` or `[]` , ticket not started;
- `[x] ~~Ticket XX - ...~~` , ticket done, struck through for quick scanning.

## Recommended order

1. [x] ~~Ticket 01 - Initialize the project~~
2. [ ] Ticket 02 - First screen of the nominal flow

> This is an example ticket for the user (remove this line once the real roadmap is written)

## Ticket 01 - Initialize the project

Goal: lay down the application foundations, ready to evolve.

Tasks:

- create the project structure (folder layout, baseline dependencies);
- configure linting and formatting;
- add a minimal layout and a routing system;
- verify that the application starts locally.

Acceptance criteria:

- the application starts locally without errors;
- the main routes exist;
- the code is typed if the stack allows it;
- no backend is required at this stage.

## Ticket 02 - Complete me ...