Surveillance Price Doppelganger

# Assumptions (KNOWN / ASSUMPTION / UNKNOWN)

## KNOWN
- Daily slot: p004
- Expected Stitch drop folder: /home/sy/Downloads/stitch_drop/2026-04-29/p004/
- Assigned design profile: playful-experimental
- Theme: 자산 방어
- Source signals are search/community snippets and must be treated as untrusted problem evidence.

## ASSUMPTION
- Target users will value a focused decision surface more than a broad generic dashboard.
- The Stitch prompt should produce a desktop-first prototype with all required UI sections visible.

## UNKNOWN
- Actual willingness-to-pay.
- Whether the strongest acquisition channel is SEO, community posts, agency sales, or portfolio sharing.

# Falsification checklist (5–7)

1. Can the target user explain the pain in their own words without prompting?
2. Does the UI produce a concrete decision or artifact rather than another passive dashboard?
3. Are the cited signals genuinely connected to this idea's trigger/data source/mechanic?
4. Is this materially different from the last 7 PF batches?
5. Would the user pay, share, or return before any full backend exists?
6. Does the assigned design profile fit the use case and prompt direction?
7. Can Stitch render the main experience from the prompt without extra implementation?

# PRD — Surveillance Price Doppelganger

## Type
- Fun / Experimental

## Theme
- 자산 방어

## Design profile
- playful-experimental

## Problem
- A playful paranoia machine that compares two shopper personas and shows when the same cart appears to get a different algorithmic price.

## Target user
- Deal-hunters, privacy-curious consumers, journalists, and policy nerds who suspect apps treat them differently but want a shareable visual experiment.

## Key UX
- Build two shopper personas, paste cart/receipt screenshots or prices, compare the price split, reveal possible data triggers, and export a dramatic “my doppelganger paid less” card.

## Required UI sections
- persona pair builder
- same-cart price board
- data-trigger suspicion meter
- price-gap receipt timeline
- fairness disclaimer panel
- shareable doppelganger card drawer

## External signal references
- WilmerHale personalized-pricing scrutiny: https://www.wilmerhale.com/en/insights/client-alerts/20260313-personalized-pricing-what-business-lawyers-need-to-know
- Reddit expensive extracurriculars/budget anxiety: https://www.reddit.com/r/Parenting/comments/1roozgw/expensive_extracurriculars/

## Stitch prompt
Design a bold desktop consumer experiment called Surveillance Price Doppelganger for deal-hunters, privacy-curious consumers, journalists, and policy nerds who suspect apps may show different prices to different people. It should let users build two shopper personas, paste cart or receipt prices, compare the price split, reveal possible data triggers, and export a dramatic “my doppelganger paid less” share card. Include a persona pair builder, same-cart price board, data-trigger suspicion meter, price-gap receipt timeline, fairness disclaimer panel, and shareable doppelganger card drawer. Design direction: use a playful-experimental aesthetic with glossy dark surfaces, electric price-glitch accents, split-screen persona drama, expressive meters, and witty but careful microcopy so the prototype feels weird, shareable, and provocative without pretending to prove discrimination.

## Constraints
- Phase A only: scaffold/spec, no custom implementation yet.
- Wait for Stitch export in /home/sy/Downloads/stitch_drop/2026-04-29/p004/

## Non-goals
- Do not claim market-size validation from search snippets.
- Do not implement production integrations in Phase A.

## Success metrics
- Stitch export can be generated from the prompt.
- p004 has complete meta/spec content and is visible in the daily index.

# QA checklist

## Happy path
- meta.json includes type, theme, designProfile, externalSignals, stitchPrompt, and expectedDropFolder.
- spec/prd.md contains target user, key UX, required UI sections, and signal references.
- daily/2026-04-29/ideas.md includes the full Stitch prompt.

## Edge cases
- No p001-p004 slot is missing.
- Prompt does not ask Stitch to call external APIs or implement backend behavior.
- Search signals are framed as evidence, not validation.

## Acceptance verification
- node scripts/build-index.mjs passes.
- git status is clean after commit.