Remove honeypot fields from US-1 and US-3
Honeypot spam protection is overengineered for this project's scope. Removed the acceptance criteria from both stories and added addenda documenting the decision. Updated implementation order and review findings accordingly. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
@@ -37,9 +37,9 @@ The vertical slice. After these three stories, the app is usable: an organizer c
|
||||
|
||||
| # | Story | Depends on | Delivers |
|
||||
|---|-------|------------|----------|
|
||||
| 1 | US-1: Create event | T-4 | Event creation with tokens, localStorage, honeypot |
|
||||
| 1 | US-1: Create event | T-4 | Event creation with tokens, localStorage |
|
||||
| 2 | US-2: View event page | US-1 | Public event page with attendee list, expired state |
|
||||
| 3 | US-3: RSVP | US-2 | Attend/decline flow, localStorage dedup, honeypot |
|
||||
| 3 | US-3: RSVP | US-2 | Attend/decline flow, localStorage dedup |
|
||||
|
||||
### Increment 2: Organizer Toolset — US-5, US-4
|
||||
|
||||
|
||||
Reference in New Issue
Block a user