Repository navigation
Description
Feature Summary
Store waitlist registrations with truthful receipt feedback; reconcile waitlist/newsletter terminology before changing routes or transport. The existing M estimate remains unchanged.
Linked Stories/Tasks
Parent: #16. Project: This One Time on Acid — book. Shared capture, deployment and verification separate.
Milestones & Timeline
No milestone, cycle, due date or release date requested.
Proposed Solution
Update src/app/components/pages/book-site/WaitlistPage.tsx. Replace mock handler with shared waitlist transport, named required email, source-route /waitlist, form-name/honeypot. Remove hardcoded-email bypass. Distinguish unverified acknowledgement from evidenced receipt and confirmed enrolment. An accepted response alone does not establish stored receipt or confirmed subscription. For an unverified outcome, use neutral acknowledgement without success wording, styling, announcements, checkmark or confetti. Preserve reduced-motion support. Success feedback must be limited to the outcome actually supported by evidence; retention of celebratory effects requires a separately scoped presentation proposal and approval. Retain input on failure, explicit retry, accessible status and focus/announcement when feedback replaces the form. The announcement must distinguish an unverified outcome from evidenced receipt or confirmed enrolment. Preserve mobile/themes. Centralise acknowledgement/copy; receipt is not confirmed Brevo subscription.
Linked Stories/Tasks
No PR linked. Operations owns recipients/monitoring. Newsletter at /newsletter is separate double opt-in.
Milestones & Timeline
Release timing remains unset.
Acceptance Criteria
- Controlled registration stored under waitlist with source-route /waitlist.
- All emails follow ordinary capture.
- Invalid, pending, failed, cancelled or unverified outcomes do not claim confirmed success or trigger success-specific presentation; known errors remain distinguishable from uncertainty.
- Failure retains email and allows explicit retry; no automatic repeat.
- Receipt feedback requires evidence of the claimed receipt; accepted response, stored receipt, confirmed subscription and verified manuscript access remain distinct. Unverified outcomes use neutral acknowledgement.
- Motion preference, keyboard/mobile/themes and focus verified.
- No automatic newsletter enrolment or customer-email promise.
- All acceptance criteria met
- Documentation/changelog updated
- Tests added/updated
- PR uses correct branch prefix (feat/)
- Labels/types match org standards
- PR description updated with relevant details
- Changelog entry prepared for PR (if applicable)
- Labels/types match org standards
Recorded neutral-copy candidate
The decision register’s “Neutral acknowledgement copy — wording approval, 11 November 2026” section records the following exact wording-approved candidate:
Heading: Waitlist registration not confirmed
Body: We can’t confirm that your email address has been added to the waitlist. No further action is confirmed on this screen.
Supporting text: Please don’t rely on this message as confirmation of future updates.
Wording approval does not establish runtime applicability or authorise implementation. Known failures require appropriate failure feedback; this candidate must not replace verified error information. Existing capture, retry, consent and verification requirements remain unchanged.
TOA - Book website — Design and reader decision register
Designs / References
Waitlist component, setup, project Figma Make/repository guidelines. Historical ranges 45–53,126–136 belong to original 76b1528 audit.
Dependencies
Shared capture, enabled detection, verified deployment and approved copy/monitoring.
Testing Approach
Deferred success, validation, rapid duplicates, offline/HTTP failure/retry, bypass-address regression, live/focus feedback and reduced motion; verify stored receipt.
Additional Context
The former no-new-success-route restriction does not exclude the required newsletter/contact thank-you pages, proposed under #213 and #210. Existing waitlist and newsletter journeys remain distinct until their purpose and route relationship are explicitly agreed. Do not silently merge, redirect or enrol. Existing repository conventions and template defaults remain applicable.
Definition of Ready (DoR)
- Problem statement and outcome defined
- Acceptance criteria written (Given/When/Then)
- Designs/specs/references attached (if relevant)
- Dependencies mapped
- Estimate added
- Stakeholders/approvers listed
- Milestone/iteration assigned (if applicable)
Definition of Done (DoD)
- All acceptance criteria met
- Feature implemented and tested
- Tests added/updated; CI green
- Accessibility: WCAG 2.2 AA compliance verified (semantic HTML, keyboard support, colour contrast)
- Security: input validated, output escaped, no OWASP Top 10 vulnerabilities
- Performance: no measurable regression introduced
- Documentation/changelog updated if needed
- Feature toggles/rollout considered
- QA verified/UAT approved (if applicable)
- Release notes prepared; monitoring/alerts set
- Branch prefix is correct (feat/)
- Branch deleted after merge
- Linked issue(s) updated with latest status and closed after merge,
- The related epic should not be closed, instead updated with a comment to reflect the closed issue
Metadata
Metadata
Assignees
Labels
Type
Fields
Priority
Activity
linear-code commentedon Oct 5, 2026
TOA-210