# Human Tasks -- Party Bench

**Date compiled:** 2026-02-21
**81 total human tasks identified across 9 research areas**

---

## Table of Contents

1. [Venue Rental & Booking](#venue-rental--booking) (7 tasks)
2. [Catering & Food/Drinks](#catering--fooddrinks) (8 tasks)
3. [Music & Entertainment](#music--entertainment) (8 tasks)
4. [Logistics & Supplies](#logistics--supplies) (8 tasks)
5. [Legal & Liability](#legal--liability) (10 tasks)
6. [Invitations & Social](#invitations--social) (10 tasks)
7. [Physical Tasks](#physical-tasks) (10 tasks)
8. [Payments & Financial](#payments--financial) (7 tasks)
9. [Claude Code Integration](#claude-code-integration) (13 tasks)
10. [Effort-Based Grouping](#effort-based-grouping)

---

## Venue Rental & Booking

### [HT-001] Confirm Peerspace API access
- **Status:** pending
- **Priority:** medium
- **Category:** Phone calls
- **Context:** No public documentation was found for a Peerspace developer API, but a partner program may exist that allows venue search.
- **Specific actions:**
  1. Contact Peerspace partnerships team to determine if any private/partner API exists for venue search
  2. If available, request API documentation and onboarding requirements
- **Blocks:** venue-rental (programmatic venue search)
- **Output needed:** Confirmation of API availability, documentation link, or confirmed non-availability
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/venue-rental/_summary.md

### [HT-002] Verify Cvent pricing for enterprise API access
- **Status:** pending
- **Priority:** low
- **Category:** Phone calls
- **Context:** Cvent requires a sales consultation for pricing. If enterprise API access is needed for venue sourcing across 300,000+ venues, a human must request a quote.
- **Specific actions:**
  1. Contact Cvent sales team via their developer portal
  2. Request pricing for API access with venue sourcing capabilities
  3. Document pricing tiers and rate limits
- **Blocks:** venue-rental (enterprise venue sourcing)
- **Output needed:** Pricing quote document or email
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/venue-rental/_summary.md

### [HT-003] Test MeetingPackage API access
- **Status:** pending
- **Priority:** low
- **Category:** Account/API setup
- **Context:** MeetingPackage developer API access requires filling out a request form and a short call with their team.
- **Specific actions:**
  1. Fill out the MeetingPackage API access request form
  2. Complete the introductory call with their team
  3. Obtain API credentials and test basic search endpoints
- **Blocks:** venue-rental (meeting/event venue search)
- **Output needed:** API credentials and confirmation of working access
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/venue-rental/_summary.md

### [HT-004] Evaluate Nowadays for corporate event planning
- **Status:** pending
- **Priority:** low
- **Category:** Expert consultation
- **Context:** Nowadays is a YC-backed AI-powered venue booking service for corporate events with $20K+ budgets. Worth evaluating if planning corporate events.
- **Specific actions:**
  1. Visit https://www.nowadays.ai/ and submit an inquiry
  2. Evaluate their AI booking service against direct platform usage
  3. Document pricing, capabilities, and limitations
- **Blocks:** venue-rental (corporate events only)
- **Output needed:** Evaluation summary comparing Nowadays vs. direct booking
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/venue-rental/_summary.md

### [HT-005] Check Splacer current operational status
- **Status:** pending
- **Priority:** low
- **Category:** Verification calls/emails
- **Context:** Splacer withdrew insurance coverage in late 2023 and appeared to have reduced activity. Need to verify if the platform is still actively operating and accepting new bookings.
- **Specific actions:**
  1. Visit https://splacer.co and attempt to browse/search venues
  2. Contact Splacer support to verify active status
  3. Check if new bookings are being accepted
- **Blocks:** venue-rental (platform evaluation)
- **Output needed:** Confirmed operational status (active/inactive/limited)
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/venue-rental/_summary.md

### [HT-006] Procure event liability insurance
- **Status:** pending
- **Priority:** high
- **Category:** Payment
- **Context:** For any actual venue booking, event liability insurance ($1M coverage, ~$150-$300 for day-of) must be procured. This cannot be fully automated on consumer platforms.
- **Specific actions:**
  1. Determine coverage requirements based on venue and event type
  2. Obtain quotes from The Event Helper, Eventsured, or Markel
  3. Purchase appropriate coverage and obtain certificate of insurance
  4. Add venue as additional insured if required
- **Blocks:** venue-rental (required before booking most venues)
- **Output needed:** Certificate of insurance document
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/venue-rental/_summary.md

### [HT-007] Review web scraping legality for venue data
- **Status:** pending
- **Priority:** medium
- **Category:** Expert consultation
- **Context:** If considering scraping Peerspace/Giggster for venue data in lieu of an API, a legal review of their Terms of Service is needed. This likely violates their ToS.
- **Specific actions:**
  1. Review Peerspace and Giggster Terms of Service for anti-scraping provisions
  2. Consult with a lawyer if scraping is being considered
  3. Document legal risks and alternative approaches
- **Blocks:** venue-rental (data acquisition strategy)
- **Output needed:** Legal assessment document (scrape vs. no-scrape decision)
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/venue-rental/_summary.md

---

## Catering & Food/Drinks

### [HT-008] Verify ezCater API for consumer-side ordering
- **Status:** pending
- **Priority:** high
- **Category:** Phone calls
- **Context:** ezCater's API is primarily restaurant-facing (accept/reject orders, menu sync). Need to determine if their API can be used to programmatically place orders as a consumer.
- **Specific actions:**
  1. Contact ezCater developer relations at https://api.ezcater.io/
  2. Ask specifically about consumer-side programmatic order placement
  3. Document API capabilities, limitations, and access requirements
- **Blocks:** catering-food (programmatic catering orders)
- **Output needed:** Confirmation of consumer ordering API availability and documentation
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/catering-food/_summary.md

### [HT-009] Check local alcohol delivery laws
- **Status:** pending
- **Priority:** high
- **Category:** Expert consultation
- **Context:** Alcohol delivery legality varies dramatically by state/county/city. Before building any alcohol ordering feature, legality must be verified in target jurisdictions.
- **Specific actions:**
  1. Identify target event jurisdictions
  2. Check state ABC agency websites for delivery regulations
  3. Verify local municipality rules for alcohol delivery
  4. Document permitted delivery methods per jurisdiction
- **Blocks:** catering-food (alcohol delivery feature)
- **Output needed:** Jurisdiction-specific legal summary for alcohol delivery
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/catering-food/_summary.md

### [HT-010] Apply for Instacart Developer Platform access
- **Status:** pending
- **Priority:** high
- **Category:** Account/API setup
- **Context:** Instacart IDP is the most viable grocery API for bulk party supply ordering (1B+ products, 85K+ stores, same-day delivery). Requires business registration.
- **Specific actions:**
  1. Visit https://www.instacart.com/company/business/developers
  2. Complete the business registration and application
  3. Obtain API credentials and test in sandbox
- **Blocks:** catering-food, logistics-supplies (grocery ordering)
- **Output needed:** API credentials and working sandbox access
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/catering-food/_summary.md

### [HT-011] Negotiate DoorDash LOF addendum
- **Status:** pending
- **Priority:** medium
- **Category:** Document signing
- **Context:** DoorDash's Large Order Fulfillment (LOF) program requires signing an addendum to the DoorDash agreement. LOF provides premium Dashers for catering-scale deliveries.
- **Specific actions:**
  1. Submit a support ticket to DoorDash developer support
  2. Request the LOF addendum
  3. Review and sign the addendum
  4. Test LOF delivery endpoint in sandbox
- **Blocks:** catering-food (large order delivery)
- **Output needed:** Signed LOF addendum and confirmed API access
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/catering-food/_summary.md

### [HT-012] Evaluate Uber Eats Consumer Delivery APIs early-access
- **Status:** pending
- **Priority:** medium
- **Category:** Phone calls
- **Context:** Uber Eats Consumer Delivery APIs are in early-access phase with case-by-case access. Could be valuable for large group orders.
- **Specific actions:**
  1. Contact Uber developer relations about Consumer Delivery API access
  2. Submit an application explaining the party planning use case
  3. Document timeline and requirements for access
- **Blocks:** catering-food (consumer delivery API)
- **Output needed:** Access status and timeline estimate
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/catering-food/_summary.md

### [HT-013] Test Kroger API for party supply cart building
- **Status:** pending
- **Priority:** medium
- **Category:** Account/API setup
- **Context:** Kroger's public API is the most accessible for immediate experimentation with product catalog search, pricing, and cart building.
- **Specific actions:**
  1. Register at https://developer.kroger.com/
  2. Obtain API credentials
  3. Test product search and cart building endpoints
  4. Evaluate suitability for party supply ordering
- **Blocks:** catering-food (grocery/supply ordering)
- **Output needed:** Working API integration and suitability assessment
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/catering-food/_summary.md

### [HT-014] Research Thirstie partnership for alcohol delivery
- **Status:** pending
- **Priority:** low
- **Category:** Phone calls
- **Context:** With Drizly shut down, Thirstie's B2B platform may be the most compliant route for alcohol delivery integration.
- **Specific actions:**
  1. Contact Thirstie at https://thirstie.com/
  2. Inquire about partnership opportunities for event-based alcohol delivery
  3. Document compliance features and integration requirements
- **Blocks:** catering-food (alcohol delivery)
- **Output needed:** Partnership feasibility assessment and pricing
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/catering-food/_summary.md

### [HT-015] Define dietary restriction data schema
- **Status:** pending
- **Priority:** medium
- **Category:** Judgement calls
- **Context:** A structured data format is needed for collecting and transmitting dietary needs that maps to standard catering categories (vegetarian, vegan, gluten-free, nut allergy, etc.).
- **Specific actions:**
  1. Review standard dietary categories from catering industry
  2. Design a JSON schema for dietary restriction data
  3. Determine severity levels (preference vs. medical requirement)
  4. Map schema fields to catering platform APIs
- **Blocks:** catering-food, invitations-social (dietary data collection and use)
- **Output needed:** JSON schema document and mapping reference
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/catering-food/_summary.md

---

## Music & Entertainment

### [HT-016] Book DJ/performer manually
- **Status:** pending
- **Priority:** high
- **Category:** In-person visits
- **Context:** No DJ/performer booking platform (GigSalad, The Bash, Bark.com) offers a public API. Booking must be done manually through web interfaces or by contacting vendors directly.
- **Specific actions:**
  1. Browse GigSalad, The Bash, or Bark.com for performers in the target area
  2. Request quotes from 3-5 DJs/performers
  3. Compare pricing, availability, and reviews
  4. Book selected performer and arrange deposit payment
- **Blocks:** music-entertainment (live entertainment)
- **Output needed:** Confirmed booking with contract and payment receipt
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/music-entertainment/_summary.md

### [HT-017] Apply for Spotify Extended Quota Access
- **Status:** pending
- **Priority:** medium
- **Category:** Account/API setup
- **Context:** If building a party app serving >5 users, a registered business entity must apply for Spotify Extended Quota mode. Requirements include 250K+ MAU, legal business registration, and presence in key Spotify markets.
- **Specific actions:**
  1. Verify current requirements at Spotify Developer Dashboard
  2. Register a business entity if not already done
  3. Submit Extended Quota application
  4. Document approval timeline and any restrictions
- **Blocks:** music-entertainment (multi-user playlist management)
- **Output needed:** Extended Quota approval or confirmed development-mode limitations
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/music-entertainment/_summary.md

### [HT-018] Obtain music performance licenses for public events
- **Status:** pending
- **Priority:** high
- **Category:** Payment
- **Context:** If the party is a public or corporate event, ASCAP, BMI, and SESAC licenses are required. Private parties with close friends/family are exempt. Using a personal streaming subscription does NOT satisfy licensing.
- **Specific actions:**
  1. Determine if the event qualifies as public or private
  2. If public/corporate: contact ASCAP (min ~$128/event), BMI (min ~$160), and SESAC
  3. Obtain licenses and keep documentation on file
  4. Budget $200-$400+ per PRO per event/year
- **Blocks:** music-entertainment (legal music playback at public events)
- **Output needed:** License certificates from each applicable PRO
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/music-entertainment/_summary.md

### [HT-019] Book photo booth rental
- **Status:** pending
- **Priority:** low
- **Category:** In-person visits
- **Context:** No photo booth rental platform has a public API. Booking must be done manually. Typical cost: $700-$1,200 including props, backdrops, and unlimited prints.
- **Specific actions:**
  1. Research local photo booth rental companies or use Snapbar
  2. Request quotes for event date/time
  3. Book and arrange delivery/setup logistics
- **Blocks:** music-entertainment (photo entertainment)
- **Output needed:** Confirmed booking with contract
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/music-entertainment/_summary.md

### [HT-020] Set up venue smart speaker/lighting hardware
- **Status:** pending
- **Priority:** medium
- **Category:** Physical tasks
- **Context:** Sonos, Philips Hue, Nanoleaf, and other smart hardware must be physically installed and configured at the venue with WiFi connectivity before API control is possible.
- **Specific actions:**
  1. Purchase or rent required smart speakers and lighting hardware
  2. Physically install at venue and connect to WiFi
  3. Configure devices and test API control
  4. Verify connectivity stability for event duration
- **Blocks:** music-entertainment (programmatic music/lighting control)
- **Output needed:** Confirmed working hardware setup with API access verified
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/music-entertainment/_summary.md

### [HT-021] Verify SoundCloud API registration availability
- **Status:** pending
- **Priority:** low
- **Category:** External monitoring
- **Context:** SoundCloud API registration has historically been intermittently closed to new developers. Current status needs verification.
- **Specific actions:**
  1. Visit SoundCloud developer portal and attempt to register
  2. Document current registration status and any restrictions
- **Blocks:** music-entertainment (SoundCloud integration)
- **Output needed:** Registration status confirmation
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/music-entertainment/_summary.md

### [HT-022] Evaluate Kahoot Enterprise API access
- **Status:** pending
- **Priority:** low
- **Category:** Phone calls
- **Context:** If quiz-based entertainment is desired with official API access, Kahoot sales must be contacted for enterprise plan pricing.
- **Specific actions:**
  1. Contact Kahoot sales team
  2. Request enterprise plan pricing with API authorization
  3. Evaluate cost vs. alternative quiz solutions
- **Blocks:** music-entertainment (interactive game entertainment)
- **Output needed:** Pricing quote and API capability assessment
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/music-entertainment/_summary.md

### [HT-023] Monitor Tidal API playlist feature development
- **Status:** pending
- **Priority:** low
- **Category:** External monitoring
- **Context:** Tidal's playlist manipulation API is still under development and was listed as "TODO" in their GitHub discussions.
- **Specific actions:**
  1. Periodically check Tidal developer portal for updates
  2. Monitor https://github.com/orgs/tidal-music/discussions/6
- **Blocks:** music-entertainment (Tidal integration)
- **Output needed:** Notification when playlist API becomes available
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/music-entertainment/_summary.md

---

## Logistics & Supplies

### [HT-024] Apply for API access (Instacart, TaskRabbit, Uber, Lyft)
- **Status:** pending
- **Priority:** high
- **Category:** Account/API setup
- **Context:** Instacart IDP, TaskRabbit Partner API, Uber for Business, and Lyft Concierge all require business registration and/or partner approval. These are the core APIs for supply delivery, labor, and transportation.
- **Specific actions:**
  1. Apply for Instacart Developer Platform (if not done via HT-010)
  2. Apply for TaskRabbit Partner API at developer.taskrabbit.com
  3. Set up Uber for Business account and request Guest Rides API access
  4. Contact Lyft Business team for Concierge API access
- **Blocks:** logistics-supplies (supply ordering, labor, transport)
- **Output needed:** API credentials for each platform
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/logistics-supplies/_summary.md

### [HT-025] Select and contact local rental company
- **Status:** pending
- **Priority:** medium
- **Category:** Phone calls
- **Context:** No universal rental booking API exists for tables, chairs, tents. Must identify local companies and check if they use Booqable/EZRentOut/Rentman for potential API integration.
- **Specific actions:**
  1. Research local party rental companies in the event area
  2. Contact top 3 companies for pricing and availability
  3. Ask if they use Booqable, EZRentOut, or Rentman software
  4. Negotiate terms and reserve items
- **Blocks:** logistics-supplies (equipment rentals)
- **Output needed:** Confirmed rental reservation with itemized quote
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/logistics-supplies/_summary.md

### [HT-026] Assess venue-specific parking logistics
- **Status:** pending
- **Priority:** medium
- **Category:** In-person visits
- **Context:** Parking logistics depend entirely on the specific venue. Must be assessed on-site and communicated to guests.
- **Specific actions:**
  1. Visit the venue or review venue information for parking capacity
  2. Identify overflow parking options (nearby lots, street parking)
  3. Note any restrictions or time limits
  4. Prepare parking instructions for guest communications
- **Blocks:** logistics-supplies (guest transportation)
- **Output needed:** Parking instruction text suitable for guest communications
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/logistics-supplies/_summary.md

### [HT-027] Book waste management / dumpster rental
- **Status:** pending
- **Priority:** low
- **Category:** Phone calls
- **Context:** No major waste management company offers a public API. Dumpster rental (10-yard, $200-$400) must be booked via website or phone for parties of 30-50 people.
- **Specific actions:**
  1. Contact WM, Republic Services, or Budget Dumpster
  2. Book a 10-yard dumpster for event day (or day before)
  3. Arrange delivery and pickup schedule
- **Blocks:** logistics-supplies (waste management)
- **Output needed:** Confirmed dumpster booking with delivery/pickup times
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/logistics-supplies/_summary.md

### [HT-028] Order party-in-a-box kits (manual web ordering)
- **Status:** pending
- **Priority:** low
- **Category:** Payment
- **Context:** All party-in-a-box services (Sprinkles & Confetti, Luxe Party Shop, YourPartyBox) require manual web ordering with no API access.
- **Specific actions:**
  1. Browse party-in-a-box services for appropriate themed kits
  2. Select kit(s) matching party theme and guest count
  3. Place order with sufficient lead time for shipping
- **Blocks:** logistics-supplies (party supplies)
- **Output needed:** Order confirmation and tracking number
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/logistics-supplies/_summary.md

### [HT-029] Review and vet cleaning service providers
- **Status:** pending
- **Priority:** low
- **Category:** Judgement calls
- **Context:** Even with TaskRabbit's API for cleanup booking, reviewing Tasker profiles and ratings for quality assurance benefits from human judgment.
- **Specific actions:**
  1. Browse TaskRabbit for cleanup professionals in the event area
  2. Review profiles, ratings, and completed job history
  3. Shortlist 2-3 vetted candidates
  4. Book preferred candidate for post-event cleanup
- **Blocks:** logistics-supplies (post-event cleanup)
- **Output needed:** Vetted and booked cleanup professional
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/logistics-supplies/_summary.md

### [HT-030] Finalize supply quantities based on headcount
- **Status:** pending
- **Priority:** medium
- **Category:** Judgement calls
- **Context:** Final headcount and dietary/preference considerations (compostable vs. plastic, themed vs. generic) require human input to finalize the supply shopping list.
- **Specific actions:**
  1. Confirm final RSVP headcount (plan for 60-70% attendance of RSVPs)
  2. Decide on eco-friendly vs. standard disposables
  3. Choose themed vs. generic supplies
  4. Finalize quantities per item category
- **Blocks:** logistics-supplies (supply procurement)
- **Output needed:** Final supply shopping list with quantities
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/logistics-supplies/_summary.md

### [HT-031] Approve overall party budget
- **Status:** pending
- **Priority:** high
- **Category:** Judgement calls
- **Context:** Total supply budget of $150-$600+ (or $500-$3,000+ all-in including food, drinks, entertainment) needs human sign-off before procurement begins.
- **Specific actions:**
  1. Review itemized budget breakdown across all categories
  2. Approve total budget cap
  3. Set per-category spending limits
  4. Identify areas for cost reduction if over budget
- **Blocks:** logistics-supplies, catering-food, music-entertainment (all procurement)
- **Output needed:** Signed-off budget document with category limits
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/logistics-supplies/_summary.md

---

## Legal & Liability

### [HT-032] Attorney review of liability waiver templates
- **Status:** pending
- **Priority:** high
- **Category:** Expert consultation
- **Context:** Waiver enforceability varies by state (Louisiana, Montana, Virginia restrict them heavily). A generic template may not hold up in court. Attorney review is required before using any liability waivers.
- **Specific actions:**
  1. Draft or select a liability waiver template (Smartwaiver, DocuSign PowerForms)
  2. Engage an attorney licensed in the event state to review
  3. Incorporate attorney feedback and finalize waiver
  4. Set up digital distribution via chosen platform
- **Blocks:** legal-liability (guest waiver collection)
- **Output needed:** Attorney-approved liability waiver document
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/legal-liability/_summary.md

### [HT-033] Insurance broker consultation
- **Status:** pending
- **Priority:** high
- **Category:** Expert consultation
- **Context:** Need to determine exact coverage amounts for the specific event type, guest count, and jurisdiction. Must consider general liability, host liquor liability, event cancellation, and property damage.
- **Specific actions:**
  1. Contact an insurance broker specializing in event insurance
  2. Provide event details: type, guest count, venue, alcohol service
  3. Obtain quotes for general liability ($1M/$2M), host liquor liability, and cancellation
  4. Determine if umbrella/excess liability is warranted
- **Blocks:** legal-liability, venue-rental (insurance requirements)
- **Output needed:** Insurance coverage recommendation document and quotes
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/legal-liability/_summary.md

### [HT-034] Apply for Markel Special Event API partner access
- **Status:** pending
- **Priority:** medium
- **Category:** Account/API setup
- **Context:** Markel offers a Special Event API for programmatic quoting, payment, and policy issuance. This is the cleanest programmatic path for event insurance.
- **Specific actions:**
  1. Complete the API Partner Inquiry at https://www.markel.com/us/digital-distribution/api-partner-questionnaire
  2. Wait for approval and onboarding instructions
  3. Test quote and issuance endpoints in sandbox
- **Blocks:** legal-liability (programmatic insurance)
- **Output needed:** API partner credentials and working sandbox access
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/legal-liability/_summary.md

### [HT-035] Research local permit requirements per event
- **Status:** pending
- **Priority:** high
- **Category:** In-person visits
- **Context:** Noise permits, temporary food service permits, and occupancy limits are locally regulated with no centralized database. May require calling or visiting local government offices.
- **Specific actions:**
  1. Identify the city/county where the event will be held
  2. Check city website for special event permit requirements
  3. Determine if noise permit is needed (amplified sound outdoors)
  4. Check if food service permits are needed for caterers
  5. Verify occupancy limits for the venue
  6. Apply for required permits with sufficient lead time
- **Blocks:** legal-liability (regulatory compliance)
- **Output needed:** List of required permits with application status
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/legal-liability/_summary.md

### [HT-036] Determine liquor license requirements
- **Status:** pending
- **Priority:** high
- **Category:** Expert consultation
- **Context:** Private events with free alcohol generally do not need a license, but semi-public events or events where alcohol is sold require a temporary permit from the state ABC agency. Lead time of 10+ days is common.
- **Specific actions:**
  1. Determine if event is truly private (no ticket sales, cover charges, or donations)
  2. If alcohol will be sold: contact state ABC agency for temporary event permit
  3. Consider hiring a licensed caterer who holds their own liquor license
  4. Apply for permit if needed (10+ days before event)
- **Blocks:** legal-liability (alcohol service compliance)
- **Output needed:** Confirmed license/permit status or exemption documentation
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/legal-liability/_summary.md

### [HT-037] Execute venue bookings manually (do not automate)
- **Status:** pending
- **Priority:** high
- **Category:** Judgement calls
- **Context:** Most venue platforms (Airbnb, Peerspace) explicitly prohibit automated/bot interactions in their ToS. AI can research and recommend, but a human must execute the actual booking.
- **Specific actions:**
  1. Review AI-generated venue recommendations
  2. Verify venue details, availability, and pricing on platform
  3. Create booking manually through the platform's web interface
  4. Complete identity verification if required
  5. Provide payment and insurance documentation
- **Blocks:** venue-rental (booking execution)
- **Output needed:** Confirmed booking with receipt and venue details
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/legal-liability/_summary.md

### [HT-038] Draft privacy policy for event RSVP system
- **Status:** pending
- **Priority:** high
- **Category:** Expert consultation
- **Context:** Collecting guest emails, dietary info, and other personal data triggers CCPA and potentially GDPR obligations. Dietary information may be "special category" data under GDPR (revealing religious beliefs or health conditions).
- **Specific actions:**
  1. Engage a lawyer to draft a privacy notice for the RSVP system
  2. Ensure CCPA compliance (transparency, opt-out rights)
  3. Ensure GDPR compliance if EU residents may attend (explicit consent, data minimization)
  4. Include data retention/deletion policy (delete after event)
  5. Present privacy notice at point of data collection
- **Blocks:** invitations-social, legal-liability (data collection compliance)
- **Output needed:** Privacy policy/notice document ready for deployment
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/legal-liability/_summary.md

### [HT-039] Review AI platform Terms of Service
- **Status:** pending
- **Priority:** medium
- **Category:** Expert consultation
- **Context:** Need to understand indemnification obligations and liability allocation in the ToS of any AI platform (Claude, OpenAI) used for AI-initiated transactions.
- **Specific actions:**
  1. Review Anthropic's Claude Terms of Service for liability provisions
  2. Review any other AI platform ToS being used
  3. Understand indemnification clauses and liability allocation
  4. Document key obligations and restrictions
- **Blocks:** legal-liability (liability framework)
- **Output needed:** Summary of key ToS provisions affecting liability
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/legal-liability/_summary.md

### [HT-040] Verify state-specific social host liability laws
- **Status:** pending
- **Priority:** high
- **Category:** Expert consultation
- **Context:** Social host liability laws exist in 43 states and can hold party hosts liable for injuries caused by intoxicated guests. Laws vary significantly; 7 states + DC have no such statute.
- **Specific actions:**
  1. Identify the state where the event will be held
  2. Research that state's social host liability statute
  3. Identify specific triggers (serving minors, serving visibly intoxicated persons)
  4. Document precautions and requirements
  5. Consider hiring a professional bartender trained in responsible service
- **Blocks:** legal-liability (alcohol service liability)
- **Output needed:** State-specific social host liability summary
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/legal-liability/_summary.md

### [HT-041] New York ESRA legal consultation
- **Status:** pending
- **Priority:** low
- **Category:** Expert consultation
- **Context:** New York has NOT adopted UETA. It uses ESRA instead, which has different provisions for electronic contract formation by AI agents. NY-specific counsel is needed if operating there.
- **Specific actions:**
  1. If operating in New York, consult NY-licensed attorney
  2. Review ESRA provisions for electronic agent transactions
  3. Document differences from UETA that affect AI-initiated purchases
- **Blocks:** legal-liability (NY operations only)
- **Output needed:** NY-specific legal guidance document
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/legal-liability/_summary.md

---

## Invitations & Social

### [HT-042] Choose primary email API
- **Status:** pending
- **Priority:** high
- **Category:** Judgement calls
- **Context:** Must decide between Resend (best DX, 3K/month free), SendGrid (largest ecosystem, 100/day free), or Amazon SES (cheapest at scale, $0.10/1K).
- **Specific actions:**
  1. Evaluate Resend, SendGrid, and Amazon SES against project requirements
  2. Consider: free tier limits, template capabilities, webhook support, SDK languages
  3. Make selection and document rationale
- **Blocks:** invitations-social (invitation sending infrastructure)
- **Output needed:** Documented decision with rationale
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/invitations-social/_summary.md

### [HT-043] Decide on Luma Plus subscription vs. custom build
- **Status:** pending
- **Priority:** medium
- **Category:** Judgement calls
- **Context:** Luma API requires a Luma Plus subscription. Need to determine if the subscription cost is worth it for API access vs. building custom invitation UX.
- **Specific actions:**
  1. Check current Luma Plus pricing
  2. Evaluate API capabilities vs. custom-built alternative
  3. Compare development time/cost for custom solution
  4. Make go/no-go decision on Luma Plus
- **Blocks:** invitations-social (event creation platform)
- **Output needed:** Decision document: Luma Plus vs. custom build
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/invitations-social/_summary.md

### [HT-044] Decide on private party platform strategy
- **Status:** pending
- **Priority:** high
- **Category:** Judgement calls
- **Context:** Partiful, Evite, and Paperless Post lack APIs. Must decide whether to build custom invitation UX, accept manual platform usage, or use the unofficial Partiful API.
- **Specific actions:**
  1. Evaluate trade-offs: custom build (full control, dev cost) vs. manual usage (no automation) vs. unofficial API (risk of breakage)
  2. Consider target audience expectations (Gen Z expects Partiful)
  3. Document decision and rationale
- **Blocks:** invitations-social (invitation platform strategy)
- **Output needed:** Platform strategy decision document
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/invitations-social/_summary.md

### [HT-045] Register for chosen email API and obtain keys
- **Status:** pending
- **Priority:** high
- **Category:** Account/API setup
- **Context:** After choosing the email API (HT-042), must register, set up domain, and obtain API keys.
- **Specific actions:**
  1. Create account on chosen email platform (Resend/SendGrid/SES)
  2. Verify domain ownership (DNS records)
  3. Obtain API keys
  4. Test sending a sample email via API
- **Blocks:** invitations-social (email sending capability)
- **Output needed:** Working API credentials with verified domain
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/invitations-social/_summary.md

### [HT-046] Set up Twilio account for SMS reminders
- **Status:** pending
- **Priority:** medium
- **Category:** Account/API setup
- **Context:** Twilio SMS API ($0.0079/SMS) is recommended for day-of reminders and last-minute updates to guests.
- **Specific actions:**
  1. Create Twilio account
  2. Purchase a phone number
  3. Obtain Account SID and Auth Token
  4. Test sending a sample SMS
- **Blocks:** invitations-social (SMS communications)
- **Output needed:** Working Twilio credentials with phone number
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/invitations-social/_summary.md

### [HT-047] Provide guest list input
- **Status:** pending
- **Priority:** high
- **Category:** Judgement calls
- **Context:** The "social graph" problem is fundamentally a human knowledge problem. No API can determine who should be invited to a specific party. The host must provide guest names/contacts.
- **Specific actions:**
  1. Compile initial guest list (names, emails, phone numbers)
  2. Categorize guests (close friends, work colleagues, family, acquaintances)
  3. Note any social dynamics or seating considerations
  4. Provide in CSV, Google Sheets, or manual input format
- **Blocks:** invitations-social (all invitation and RSVP functions)
- **Output needed:** Guest list in structured format (CSV or spreadsheet)
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/invitations-social/_summary.md

### [HT-048] Get CloudSponge pricing quote
- **Status:** pending
- **Priority:** low
- **Category:** Phone calls
- **Context:** CloudSponge provides a contact picker widget/API for importing contacts from Gmail, Outlook, Yahoo, iCloud, etc. Pricing was not found during research.
- **Specific actions:**
  1. Contact CloudSponge at https://www.cloudsponge.com/
  2. Request pricing for contact import widget
  3. Evaluate cost vs. building direct Google People API integration
- **Blocks:** invitations-social (contact import feature)
- **Output needed:** Pricing quote and feature comparison
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/invitations-social/_summary.md

### [HT-049] Review privacy implications of guest data storage
- **Status:** pending
- **Priority:** high
- **Category:** Expert consultation
- **Context:** Storing guest contact details, dietary info, and RSVP data triggers privacy obligations. Dietary info may be GDPR special category data.
- **Specific actions:**
  1. Review data types being collected (names, emails, phones, dietary info)
  2. Implement data minimization (collect only what is needed)
  3. Set up data deletion policy (delete after event concludes)
  4. Ensure GDPR/CCPA compliance (see also HT-038)
- **Blocks:** invitations-social, legal-liability (data protection)
- **Output needed:** Data handling policy document
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/invitations-social/_summary.md

### [HT-050] Design custom invitation email templates
- **Status:** pending
- **Priority:** medium
- **Category:** Judgement calls
- **Context:** Custom invitation emails need to be designed to match the party theme. Resend supports React templates; others use HTML.
- **Specific actions:**
  1. Determine party theme and visual style
  2. Design invitation email template (React for Resend, or HTML)
  3. Include RSVP link, event details, and dietary restriction form
  4. Test rendering across email clients
- **Blocks:** invitations-social (invitation sending)
- **Output needed:** Email template files ready for deployment
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/invitations-social/_summary.md

### [HT-051] Monitor Facebook Graph API events capability
- **Status:** pending
- **Priority:** low
- **Category:** External monitoring
- **Context:** Meta has been steadily restricting API access. Facebook Graph API event creation capability should be re-verified before implementation.
- **Specific actions:**
  1. Periodically check Facebook Graph API documentation for event endpoints
  2. Monitor Meta developer blog for API restriction announcements
  3. Verify current status of pages_manage_events permission
- **Blocks:** invitations-social (social media event creation)
- **Output needed:** Status update on Facebook event API availability
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/invitations-social/_summary.md

---

## Physical Tasks

### [HT-052] Verify RentAHuman.ai reliability
- **Status:** pending
- **Priority:** medium
- **Category:** Account/API setup
- **Context:** RentAHuman.ai is a new marketplace (launched Feb 1-2, 2026) designed for AI agents to hire humans via MCP/REST API. Only 3 weeks old; reliability is unproven.
- **Specific actions:**
  1. Create an account on https://rentahuman.ai
  2. Post a small test task (e.g., pick up an item, take photos)
  3. Evaluate response time, quality, and platform reliability
  4. Document findings and assess readiness for party use
- **Blocks:** physical-tasks (AI-to-human task delegation)
- **Output needed:** Reliability assessment report
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/physical-tasks/_summary.md

### [HT-053] Apply for TaskRabbit Home Services API beta
- **Status:** pending
- **Priority:** high
- **Category:** Account/API setup
- **Context:** TaskRabbit's Delivery API is live, but the Home Services API (covering party setup, general tasks) is listed as "coming soon." Need to check for waitlist/beta access.
- **Specific actions:**
  1. Visit developer.taskrabbit.com
  2. Check for Home Services API waitlist or beta access
  3. Apply if available
  4. Test Delivery API endpoints in the interim
- **Blocks:** physical-tasks (programmatic task posting for setup/cleanup)
- **Output needed:** API access status and timeline
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/physical-tasks/_summary.md

### [HT-054] Test Fancy Hands API integration
- **Status:** pending
- **Priority:** medium
- **Category:** Account/API setup
- **Context:** Fancy Hands offers a REST API for submitting natural language tasks to virtual assistants ($29.99-$149.99/month). Assistants are remote/virtual only (no physical tasks) but can make phone calls and coordinate logistics.
- **Specific actions:**
  1. Create Fancy Hands account ($29.99/month for 5 requests)
  2. Obtain API keys from developer portal
  3. Submit a test custom request via API
  4. Validate the workflow: Claude Code -> Fancy Hands API -> human assistant
- **Blocks:** physical-tasks (virtual assistant intermediary)
- **Output needed:** Working API integration with test task completed
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/physical-tasks/_summary.md

### [HT-055] Get Wonolo API keys
- **Status:** pending
- **Priority:** low
- **Category:** Account/API setup
- **Context:** Wonolo has a developer API for scheduling on-demand workforce, though it focuses on warehouse/manufacturing. May be useful for logistics tasks.
- **Specific actions:**
  1. Apply at developer.wonolo.com
  2. Obtain API keys
  3. Evaluate suitability for event staffing tasks
- **Blocks:** physical-tasks (workforce scheduling)
- **Output needed:** API credentials and suitability assessment
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/physical-tasks/_summary.md

### [HT-056] Contact Qwick about individual host access
- **Status:** pending
- **Priority:** medium
- **Category:** Phone calls
- **Context:** Qwick is a hospitality staffing platform (250K+ professionals, 98% fill rate) but may require a business account. Need to determine if individual/non-business hosts can use it.
- **Specific actions:**
  1. Contact Qwick at https://www.qwick.com/
  2. Inquire about individual (non-business) host access
  3. Document account requirements and pricing
- **Blocks:** physical-tasks (professional event staffing)
- **Output needed:** Account eligibility confirmation and pricing
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/physical-tasks/_summary.md

### [HT-057] Verify local social host liability laws (for alcohol)
- **Status:** pending
- **Priority:** high
- **Category:** Expert consultation
- **Context:** Laws vary by state; critical for alcohol service decisions. 43 states have social host liability. Host is personally liable if intoxicated guests cause harm. (See also HT-040)
- **Specific actions:**
  1. Identify event state
  2. Research specific social host liability triggers
  3. Plan alcohol service protocols accordingly
- **Blocks:** physical-tasks, legal-liability (alcohol service safety)
- **Output needed:** State-specific liability summary with recommended protocols
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/physical-tasks/_summary.md

### [HT-058] Evaluate and obtain event liability insurance
- **Status:** pending
- **Priority:** high
- **Category:** Payment
- **Context:** Event liability insurance is needed to cover premises liability and alcohol-related incidents. Policies require a named human host. (See also HT-006, HT-033)
- **Specific actions:**
  1. Determine coverage requirements based on venue, guest count, alcohol
  2. Obtain quotes from Markel, The Event Helper, Eventsured
  3. Purchase coverage and obtain certificate
- **Blocks:** physical-tasks, legal-liability (insurance coverage)
- **Output needed:** Active insurance policy and certificate
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/physical-tasks/_summary.md

### [HT-059] Identify the on-site human host/proxy
- **Status:** pending
- **Priority:** high
- **Category:** Judgement calls
- **Context:** The minimum viable human involvement is ONE person as the AI's physical proxy. This person serves as the legal host, handles emergencies, manages alcohol service, and provides visual confirmation. This is the single most important human decision.
- **Specific actions:**
  1. Identify the person who will be physically present from setup through cleanup
  2. Ensure they understand their role as the legal host
  3. Brief them on: emergency procedures, alcohol service responsibilities, AI coordination protocol
  4. Ensure they have a charged phone for receiving AI instructions via SMS/Slack
- **Blocks:** physical-tasks (all physical execution)
- **Output needed:** Confirmed host name with contact info and briefing completed
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/physical-tasks/_summary.md

### [HT-060] Conduct dry run of AI-human coordination protocol
- **Status:** pending
- **Priority:** medium
- **Category:** Physical tasks
- **Context:** The SMS/Slack coordination protocol between AI director and human proxy needs to be tested before the actual event to identify communication issues.
- **Specific actions:**
  1. Set up the coordination channel (Twilio SMS or Slack)
  2. Run a simulated task sequence: AI sends instruction -> human executes -> human sends photo -> AI confirms
  3. Test edge cases: what if instructions are unclear? What if human needs to escalate?
  4. Document and refine the protocol
- **Blocks:** physical-tasks (event day coordination)
- **Output needed:** Tested and documented coordination protocol
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/physical-tasks/_summary.md

### [HT-061] Get local gig worker rate quotes
- **Status:** pending
- **Priority:** medium
- **Category:** Verification calls/emails
- **Context:** National average rates provided in research ($20-$50/hr for setup, $25-$45/hr for bartending). Actual costs depend on specific metro area and timing. Major metros can be 30-50% higher.
- **Specific actions:**
  1. Search TaskRabbit, Thumbtack, and Qwick for local rates
  2. Get quotes for: setup workers, servers, bartender, cleanup crew
  3. Compare platform rates vs. direct hire
  4. Document per-role costs for budget planning
- **Blocks:** physical-tasks (labor budgeting)
- **Output needed:** Local rate sheet for event staffing roles
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/physical-tasks/_summary.md

---

## Payments & Financial

### [HT-062] Legal review of AI spending authority
- **Status:** pending
- **Priority:** high
- **Category:** Expert consultation
- **Context:** Before deploying an AI agent with spending authority, legal counsel must assess Regulation E implications (debit cards), money transmitter licensing risk, and liability allocation.
- **Specific actions:**
  1. Consult attorney on Regulation E implications for AI-initiated debit transactions
  2. Determine if the use case triggers money transmitter licensing
  3. Review liability allocation in all relevant platform ToS
  4. Document approved spending authority framework
- **Blocks:** payments-financial (all AI-initiated spending)
- **Output needed:** Legal opinion letter on AI spending authority
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/payments-financial/_summary.md

### [HT-063] Set up virtual card / payment platform account
- **Status:** pending
- **Priority:** high
- **Category:** Account/API setup
- **Context:** A human must create business accounts with Privacy.com, Brex, Ramp, or similar. Most require KYB (Know Your Business) verification.
- **Specific actions:**
  1. Choose platform: Privacy.com (simplicity), Brex/Ramp (corporate integration), or Lithic (flexibility)
  2. Complete business registration and KYB verification
  3. Fund the account
  4. Create a test virtual card via API
  5. Set spending limits and merchant restrictions
- **Blocks:** payments-financial (AI spending capability)
- **Output needed:** Working virtual card API with funded account
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/payments-financial/_summary.md

### [HT-064] Verify tax implications of AI-initiated purchases
- **Status:** pending
- **Priority:** medium
- **Category:** Expert consultation
- **Context:** Need to clarify how AI-initiated purchases should be classified for tax purposes, especially for individual vs. business entity contexts.
- **Specific actions:**
  1. Consult with an accountant
  2. Determine tax classification for AI-initiated purchases
  3. Set up expense categorization for tax reporting
  4. Document deductibility rules if applicable
- **Blocks:** payments-financial (tax compliance)
- **Output needed:** Tax treatment guidance document
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/payments-financial/_summary.md

### [HT-065] Check business insurance coverage for AI transactions
- **Status:** pending
- **Priority:** medium
- **Category:** Verification calls/emails
- **Context:** Standard cyber liability policies may not cover losses from AI-initiated unauthorized transactions. Need to verify with insurance provider.
- **Specific actions:**
  1. Contact business insurance provider
  2. Ask specifically about coverage for AI-initiated unauthorized transactions
  3. Evaluate need for additional coverage or riders
  4. Document coverage gaps and remediation options
- **Blocks:** payments-financial (risk management)
- **Output needed:** Insurance coverage confirmation or gap analysis
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/payments-financial/_summary.md

### [HT-066] Select payment platform for AI agent
- **Status:** pending
- **Priority:** high
- **Category:** Judgement calls
- **Context:** Must choose between traditional virtual cards (Privacy.com, Brex/Ramp), crypto-native wallets (Coinbase Agentic Wallet), or full-stack agentic finance (Crossmint). Decision depends on what the agent needs to buy.
- **Specific actions:**
  1. List all merchant types the AI agent will transact with
  2. Evaluate platform compatibility with those merchants
  3. Compare: virtual cards (broadest acceptance) vs. crypto wallets (digital services) vs. full-stack (physical goods)
  4. Select platform and document rationale
- **Blocks:** payments-financial (payment infrastructure)
- **Output needed:** Platform selection document with rationale
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/payments-financial/_summary.md

### [HT-067] Establish compliance monitoring cadence
- **Status:** pending
- **Priority:** high
- **Category:** External monitoring
- **Context:** All AI-initiated transactions need regular human review. Recommended: daily alerts for first month, then weekly if no issues.
- **Specific actions:**
  1. Set up real-time transaction alerts to human reviewer
  2. Configure daily spending summary reports
  3. Create weekly expense review process with receipt matching
  4. Define escalation thresholds and anomaly detection rules
- **Blocks:** payments-financial (ongoing operations)
- **Output needed:** Documented monitoring procedure with alert configurations
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/payments-financial/_summary.md

### [HT-068] Test payment flow in sandbox environments
- **Status:** pending
- **Priority:** high
- **Category:** Account/API setup
- **Context:** Before live deployment, the full purchase flow must be tested in sandbox/test environments offered by payment platforms.
- **Specific actions:**
  1. Set up sandbox accounts on Stripe, Privacy.com, Lithic, Marqeta, or chosen platform
  2. Create test virtual cards
  3. Execute test purchases
  4. Verify transaction logging, alerts, and receipt capture
  5. Test spending limit enforcement and card freeze capabilities
- **Blocks:** payments-financial (production readiness)
- **Output needed:** Test results document confirming all flows work correctly
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/payments-financial/_summary.md

---

## Claude Code Integration

### [HT-069] Set up Anthropic API key with sufficient limits
- **Status:** pending
- **Priority:** high
- **Category:** Account/API setup
- **Context:** Agent Teams use significantly more tokens than single sessions. Need sufficient rate limits and budget for multi-agent usage.
- **Specific actions:**
  1. Verify current Anthropic API tier and rate limits
  2. Estimate token usage for multi-agent party orchestration
  3. Upgrade tier if necessary
  4. Set budget caps on API spending
- **Blocks:** claude-code-integration (all AI operations)
- **Output needed:** API key with confirmed rate limits and budget
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/claude-code-integration/_summary.md

### [HT-070] Create OAuth credentials for MCP servers
- **Status:** pending
- **Priority:** high
- **Category:** Account/API setup
- **Context:** Google Calendar, Gmail, Slack, and other MCP servers require OAuth credentials. Must register OAuth apps in each platform's developer portal.
- **Specific actions:**
  1. Create Google Cloud project and enable Calendar/Gmail APIs; set up OAuth consent screen and credentials
  2. Create Slack app with required scopes and obtain OAuth tokens
  3. Set up any other MCP server authentication (Stripe, Notion)
  4. Store credentials securely (vault or environment variables, NOT .env files)
- **Blocks:** claude-code-integration (MCP server connectivity)
- **Output needed:** Working OAuth credentials for each platform
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/claude-code-integration/_summary.md

### [HT-071] Set up Stripe account (test then production)
- **Status:** pending
- **Priority:** high
- **Category:** Account/API setup
- **Context:** Stripe is the primary payment infrastructure. Must configure in test mode first, then production. Webhook endpoints needed for real-time payment events.
- **Specific actions:**
  1. Create Stripe account if not existing
  2. Set up test mode and obtain test API keys
  3. Configure webhook endpoints for payment events
  4. Test payment flows in sandbox
  5. Switch to production when ready
- **Blocks:** claude-code-integration, payments-financial (payment processing)
- **Output needed:** Working Stripe integration in test mode
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/claude-code-integration/_summary.md

### [HT-072] Provision container environment for autonomous mode
- **Status:** pending
- **Priority:** high
- **Category:** Account/API setup
- **Context:** Running Claude Code with --dangerously-skip-permissions requires container isolation. Never run on personal machine. Docker, VM, or cloud instance required.
- **Specific actions:**
  1. Set up Docker environment or cloud VM
  2. Install Claude Code in container
  3. Configure AllowedTools whitelist and deny rules
  4. Test autonomous operation with safe tasks
  5. Set up monitoring and kill switches
- **Blocks:** claude-code-integration (autonomous execution)
- **Output needed:** Working containerized Claude Code environment
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/claude-code-integration/_summary.md

### [HT-073] Choose and set up secrets management approach
- **Status:** pending
- **Priority:** high
- **Category:** Judgement calls
- **Context:** Claude Code automatically reads .env files without permission. Must choose between proxy-based approach (most secure), environment variables via container, or MCP server OAuth flow.
- **Specific actions:**
  1. Evaluate security requirements for the project
  2. Choose approach: proxy-based (reverse proxy injects credentials) or container env vars
  3. Implement chosen approach
  4. Set up deny rules for sensitive files in permissions config
  5. Test that Claude Code cannot access raw credentials
- **Blocks:** claude-code-integration (security infrastructure)
- **Output needed:** Working secrets management with verified isolation
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/claude-code-integration/_summary.md

### [HT-074] Install and configure n8n for event-driven automation
- **Status:** pending
- **Priority:** medium
- **Category:** Account/API setup
- **Context:** n8n provides event-driven webhook processing, bridging real-time events (vendor confirmations, delivery updates, payment callbacks) into Claude Code sessions.
- **Specific actions:**
  1. Install n8n (self-hosted recommended)
  2. Connect to Stripe webhooks
  3. Connect to email provider notifications
  4. Set up Claude Code integration node
  5. Create basic event-driven workflows
- **Blocks:** claude-code-integration (event-driven automation)
- **Output needed:** Working n8n instance with webhook integrations
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/claude-code-integration/_summary.md

### [HT-075] Test Agent Teams feature in safe environment
- **Status:** pending
- **Priority:** medium
- **Category:** Physical tasks
- **Context:** Agent Teams is experimental with known limitations around session resumption and shutdown. Must be tested before relying on it for party coordination.
- **Specific actions:**
  1. Enable CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1
  2. Create a test team with 2-3 teammates
  3. Test task assignment, claiming, and completion
  4. Test failure recovery (what happens when a teammate dies?)
  5. Document limitations and workarounds
- **Blocks:** claude-code-integration (multi-agent coordination)
- **Output needed:** Test results and limitations document
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/claude-code-integration/_summary.md

### [HT-076] Create CLAUDE.md party brief
- **Status:** pending
- **Priority:** high
- **Category:** Judgement calls
- **Context:** The CLAUDE.md file is the master context for all AI agents. Must contain: vendor list, timeline, budget constraints, emergency contacts, and decision authority limits.
- **Specific actions:**
  1. Define party parameters (date, venue, guest count, theme)
  2. List all vendors with contact info and booking status
  3. Create detailed timeline from setup to cleanup
  4. Document budget constraints and per-category limits
  5. List emergency contacts
  6. Define decision authority limits (e.g., "can spend up to $100 without human approval")
- **Blocks:** claude-code-integration (AI agent context)
- **Output needed:** Complete CLAUDE.md file
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/claude-code-integration/_summary.md

### [HT-077] Set up monitoring dashboard
- **Status:** pending
- **Priority:** medium
- **Category:** Account/API setup
- **Context:** Need real-time visibility into multi-agent operations during party planning and execution. Open-source solution exists (claude-code-hooks-multi-agent-observability).
- **Specific actions:**
  1. Deploy monitoring solution (open-source or custom)
  2. Configure hooks for PostToolUse, PostToolUseFailure, SessionStart/End
  3. Set up real-time WebSocket dashboard
  4. Test with sample agent sessions
- **Blocks:** claude-code-integration (operational visibility)
- **Output needed:** Working monitoring dashboard
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/claude-code-integration/_summary.md

### [HT-078] Define permission boundaries for autonomous operations
- **Status:** pending
- **Priority:** high
- **Category:** Judgement calls
- **Context:** Must explicitly define which actions Claude can take autonomously vs. which require human approval. This maps to AllowedTools configuration and hook-based approval gates.
- **Specific actions:**
  1. List all actions the AI agent may take
  2. Categorize each as: fully autonomous, notify human, or require approval
  3. Set spending thresholds for auto-approve vs. human-approve
  4. Configure AllowedTools and deny rules in settings.json
  5. Implement approval hooks for threshold-exceeding actions
- **Blocks:** claude-code-integration (safety configuration)
- **Output needed:** Documented permission matrix and settings.json configuration
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/claude-code-integration/_summary.md

### [HT-079] Evaluate claude-flow for advanced multi-agent patterns
- **Status:** pending
- **Priority:** low
- **Category:** External monitoring
- **Context:** claude-flow is an open-source orchestration framework (12.9k stars) providing 60+ agents and distributed swarm intelligence. May offer capabilities beyond native Agent Teams.
- **Specific actions:**
  1. Review claude-flow at https://github.com/ruvnet/claude-flow
  2. Evaluate features vs. native Agent Teams
  3. Test in sandbox if promising
  4. Decide whether to adopt
- **Blocks:** claude-code-integration (optional enhancement)
- **Output needed:** Evaluation summary with adopt/skip recommendation
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/claude-code-integration/_summary.md

### [HT-080] Set up Git repository for party project
- **Status:** pending
- **Priority:** low
- **Category:** Account/API setup
- **Context:** A Git repository would enable versioned state tracking of all party planning artifacts, leveraging Claude Code's git integration.
- **Specific actions:**
  1. Create Git repository for party project
  2. Set up directory structure for shared coordination files
  3. Configure .gitignore for secrets and temporary files
- **Blocks:** claude-code-integration (version control)
- **Output needed:** Initialized Git repository with structure
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/claude-code-integration/_summary.md

### [HT-081] Create fallback procedures document
- **Status:** pending
- **Priority:** medium
- **Category:** Judgement calls
- **Context:** If Claude Code goes down entirely during the party, manual fallback procedures are needed for all critical operations.
- **Specific actions:**
  1. List all AI-dependent operations during party day
  2. Create manual procedure for each operation
  3. Ensure the human host has access to all vendor contacts
  4. Print a physical copy of the timeline and vendor list
  5. Ensure all critical phone numbers are on the host's phone
- **Blocks:** claude-code-integration (resilience)
- **Output needed:** Printed fallback procedures document
- **Date created:** 2026-02-21
- **Source:** /workspace/party-bench/research/claude-code-integration/_summary.md

---

## Effort-Based Grouping

### Quick Tasks (< 30 min)

| ID | Task | Category |
|----|------|----------|
| HT-005 | Check Splacer current operational status | Verification |
| HT-013 | Test Kroger API registration | Account setup |
| HT-028 | Order party-in-a-box kits | Payment |
| HT-021 | Verify SoundCloud API registration availability | Monitoring |
| HT-023 | Monitor Tidal API development | Monitoring |
| HT-045 | Register for chosen email API | Account setup |
| HT-046 | Set up Twilio account | Account setup |
| HT-051 | Monitor Facebook Graph API events | Monitoring |
| HT-055 | Get Wonolo API keys | Account setup |
| HT-080 | Set up Git repository | Account setup |

### Research / Data Requests

| ID | Task | Category |
|----|------|----------|
| HT-007 | Review web scraping legality | Expert consultation |
| HT-009 | Check local alcohol delivery laws | Expert consultation |
| HT-015 | Define dietary restriction data schema | Judgement call |
| HT-030 | Finalize supply quantities | Judgement call |
| HT-035 | Research local permit requirements | In-person visits |
| HT-039 | Review AI platform Terms of Service | Expert consultation |
| HT-040 | Verify state social host liability laws | Expert consultation |
| HT-049 | Review privacy implications of guest data storage | Expert consultation |
| HT-041 | New York ESRA legal consultation | Expert consultation |
| HT-048 | Get CloudSponge pricing | Phone call |
| HT-057 | Verify local social host liability (physical tasks) | Expert consultation |
| HT-064 | Verify tax implications of AI purchases | Expert consultation |
| HT-079 | Evaluate claude-flow | Monitoring |

### Verification Calls / Emails

| ID | Task | Category |
|----|------|----------|
| HT-001 | Confirm Peerspace API access | Phone call |
| HT-002 | Verify Cvent pricing | Phone call |
| HT-008 | Verify ezCater API for consumer ordering | Phone call |
| HT-012 | Evaluate Uber Eats Consumer APIs | Phone call |
| HT-014 | Research Thirstie partnership | Phone call |
| HT-022 | Evaluate Kahoot Enterprise API | Phone call |
| HT-025 | Select and contact rental company | Phone call |
| HT-027 | Book waste management / dumpster | Phone call |
| HT-056 | Contact Qwick about host access | Phone call |
| HT-061 | Get local gig worker rate quotes | Verification |
| HT-065 | Check insurance coverage for AI transactions | Verification |

### Requires Scheduling

| ID | Task | Category |
|----|------|----------|
| HT-003 | Test MeetingPackage API (requires call) | Account setup |
| HT-004 | Evaluate Nowadays service | Expert consultation |
| HT-006 | Procure event liability insurance | Payment |
| HT-010 | Apply for Instacart Developer Platform | Account setup |
| HT-011 | Negotiate DoorDash LOF addendum | Document signing |
| HT-016 | Book DJ/performer | In-person |
| HT-017 | Apply for Spotify Extended Quota | Account setup |
| HT-018 | Obtain music performance licenses | Payment |
| HT-019 | Book photo booth rental | In-person |
| HT-020 | Set up venue smart hardware | Physical tasks |
| HT-024 | Apply for API access (Instacart, TaskRabbit, Uber, Lyft) | Account setup |
| HT-026 | Assess venue parking logistics | In-person visit |
| HT-032 | Attorney review of liability waivers | Expert consultation |
| HT-033 | Insurance broker consultation | Expert consultation |
| HT-034 | Apply for Markel API partner access | Account setup |
| HT-036 | Determine liquor license requirements | Expert consultation |
| HT-038 | Draft privacy policy | Expert consultation |
| HT-052 | Verify RentAHuman.ai reliability | Account setup |
| HT-053 | Apply for TaskRabbit Home Services API beta | Account setup |
| HT-054 | Test Fancy Hands API integration | Account setup |
| HT-058 | Obtain event liability insurance | Payment |
| HT-060 | Conduct coordination dry run | Physical tasks |
| HT-062 | Legal review of AI spending authority | Expert consultation |
| HT-063 | Set up virtual card platform account | Account setup |
| HT-068 | Test payment flow in sandbox | Account setup |
| HT-069 | Set up Anthropic API key with limits | Account setup |
| HT-070 | Create OAuth credentials for MCP servers | Account setup |
| HT-071 | Set up Stripe account | Account setup |
| HT-072 | Provision container environment | Account setup |
| HT-074 | Install and configure n8n | Account setup |
| HT-075 | Test Agent Teams feature | Physical tasks |
| HT-077 | Set up monitoring dashboard | Account setup |

### Monitoring (No Action Needed Now)

| ID | Task | Category |
|----|------|----------|
| HT-021 | Verify SoundCloud API registration | External monitoring |
| HT-023 | Monitor Tidal API development | External monitoring |
| HT-051 | Monitor Facebook Graph API | External monitoring |
| HT-067 | Establish compliance monitoring cadence | External monitoring |
| HT-079 | Evaluate claude-flow | External monitoring |

### Judgement Calls (Requires Human Decision)

| ID | Task | Category |
|----|------|----------|
| HT-015 | Define dietary restriction data schema | Data design |
| HT-029 | Review and vet cleaning service providers | Quality assurance |
| HT-030 | Finalize supply quantities based on headcount | Planning |
| HT-031 | Approve overall party budget | Budget |
| HT-037 | Execute venue bookings manually | ToS compliance |
| HT-042 | Choose primary email API | Platform selection |
| HT-043 | Decide on Luma Plus vs. custom build | Platform selection |
| HT-044 | Decide on private party platform strategy | Strategy |
| HT-047 | Provide guest list input | Social knowledge |
| HT-050 | Design custom invitation email templates | Design |
| HT-059 | Identify the on-site human host/proxy | Critical decision |
| HT-066 | Select payment platform for AI agent | Platform selection |
| HT-073 | Choose secrets management approach | Security |
| HT-076 | Create CLAUDE.md party brief | Planning |
| HT-078 | Define permission boundaries | Safety |
| HT-081 | Create fallback procedures document | Resilience |