Back to corpus
architecturetechnical paper candidatescore 58

Stage 4: FORGE -- Final Creative Architecture

FirstDate is a production-first reality dating series that treats transparency as its format, not its liability. Three asymmetric roles (Host, Applicant, Viewer) orbit a 10-week seasonal arc set in Miami, where every consent ritual, every sponsor deal, every casting decision is designed to be seen. The app is not a dating platform with a show bolted on. It is a show management system whose public membrane happens to look like a dating app. Swiping is a personality quiz, not a match engine. The episode is the produc

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

FirstDate is a production-first reality dating series that treats transparency as its format, not its liability. Three asymmetric roles (Host, Applicant, Viewer) orbit a 10-week seasonal arc set in Miami, where every consent ritual, every sponsor deal, every casting decision is designed to be seen. The app is not a dating platform with a show bolted on. It is a show management system whose public membrane happens to look like a dating app. Swiping is a personality quiz, not a match engine. The episode is the product. The date is the shoot. The restaurant is the set. Everything else serves the content flywheel. | Tab | Primary View | Actions | |-----|-------------|---------| | Inbox | ApplicationInboxView | Review, shortlist, select, pass applications. Assign talent to episode. | | Pipeline | EpisodePipelineView + DealsSection | Kanban episodes across 6 statuses. Manage deals (pitch_stage). View per-episode financials inline. | | Schedule | ProductionCalendarView | Set shoot dates, detect conflicts, view episode timeline. | | Ledger | FinancialsView | P&L by episode, breakeven projection, add income/expense, receipt upload, wardrobe cost tracking. | | Studio | StudioView | Pre-shoot checklist (restaurant confirmed, talent confirmed, consent signed, outfit logged, equipment packed). | **Additional navigation** (pushed from tabs, not tab items): - EpisodeDetailView (from Pipeline) - ApplicationDetailView (from Inbox) - ConsentCaptureSheet (from Studio) - WardrobeManagerView (from Ledger) - OutfitLogView (from Studio) - ContentScriptView (from Pipeline/EpisodeDetail) - MiamiMapView (from Schedule, toolbar button) | Tab | Primary View | Actions | |-----|-------------|---------| | Series | SeriesView | Watch published episodes with BehindTheGlass overlay. Browse season archive. | | Apply | ApplicationWizardView | 4-step wizard (About You, Story, Look + Video Selfie, Consent). Edit existing application. | | Spots | RestaurantsView + MiamiMapView | Browse curated Miami restaurants, neighborhood filter, map pins. | | Status | ApplicationStatusView | Track application through pipeline. See selection notification. | **Data access**: Own profile, own application, published episodes, all restaurants, own matches/messages.

Promotion decision

What has to happen next

Promote into a technical note or architecture paper with implementation anchors.

Why this is not always a full paper yet

Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.