docs: 1045 - explore findings for cost-for-event confirmation - #1073
Draft
leahpeker wants to merge 1 commit into
Draft
docs: 1045 - explore findings for cost-for-event confirmation#1073leahpeker wants to merge 1 commit into
leahpeker wants to merge 1 commit into
Conversation
Open
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
Exploration/scoping spec for #1045 — "cost for event". The issue asks that users confirm they paid before an RSVP is finalized, across three flows: signed-in member/token holder, not-signed-in member (sign in first), and brand new person (join form first).
This PR is investigation-only — no application code. Key finding: the payment data model and UI already exist end-to-end (
Event.price/venmo_link/cashapp_link/zelle_info, already rendered byCostSection); what's missing is a required confirmation gate before RSVP submission. Full findings, code references, options (client-only gate vs. server-enforced gate), a recommendation, and open questions are in the spec:docs/superpowers/specs/2026-07-21-cost-for-event-explore.mdCloses #1045
Test plan