# Checkpoint 000001 — Neighborhood volunteer signup

Saved: 2026-09-16 12:08 EDT (local machine time)

## Goal
Prototype a small signup page for a fictional neighborhood volunteer event (see
`PROJECT.md`). A visitor can see the date, location and available roles and submit
an RSVP; the coordinator needs a readable list of RSVPs. There is no backend yet.

## Decisions to preserve
These are the user's decisions, stated in this session — not agent inference:

- **No accounts or sign-in for volunteers.** The RSVP form still collects `name`
  and `email`, so this is "no authentication," not anonymity. Nothing here decides
  how that data is stored or displayed.
- **The coordinator manages capacity by hand in the pilot.** No automated capacity
  enforcement or role-limit logic is being asked for.
- **A waitlist "can wait."** Deliberately deferred, not rejected.
- **Preserve the RSVP field names `name`, `email` and `role`.** These are the
  existing draft fields in `PROJECT.md` line 7 and should carry through.

No reasons beyond the above were stated in this session; the pilot framing is the
user's own wording.

## Current state
- Nothing has been implemented or tested. This is confirmed by both `PROJECT.md`
  and the user's statement in this session, not by any build or test run.
- Files present in the project root: `PROJECT.md`, `.bakery/`, `.claude/`.
  No application source files exist yet.
- Not a git repository, so there is no branch or commit to record.
- This session made no application changes; the only file written is this
  checkpoint.

## Unresolved
- No decision yet on where RSVPs are stored or how the coordinator's readable
  list is produced (file, in-memory, static page — all still open).
- The event date, location and the actual list of roles are not specified anywhere
  in the project.
- No disagreements outstanding. The absence of tests reflects that nothing has
  been built yet, not a gap in the work.

## Next useful step
Pick the first increment and build only that — most likely a static signup page
rendering date, location and roles plus an RSVP form using exactly the fields
`name`, `email`, `role`. Before acting, re-read `PROJECT.md` (9 lines) and the
decisions above. Deliberately deferred: waitlist, capacity enforcement, any
sign-in or account system, any backend.

## Return brief
You paused right after settling scope, before any code existed. The shape agreed
on: a simple signup page with an RSVP form whose fields stay `name`, `email`,
`role`; no sign-in for volunteers; the coordinator handles capacity manually
during the pilot; waitlist deferred. Open questions are mostly about storage and
the concrete event details (date, location, roles) — you will need to supply or
invent those to build the page.