Lemonade Stand Tycoon

Lemonade Stand Tycoon Brainstorming Analysis

Issue: ROB-26 Artifact: /srv/http/roblox/_bmad-output/planning-artifacts/brainstorm-lst.md Date: 2026-05-18 Workflow: /bmad-brainstorming, applied headlessly for OD-018 cascade step 1

Source Inputs

Directive material used:

• /srv/http/_hq/projects/project-roblox/OD-018-pivot-to-lemonade-stand-tycoon.md
• /srv/http/roblox/_bmad-output/planning-artifacts/brainstorm-pst.md

Canon material used:

• /srv/http/_hq/projects/project-roblox/BRAND-CANON.md
• /srv/http/_hq/projects/project-roblox/COPY-VOICE.md
• /srv/http/_hq/projects/project-roblox/ASSET-LIBRARY.md
• /srv/http/_hq/projects/project-roblox/JOURNEY-STORY-CANON.md

BMAD Execution Notes

This pass rewrites Build #1 brainstorming canon. The current project story is that Lemonade Stand Tycoon won during brainstorming after the twins reviewed the top tycoon concept.

No domain research, market research, product brief, storyboard, asset generation, site publishing, paid provider calls, or public URL changes were performed in this issue.

The local BMAD manifest names /bmad-brainstorming, but the full skill body files are not present in this checkout. This artifact follows the available BMAD brainstorming output pattern from brainstorm-pst.md and applies the same internal ideation structure to the LST rewrite.

Recommended brainstorming lenses applied inside this pass:

1. Stakeholder Round Table
2. User Persona Focus Group
3. SCAMPER Method
4. Pre-mortem Analysis
5. Expand or Contract for Audience

Brainstorm-Stage Twin Pivot

Canonical brainstorm-stage event:

The twins liked the tycoon loop. They did not want Pet Salon Tycoon as the first build because the theme felt too girly. Dad and Claude used that feedback immediately and moved the winning concept to Lemonade Stand Tycoon.

Twin-layer wording for later customer surfaces:

• "We liked the tycoon part."
• "We did not want the pet salon first."
• "Then Lemonade Stand Tycoon sounded way more fun."
• "Now our shop sells drinks, upgrades, and bigger stands."

Parent-layer explanation:

The useful signal was not that the tycoon structure failed. The loop still worked: buy something, make something, serve customers, earn coins, and upgrade. The theme missed the twins' taste, so the brainstorm moved to a stand-business fantasy they recognized faster.

Canon Lock

The core LST promise:

> Buy lemons, make lemonade, serve customers, upgrade the stand, and grow bigger every day.

This is the shortest canon sentence for Lemonade Stand Tycoon. Any feature that does not reinforce that sentence should be deferred, cut, or reframed.

Canonical LST video grammar comes from OD-018:

• Buy lemons.
• Squeeze and pour.
• Set price.
• Serve customers.
• Earn coins.
• Upgrade stand.
• React to weather.
• Repeat bigger.

Forbidden drift:

• No generic idle factory where lemonade is only decoration.
• No pet-salon service fantasy as the active product.
• No tower-defense lanes, enemy waves, combat numbers, or boss framing.
• No food-realism register that stops reading as Roblox.
• No adult business simulator language in twin-facing copy.
• No paid random item pressure as a core progress requirement.
• No narrative that preserves a late project pivot; the pivot belongs at brainstorming.

Winning Concept

Winner: Lemonade Stand Tycoon.

Why it wins:

• The twins recognized the fantasy quickly.
• The tycoon loop stays simple and visible.
• The first play loop can close in under 30 seconds.
• The stand upgrades are screen-readable on mobile.
• Weather creates kid-clear variety without needing combat.
• Advertising adds a playful growth lever.
• Lemon varieties and recipe cards add collection depth.

First 30-second loop:

1. Player buys lemons.
2. Player taps the squeezer.
3. Pitcher fills.
4. Price sign flips to a simple starter price.
5. Customer walks up.
6. Player serves a cup.
7. Coin counter pops.
8. Upgrade button lights.
9. Stand changes from crate table to painted mini-stand.
10. Next customer arrives faster.

Screenshot moment:

The player stands beside a freshly upgraded yellow-and-blue lemonade cart. A customer holds a cup, coins pop above the counter, the weather widget shows sunny, and the upgrade button glows for the next stand tier.

Twin-layer line:

• "We can show friends our first real lemonade stand."

Simulator-Tycoon Canon

LST should feel like a Roblox tycoon with an active service loop, not a reskinned cash dropper.

Core loop:

1. Player checks the day and weather.
2. Player buys lemons and ice.
3. Player squeezes, mixes, and pours a batch.
4. Player sets a kid-readable price.
5. Customers spawn from the sidewalk.
6. Player serves cups before demand cools down.
7. Coins, tips, and stand-star progress appear.
8. Upgrade button lights up.
9. Stand, sign, menu, or helper visibly improves.
10. The next day starts with a stronger stand.

MVP loop constraints:

• One sunny sidewalk or front-yard map.
• One starter stand.
• One lemon-buy action.
• One squeeze-and-pour station.
• One price sign.
• One customer queue.
• One coin and stand-star reward loop.
• One visible stand upgrade path.
• One weather widget with sunny, cloudy, rain, and heatwave states.
• One ad surface, such as a flyer board or sidewalk sign.

Progression should be layered inside one map:

• Stand upgrades: crate table, wood cart, painted kiosk, branded mini-shop.
• Recipe upgrades: classic, pink, strawberry, lavender, extra-ice.
• Supply upgrades: better lemons, faster pitcher, larger ice cooler.
• Customer upgrades: more visitor types, bigger patience bar, larger tips.
• Advertising upgrades: hand sign, flyers, billboard, local post board.
• Weather prep: umbrella cover, ice storage, rain day prep, heatwave surge.
• Collection surface: Recipe Book and Lemon Variety Board.

Lemonade Loop Primitives

Treat the lemonade loop as a reusable state pipeline:

DayStart
  -> WeatherRead
  -> SupplyBuy
  -> BatchMake
  -> PriceSet
  -> CustomerServe
  -> RewardEmit
  -> UpgradePrompt
  -> StandChange
  -> NextDay

Implementation primitives:

• DayState: day number, weather, demand modifier, prep hint.
• SupplyDefinition: lemons, ice, cups, sugar, recipe modifier.
• RecipeDefinition: id, color, taste tag, unlock tier, customer preference.
• BatchState: empty, squeezed, mixed, chilled, ready, sold out.
• PriceSign: starter, fair, pricey, surge, discount.
• CustomerArchetype: kid, parent, runner, dog-walker, mail-carrier, tourist.
• DemandSignal: sunny rush, cloudy slow, rain close-prep, heatwave surge.
• RewardEmit: coins, tips, stand stars, recipe progress, ad meter.
• UpgradeDefinition: stand tier, tool speed, storage size, sign reach, helper.

Visual primitives:

• Lemon crates, rolling lemons, pitcher fill, cup stack, chalkboard price.
• Coin pop, tip jar bounce, stand-star sparkle, upgrade-button glow.
• Sunny park path, sidewalk queue, R15 customer avatars, mobile-safe HUD.
• Weather widget, day counter, coin counter, price tag, upgrade popup.
• Before/after stand tiers that read at thumbnail size.

Audio primitives:

• Short twin-voice lines on high-value beats, not constant chatter.
• Pour sound, coin ding, customer sip, chalk sign flip, sunny day chime.
• Weather alert sting when heatwave, rain, or cloudy slowdown arrives.
• Voice clips must resolve to pre-uploaded, moderated Roblox audio assets with text fallback before gameplay or capture scripts reference them.

Sample twin-facing lines:

• "Sun is out. People want lemonade."
• "We need more ice."
• "That price looks fair."
• "Customer served. Coins popped."
• "Upgrade the stand now."

Customer-Reaction Beats

The customer reaction is the payoff surface. It proves the loop worked.

Reaction beat pattern:

1. Customer approaches with a visible want bubble.
2. Player serves a cup.
3. Customer drinks for one beat.
4. Face and body animation change.
5. Tip jar or coin pop lands.
6. Stand-star progress moves.
7. Upgrade prompt appears after the reaction, not before.

Reaction archetypes:

• Refreshed: "That hit the spot."
• Surprised: "Pink lemonade? Nice."
• Loyal: "I am coming back tomorrow."
• Heatwave: "Extra ice saved me."
• Rain prep: "Smart umbrella."
• Price-sensitive: "Fair price. Good cup."

Customer reactions should vary by weather, price, recipe, and queue wait. Avoid one generic cheer animation.

Weather And Advertising Canon

Weather should change decisions without becoming a simulation spreadsheet.

Weather states:

• Sunny: normal demand, clean tutorial day.
• Cloudy: slower demand, good day for upgrades.
• Rain: stand closes or prep mode starts; player buys supplies and improves cover.
• Heatwave: demand surge, ice pressure, big coin chance.

Advertising should be visible and playful:

• Sidewalk sign pulls nearby customers.
• Flyers increase spawn rate for one day.
• Billboard creates a short rush.
• Local post board gives a small customer boost.

Advertising is not social-media pressure. It is a stand-growth lever shown with props, signs, and customer movement.

Monetization And Policy Posture

LST can support purchases later, but the brainstorm canon keeps the first loop earnable.

Allowed future surfaces:

• Stand cosmetic skins.
• Special sign styles.
• Extra helper outfits.
• Faster restock convenience.
• Recipe-card collection with clear odds, free earn path, and policy controls if random paid items ever appear.

Disallowed future surfaces:

• Paid-only access to core lemonade making.
• Paid-only first stand upgrade.
• Random paid items without odds and region policy controls.
• Robux framed as a reward emitted by gameplay.
• Failure pressure that pushes a purchase after a bad day.

Gameplay counters are fictional in-experience currencies and progress data. Robux remains platform purchase context only.

Roblox-Fidelity Lenses

These lenses must be visible early, not discovered during video production.

Art And World

The world should read as blocky Roblox-stylized at first glance.

Required cues:

• Sunny sidewalk, park, or front-yard map.
• Low-poly props with chunky silhouettes.
• Bright stand tiers with simple materials.
• Lemon crates, chalkboard signs, pitchers, cups, coins.
• Thumbnail-readable color contrast.

Avoid:

• Photoreal fruit still life.
• Generic mobile-game storefront art.
• Soft pastel illustration that could be any kids' app.

Avatars

The main player and customers should read as Roblox avatars.

Required cues:

• R15 blocky proportions.
• Roblox face grammar.
• Layered items or simple accessories.
• Customer NPCs who approach, pause, react, and leave.
• Dad, Twin A, and Twin B only when the surface is project-story content, using BRAND-CANON likeness paths.

Avoid:

• Hand-painted mascot customers.
• Photoreal kids.
• Characters that drift from the approved family canon.

UI And HUD Chrome

HUD chrome makes the game feel real.

Required cues:

• Coin counter.
• Day counter.
• Weather widget.
• Price sign or price popup.
• Upgrade button.
• Customer want bubble.
• Recipe card or stand-tier card.
• Optional mobile-screen frame for video beats.

At least most video shots should show some gameplay chrome unless the shot is a deliberate hero moment.

Visible Gameplay Loop

The loop must be nameable by a cold 6-10-year-old viewer.

Required order:

1. Buy lemons.
2. Squeeze and pour.
3. Set price.
4. Serve customer.
5. Earn coins.
6. Upgrade stand.
7. Weather event.
8. Repeat bigger.

If a shot could be mistaken for a generic lemonade picture, add UI, avatar action, or a before/after stand change.

Success Criteria Check

OD-013 section 2 success criteria:

1. Twins are excited to share with friends. Recess-energy. Screenshot-and-send. Would a 10yo actually take this to school and brag about it.
2. The game feels real. Production polish. Not vapourware. Visual consistency, audio that lands, mechanic that closes a loop. A stranger watching the commercial does not register "AI slop" or "demo".
3. The twins are excited. Creative agency, build literacy, ship-something achievement. The "fun parts" gap stays load-bearing (per OD-002 LEARNING-first rubric).

LST evaluation:

SCAMPER Highlights Incorporated

Substitute:

• Replace pet grooming stations with lemonade-making stations.
• Replace salon tips with stand coins, tips, and stand stars.
• Replace pet reveals with stand-tier and recipe reveals.

Combine:

• Combine tycoon upgrades with weather decisions.
• Combine recipe collection with lemon varieties.
• Combine customer reactions with price and weather feedback.

Adapt:

• Adapt service-ticket clarity into customer want bubbles.
• Adapt store-upgrade loops into stand-tier changes.
• Adapt collection-game joy into a Recipe Book.

Modify:

• Make the first loop close in under 30 seconds.
• Make every upgrade visible on the stand model.
• Make weather readable from one small HUD widget.

Put to another use:

• Use rain days as prep days.
• Use advertising as a visible customer-spawn lever.
• Use a chalkboard as both price sign and tutorial surface.

Eliminate:

• Remove pet-salon theme as the active Build #1 direction.
• Remove combat grammar.
• Remove spreadsheet economy detail from twin-facing surfaces.
• Remove any Robux-as-gameplay-reward implication.

Reverse:

• Start with selling one cup, then unlock supply strategy.
• Let weather teach upgrades instead of hiding upgrades in menus.
• Let twins' feedback choose the theme before adult optimization.

Tier-2 Vault Entry: Pet Salon Tycoon

Pet Salon Tycoon remains a deliberate vault concept, not the active product.

Demotion rationale:

• The twins liked the tycoon loop.
• The pet-salon theme missed their taste for Build #1.
• The concept still has useful loop lessons: service queue, before/after payoff, customer reaction, upgrade rhythm.
• It may return later if the audience or build order changes.

Vault summary:

> Pet Salon Tycoon: A cozy pet-service tycoon where messy pets become shiny and customers react. Demoted after the twins chose Lemonade Stand Tycoon as the stronger first build.

Do not use PST as the Build #1 product name in current-state planning docs after this brainstorm handoff.

Priority Idea Set

Highest-value ideas for LST build #1:

1. First cup sold in under 30 seconds.
2. Buy lemons, squeeze, pour, sell, upgrade loop.
3. Starter stand with obvious before/after upgrade states.
4. Sunny sidewalk or front-yard Roblox map.
5. R15 player avatar and customer NPC queue.
6. Weather widget with sunny, cloudy, rain, and heatwave.
7. Price sign that changes customer response.
8. Recipe Book for classic, pink, strawberry, lavender, extra-ice.
9. Lemon Variety Board for collection depth.
10. Advertising props that visibly increase customer flow.
11. Tip jar, coin counter, day counter, stand-star meter.
12. Customer reaction animations tied to recipe, price, and weather.
13. Deterministic capture beats for later video work.
14. Reference-image-driven asset set for avatars, stand tiers, lemons, props, weather, and HUD.
15. Twin-authored jokes, recipe names, and stand names.

Next Handoff

The next OD-018 cascade steps should convert this brainstorm into:

• RobloxSME audit comments on LST brainstorm canon.
• Domain research on lemonade-stand economy UX patterns and Roblox tycoon visual grammar.
• Market research on actual Roblox tycoon comparables and shipped loops.
• A product brief that treats LST as Build #1 from the start.
• Updated canon and asset-library work that replaces PST product references with LST references.

Amendment Log

Initial ROB-26 LST rewrite:

• Made Lemonade Stand Tycoon the winning Build #1 brainstorm concept.
• Placed the twins-feedback pivot near the top as a brainstorm-stage event.
• Preserved Pet Salon Tycoon only as a demoted vault concept.
• Added OD-013 success-criteria evaluation.
• Added early Roblox-fidelity lenses for art/world, avatars, UI/HUD chrome, and visible gameplay loop.
• Preserved OD-018 history-rewrite framing by not carrying Phase 8 as the public narrative pivot.

Product Brief: Lemonade Stand Tycoon

Issue: ROB-31 Date: 2026-05-18 Workflow: /bmad-product-brief Output owner: ProductManager OD-018 cascade step: 5

Canon Used

• /srv/http/_hq/projects/project-roblox/OD-018-pivot-to-lemonade-stand-tycoon.md: LST is Build #1; the twins-feedback pivot is a brainstorm-stage event.
• /srv/http/_hq/projects/project-roblox/BRAND-CANON.md: Dad, Twin A, Twin B, Claude, and Crew likeness discipline.
• /srv/http/_hq/projects/project-roblox/COPY-VOICE.md: TWIN layer for kid-facing promise lines; parent layer for operator-readable explanation.
• /srv/http/_hq/projects/project-roblox/ASSET-LIBRARY.md: library-path discipline; downstream LST asset work must create concrete paths before visual references are cited.
• /srv/http/_hq/projects/project-roblox/JOURNEY-STORY-CANON.md: the public story is a learning story with three reading layers.

BMAD Execution Notes

Workflow run: /bmad-product-brief.

Inputs synthesized:

• /srv/http/roblox/_bmad-output/planning-artifacts/brainstorm-lst.md
• /srv/http/roblox/_bmad-output/planning-artifacts/domain-research.md
• /srv/http/roblox/_bmad-output/planning-artifacts/market-research.md
• /srv/http/_hq/projects/project-roblox/OD-018-pivot-to-lemonade-stand-tycoon.md
• /srv/http/_hq/projects/project-roblox/BRAND-CANON.md
• /srv/http/_hq/projects/project-roblox/COPY-VOICE.md
• /srv/http/_hq/projects/project-roblox/ASSET-LIBRARY.md
• /srv/http/_hq/projects/project-roblox/JOURNEY-STORY-CANON.md

Advanced elicitations applied through product-brief synthesis:

1. Stakeholder Round Table.
2. User Persona Focus Group.
3. SCAMPER Method.
4. Pre-mortem Analysis.
5. Expand or Contract for Audience.

Party-mode findings are folded into the brief as product decisions, risks, scope cuts, and downstream recommendations rather than preserved as transcript.

This issue did not run PRD, storyboard, canon rewrites, asset generation, site publishing, video production, paid provider calls, or public URL changes.

Canonical Build Story

Lemonade Stand Tycoon is Build #1 from the start of the current project narrative.

At the brainstorming stage, Dad showed the strongest tycoon concept to Twin A and Twin B. The twins liked the tycoon loop, but they did not want Pet Salon Tycoon first because the theme felt too girly. Dad and Claude used that feedback immediately and moved the winning concept to Lemonade Stand Tycoon.

Pet Salon Tycoon is no longer the first build. It is a tier-2 vault concept that may return later if the family wants it.

Twin-layer wording for customer surfaces:

We liked the tycoon part.

We wanted lemonade first.

Now we sell cups, earn coins, and upgrade.

Our stand gets bigger every day.

Product Promise

Lemonade Stand Tycoon is a Roblox simulator-tycoon for 6-10-year-old players. The player buys lemons, makes lemonade, serves customers, earns coins, upgrades a stand, and handles simple weather changes.

The first build should feel like a small playable Roblox business, not a generic idle factory and not a video-only concept. The fantasy is visible at phone-screen size: lemons, pitcher, cups, price sign, customer queue, coin pop, weather widget, and a bigger stand.

Shortest canon promise:

> Buy lemons, make lemonade, serve customers, upgrade the stand, and grow bigger every day.

Twin promise:

We sell our first cup and upgrade our stand.

Friends can see our bigger stand right away.

Problem

The twins liked the tycoon shape but rejected the first pet-salon theme. The product problem is not "find any tycoon"; it is "make the tycoon loop match the twins' taste and read instantly as Roblox."

Lemonade solves the recognition problem. A kid can understand the stand fantasy in one second: lemons become drinks, customers pay coins, and the stand grows. That clarity gives Dad and the team a conservative Build #1 that can still feel real.

For Dad, the build also needs to prove the family can ship one polished loop with visible gameplay, not a pile of unfinished systems. A focused loop beats three shallow loops.

Audience

Primary players: 6-10-year-old Roblox players who like tycoons, simulator loops, visible upgrades, bright props, and showing friends what they built.

Primary builders: Twin A and Twin B. They contribute stand taste, recipe ideas, customer reactions, weather jokes, and the "would we show this to friends?" read.

Support role: Dad guides production and protects scope. Dad does not replace the twins' creative surface.

Parent-readable audience: family and friends who want to see how the twins' feedback shaped a real product decision.

Genre And Market Position

Genre: single-player Roblox simulator-tycoon with an active stand-service loop.

Closest Roblox reference patterns from market research:

• Restaurant Tycoon 3: visible service sequence, customers, bills, and upgrades.
• Welcome to Bloxburg: grounded job fantasy where earning money feels recognizable.
• Pet Simulator 99: collection clarity, icons, and constant progress feedback.
• Grow a Garden: simple resource cycle and shareable "look what I built" payoff.
• Existing lemonade tycoons: validated stand theme, supply loop, customers, workers, and upgrades.

Differentiation:

LST keeps the tycoon loop the twins liked while replacing the rejected pet-salon fantasy with a stand-business fantasy they recognized faster. Build #1 should feel more polished, more Roblox-readable, and more loop-visible than a static lemonade cash-dropper.

First Playable Loop

The first playable and video promise is concrete:

1. Buy lemons.
2. Squeeze and pour.
3. Set price.
4. Serve a customer.
5. Earn coins.
6. Upgrade the stand.
7. React to weather.
8. Repeat bigger.

The first loop should close in under 30 seconds:

1. Player taps Buy Lemons.
2. Lemon crate fills on the counter.
3. Player taps or holds Squeeze.
4. Pitcher fills with bright lemonade.
5. Player flips the price sign to a starter price.
6. One customer walks up with a want bubble.
7. Player serves one cup.
8. Customer drinks and reacts.
9. Coins pop over the stand.
10. Upgrade Stand glows.
11. The stand changes from crate table to painted starter stand.

Screenshot Moment

The friend-share moment happens immediately after the first visible stand upgrade.

Screenshot composition:

Painted lemonade stand + customer holding cup + coin pop +
sunny weather widget + glowing Upgrade Stand button.

This is the moment the twins can show a friend. The screenshot should include the stand, customer, cup, coin feedback, HUD weather, and next upgrade affordance. It should not be a cropped beauty render, a balance screen, or a generated image upload.

Twin-layer candidate line:

We sold one cup and our stand got bigger.

MVP Scope

Build #1 scope:

• One sunny sidewalk, park, or front-yard map.
• One player stand.
• One stand upgrade path.
• One customer queue.
• One lemon-buy action.
• One squeeze-and-pour station.
• One simple price sign.
• One reward loop: coins plus stand-star progress if needed.
• One primary button that changes by loop beat.
• One weather widget with sunny, cloudy, rain, and heatwave states.
• Simple recipes: classic first, pink or extra-ice as early visible variety if scope allows.
• Customer reactions tied to price, weather, recipe, and wait time.
• Mobile-safe HUD: day, weather, coins, customer want bubble, price sign, and Upgrade Stand.

Out of MVP:

• Multiple maps.
• Multiple stand branches.
• Multiple simultaneous queues.
• Multiplayer.
• Trading.
• Full staff automation.
• Prestige or rebirth.
• Complex recipe math.
• External social posting mechanics.
• Runtime generated voice.
• Runtime screenshot upload or persistence.
• Paid-random core loop.
• Public URL or publish commitments from this brief.

Build #1 Scope Cuts

The game feels real only if one loop is polished. These cuts protect that:

• One map beats three half-built locations.
• One stand path beats a broad upgrade tree.
• One queue beats complex crowd simulation.
• Simple weather beats hidden economy math.
• Simple recipes beat a spreadsheet of ingredients.
• Earned first upgrades beat paid shortcuts.
• Active serving beats passive droppers in the first minute.

Later content can add helpers, flyers, billboards, recipe collections, more locations, offline income, and prestige after the first stand loop proves itself.

Weather Product Contract

Weather changes decisions without becoming a simulation spreadsheet.

MVP weather states:

Rules:

• The first tutorial day is sunny.
• Weather must show in the HUD and world.
• Weather effects should change visible customer behavior.
• Rain should not punish a brand-new player.
• Heatwave should show both opportunity and pressure.

Economy And Monetization Posture

The core loop must be earnable:

• Coins come from in-experience lemonade sales, tips, and progress beats.
• First stand upgrades are earned through play.
• Recipe and lemon variety unlocks improve color, choice, and reactions.
• Paid random items are not part of the Build #1 core loop.
• If future paid random recipe cards or cosmetic crates exist, numerical odds and per-player policy handling are required before spend.
• Do not present Robux as a gameplay reward.

This brief does not authorize paid provider calls, video generation, site publishing, public URL changes, or canon amendments.

Roblox-Fidelity Acceptance Lenses

Downstream PRD, storyboard, asset, and review work must evaluate the product through four Roblox-fidelity axes:

1. Art/world. The map, props, and stand tiers must read as blocky Roblox-stylized space, not generic CGI, photoreal fruit, or flat app art.
2. Avatars. Player and customer NPCs must read as Roblox R15 or R6 avatars with recognizable Roblox face grammar and blocky proportions.
3. UI/HUD chrome. Coin counter, day counter, weather widget, price sign, customer want bubble, mobile frame, and Upgrade Stand affordance must be visible in key beats.
4. Gameplay-loop visibility. A kid watching cold must be able to name the loop: buy lemons, squeeze and pour, set price, serve, earn coins, upgrade, weather, repeat bigger.

If a downstream artifact hides the interface, removes the customer, skips a loop verb, or shows generic lemonade art without Roblox avatars, it fails this lens.

Success Criteria

Operator acceptance lens:

1. Twins are excited to share with friends.
2. The game feels real.
3. The twins are excited.

OD-013 §2 success criteria, cited verbatim:

1. Twins are excited to share with friends. Recess-energy. Screenshot-and-send. Would a 10yo actually take this to school and brag about it.
2. The game feels real. Production polish. Not vapourware. Visual consistency, audio that lands, mechanic that closes a loop. A stranger watching the commercial does not register "AI slop" or "demo".
3. The twins are excited. Creative agency, build literacy, ship-something achievement. The "fun parts" gap stays load-bearing (per OD-002 LEARNING-first rubric).

Direct product evaluation:

• Share with friends: the screenshot moment is the first painted stand upgrade with customer, cup, coin pop, sunny widget, and glowing Upgrade Stand.
• Game feels real: the first loop closes in under 30 seconds with a visible prop, avatar action, and HUD response for every verb.
• Twins are excited: the pivot visibly proves their feedback changed Build #1, and their next creative inputs shape recipes, stand look, customer reactions, and weather jokes.

Twin Feedback As Product Requirement

The brainstorm-stage pivot is not a side note. It is the first product requirement.

Twin A and Twin B taught the project this:

• The tycoon loop worked.
• The first theme did not fit.
• Lemonade felt more fun to show.
• Stand growth is easier to brag about.

Product requirements from that signal:

• Show stand growth early.
• Keep the first sale fast.
• Make the customer reaction visible.
• Keep the UI readable on mobile.
• Let the twins name and shape fun details.
• Treat Pet Salon Tycoon only as a tier-2 vault idea.

Asset And Canon Discipline

Current canon files remain the source of truth. This brief does not amend them.

Required discipline for downstream LST work:

• Characters use BRAND-CANON.md names and likenesses only.
• Customer-facing copy follows COPY-VOICE.md.
• Public story work follows JOURNEY-STORY-CANON.md.
• Concrete visual references must use ASSET-LIBRARY.md paths once LST assets are created.
• Do not invent prose-only references when a library path exists.
• The current asset library still contains PST paths; the LST asset-library rewrite is a later OD-018 cascade step.

Expected downstream LST library families:

• site/assets/library/style-packs/lst-tycoon-sunny-v1/
• site/assets/library/environments/lst-lemonade-stand-v1/
• site/assets/library/props/lemonade-stand/
• site/assets/library/props/lemons/
• site/assets/library/props/customers-park/
• site/assets/library/props/ui-cards/
• site/assets/library/props/vfx/

These are recommendations for the later asset-library rewrite, not artifacts created by this issue.

Risks And Product Decisions

Theme risk: treating LST as a late rescue would violate OD-018. Current product narrative must present LST as Build #1 from the beginning, with the twins-feedback pivot happening at brainstorming.

Loop risk: LST can become a passive cash-dropper if lemonade is only decoration. The first loop must require visible buy, squeeze, price, serve, reward, and upgrade beats.

Scope risk: helpers, extra maps, prestige, recipe depth, and multiplayer can make the build feel bigger on paper and weaker in play. Build #1 cuts to one map, one stand path, one queue, simple weather, and simple recipes.

Roblox-fidelity risk: the prior video failure cannot be fixed by a theme swap alone. Downstream artifacts must show Roblox art/world, Roblox avatars, HUD chrome, and visible gameplay verbs.

Policy risk: paid random items can create compliance and trust problems. The core loop avoids paid random pressure; any future paid random surface requires clear odds and policy gating.

Share risk: a generic screenshot prompt is too vague. The product share moment is deterministic: painted stand, customer cup, coin pop, sunny widget, glowing Upgrade Stand.

Learning risk: Dad or the agent system can accidentally own the creative surface. The product must reserve meaningful twin contribution points: recipes, stand colors, customer jokes, weather reactions, and final "would we show friends?" judgment.

Phase 2 Handoff

The PRD should treat this brief as the product north star:

• Name LST as Build #1 from the beginning.
• Preserve the brainstorm-stage twins-feedback pivot.
• Make the first playable promise explicit: buy lemons, squeeze and pour, set price, serve a customer, earn coins, upgrade stand, react to weather, repeat bigger.
• Keep MVP to one map, one stand path, one queue, simple weather, simple recipes, and no paid-random core loop.
• Turn OD-013 §2 into acceptance checks, not generic KPIs.
• Require the screenshot moment: painted lemonade stand, customer holding cup, coin pop, sunny weather widget, glowing Upgrade Stand.
• Declare the four Roblox-fidelity axes as downstream acceptance lenses: art/world, avatars, UI/HUD chrome, gameplay-loop visibility.
• Preserve family-shared-infra inheritance discipline: consume existing persona/library/style-pack scaffolds once rewritten for LST; contribute LST style-pack, stand-loop DataStore patterns, customer/reaction primitives, and refined twin persona inputs for Build #2.

Definition Of Done For This Brief

• product-brief.md is rewritten for Lemonade Stand Tycoon.
• The brief presents LST as Build #1 from the beginning.
• The twins-feedback pivot is framed as a brainstorm-stage event.
• The first playable loop and screenshot moment are named concretely.
• Build #1 constraints are explicit.
• The four Roblox-fidelity axes are named as downstream acceptance lenses.
• No PRD, storyboard, canon rewrite, asset generation, site publishing, video work, paid provider call, or public URL change is performed in this issue.

Sources

• OD-018 pivot directive: /srv/http/_hq/projects/project-roblox/OD-018-pivot-to-lemonade-stand-tycoon.md
• LST brainstorm: /srv/http/roblox/_bmad-output/planning-artifacts/brainstorm-lst.md
• LST domain research: /srv/http/roblox/_bmad-output/planning-artifacts/domain-research.md
• LST market research: /srv/http/roblox/_bmad-output/planning-artifacts/market-research.md
• Brand canon: /srv/http/_hq/projects/project-roblox/BRAND-CANON.md
• Copy voice canon: /srv/http/_hq/projects/project-roblox/COPY-VOICE.md
• Asset library canon: /srv/http/_hq/projects/project-roblox/ASSET-LIBRARY.md
• Journey story canon: /srv/http/_hq/projects/project-roblox/JOURNEY-STORY-CANON.md
• OD-013 success criteria: /srv/http/_hq/projects/project-roblox/OD-013-autonomous-execution.md

---

stepsCompleted: - activation-context - product-brief-ingested - advanced-elicitations-applied - prd-authored inputDocuments: - /srv/http/hq/projects/project-roblox/OD-018-pivot-to-lemonade-stand-tycoon.md - bmad-output/planning-artifacts/brainstorm-lst.md - bmad-output/planning-artifacts/domain-research.md - bmad-output/planning-artifacts/market-research.md - bmad-output/planning-artifacts/product-brief.md - /srv/http/hq/projects/project-roblox/BRAND-CANON.md - /srv/http/hq/projects/project-roblox/COPY-VOICE.md - /srv/http/hq/projects/project-roblox/ASSET-LIBRARY.md - /srv/http/_hq/projects/project-roblox/JOURNEY-STORY-CANON.md workflowType: prd issue: ROB-33 date: 2026-05-18 author: ProductManager

---

Product Requirements Document - Lemonade Stand Tycoon Build #1

Canon And Workflow Confirmation

Lemonade Stand Tycoon is Build #1 from the beginning of the current project narrative. The twins-feedback pivot is a brainstorm-stage event: Dad showed the top tycoon concept to Twin A and Twin B, the twins liked the tycoon loop, and the project moved to Lemonade Stand Tycoon because the stand fantasy fit them better.

Product brief exists at _bmad-output/planning-artifacts/product-brief.md and is treated as the approved product north star for this PRD. This issue runs only /bmad-prd; it does not run storyboard, canon rewrites, asset generation, site publishing, video work, or implementation story readiness changes.

Canon used in customer-facing requirements:

• /srv/http/_hq/projects/project-roblox/BRAND-CANON.md: Dad, Twin A, Twin B, Claude, and Crew likeness discipline.
• /srv/http/_hq/projects/project-roblox/COPY-VOICE.md: TWIN layer for kid-facing promise lines; PARENT layer for operator-readable explanation.
• /srv/http/_hq/projects/project-roblox/ASSET-LIBRARY.md: concrete visual references resolve through site/assets/library/ once LST paths are created.
• /srv/http/_hq/projects/project-roblox/JOURNEY-STORY-CANON.md: the public story remains a three-layer learning story.
• /srv/http/_hq/projects/project-roblox/OD-018-pivot-to-lemonade-stand-tycoon.md: LST replaces PST as the canonical first build.

BMAD execution notes: /bmad-prd synthesized the approved LST product brief, LST brainstorm, domain research, market research, and OD-018 directive. Advanced elicitation lenses were applied inside synthesis: Stakeholder Round Table, User Persona Focus Group, SCAMPER Method, Pre-mortem Analysis, and Expand or Contract for Audience.

Product Promise

Twin-facing promise, COPY-VOICE Layer 1:

We buy lemons.
We make lemonade.
We serve one customer.
Coins pop up.
Our stand gets bigger.

Parent-facing promise, COPY-VOICE Layer 2:

Lemonade Stand Tycoon is a focused Roblox simulator-tycoon where kids can see a complete business loop: buy lemons, make lemonade, serve customers, earn coins, react to weather, and upgrade the stand.

Shortest product promise:

> Buy lemons, make lemonade, serve customers, upgrade the stand, and grow bigger every day.

Problem

The twins liked the tycoon structure, but the first pet-salon theme did not fit their taste. The product problem is therefore precise: preserve the proven tycoon loop and make the first build instantly recognizable, playable, and worth showing to friends.

Lemonade works because the business fantasy is visible at a glance. A player sees lemons, a pitcher, cups, a price sign, a customer, a coin pop, weather, and a bigger stand. Build #1 must ship one polished loop, not a broad list of partial systems.

Audience

Primary players: 6-10-year-old Roblox players who like tycoons, simulators, visible upgrades, bright props, and showing friends what they built.

Primary creative stakeholders: Twin A and Twin B. They shape recipe ideas, stand taste, customer reactions, weather jokes, and the "would we show this to friends?" read.

Support stakeholder: Dad. Dad protects scope, Roblox publishing discipline, and family learning goals without replacing the twins' creative surface.

Parent-readable audience: family and friends who want to see how the twins' feedback shaped a real product decision.

Success Criteria

OD-013 section 2 success criteria, cited verbatim:

1. Twins are excited to share with friends. Recess-energy. Screenshot-and-send. Would a 10yo actually take this to school and brag about it.
2. The game feels real. Production polish. Not vapourware. Visual consistency, audio that lands, mechanic that closes a loop. A stranger watching the commercial does not register "AI slop" or "demo".
3. The twins are excited. Creative agency, build literacy, ship-something achievement. The "fun parts" gap stays load-bearing (per OD-002 LEARNING-first rubric).

Acceptance interpretation:

• Share with friends: the screenshot moment is the first painted stand upgrade with customer, cup, coin pop, sunny widget, and glowing Upgrade Stand.
• Game feels real: the first loop closes in under 30 seconds with a visible prop, avatar action, and HUD response for every verb.
• Twins are excited: the brainstorm-stage pivot remains visible, and the twins own meaningful choices in recipes, stand colors, customer jokes, and weather reactions.

First Playable Loop

The Build #1 loop must be playable and visible in this order:

1. Buy lemons.
2. Squeeze and pour.
3. Set price.
4. Serve a customer.
5. Earn coins.
6. Upgrade the stand.
7. React to weather.
8. Repeat bigger.

First-loop timing target: close the first sale and first stand upgrade in under 30 seconds for a new player.

First-loop beat contract:

1. Player taps Buy Lemons.
2. Lemon crate fills on the counter.
3. Player taps or holds Squeeze.
4. Pitcher fills with bright lemonade.
5. Player flips the price sign to a starter price.
6. One customer walks up with a want bubble.
7. Player serves one cup.
8. Customer drinks and reacts.
9. Coins pop above the stand.
10. Upgrade Stand glows.
11. The stand changes from crate table to painted starter stand.

Screenshot Moment

The screenshot moment happens immediately after the first visible stand upgrade.

Required composition:

Painted lemonade stand + customer holding cup + coin pop +
sunny weather widget + glowing Upgrade Stand button.

This is a deterministic in-game moment, not a runtime screenshot-upload feature and not a generated image upload. The moment must include the stand, customer, cup, coin feedback, HUD weather, and next upgrade affordance. It must not be only a cropped beauty render or a balance screen.

Twin-facing line:

We sold one cup, and our stand got bigger.

MVP Scope

Build #1 includes:

• One sunny sidewalk, park, or front-yard map.
• One player stand.
• One stand upgrade path.
• One customer queue.
• One lemon-buy action.
• One squeeze-and-pour station.
• One simple price sign.
• One customer-service reward loop: coins plus stand-star progress if needed.
• One primary action button that changes by loop beat.
• One weather widget with sunny, cloudy, rain, and heatwave states.
• Simple recipes: classic first; pink or extra-ice only if scope allows.
• Customer reactions tied to price, weather, recipe, and wait time.
• First-demo HUD: day, weather, coins, customer want bubble, price sign, and Upgrade Stand.

OD-023 First Demo Scope

OD-023 narrows the first demo to one polished, smoke-testable loop. The first demo uses in-memory session state only; no DataStore persistence is part of first-demo acceptance.

First-demo cuts:

• No monetization, no PolicyService, no Robux purchase path, and no paid-random surface.
• Single-player only.
• Desktop keyboard and mouse only.
• Default Roblox avatar only; no avatar customization.
• No Roblox Studio editing. Implementation proceeds through .luau files, Rojo, Open Cloud publish, and smoke tests.
• DataStore profile design, mobile-safe HUD acceptance, touch/controller support, monetization policy handling, multiplayer, and custom avatar work are post-MVP or later acceptance only.

MVP excludes:

• Multiple maps.
• Multiple stand branches.
• Multiple simultaneous queues.
• Multiplayer.
• DataStore persistence.
• Trading.
• Full staff automation.
• Prestige or rebirth.
• Complex recipe math.
• Touch, controller, or mobile-first controls for the first demo.
• Avatar customization.
• Roblox Studio editing as an implementation path.
• Monetization, PolicyService, Robux purchase paths, or paid-random surfaces.
• External social posting mechanics.
• Runtime generated voice.
• Runtime screenshot upload or persistence.
• Paid-random core loop.
• Public URL or publish commitments.
• Production gameplay stories entering ready-for-dev from this issue.

Functional Requirements

FR1. Day start: the player begins on Day 1 with a sunny weather state, visible day counter, weather widget, coin counter, stand, customer path, and one clear primary action.

FR2. Supply purchase: the player can buy lemons through a server-confirmed action that visibly fills a crate on the stand.

FR3. Squeeze interaction: the player can squeeze lemons with a readable desktop keyboard and mouse interaction for the first demo.

FR4. Pour feedback: the pitcher fill level and lemonade color change when a batch is made.

FR5. Price sign: the player can choose a simple price state such as cheap, fair, pricey, surge, or discount; the sign must show the current state.

FR6. Customer queue: the game spawns one customer at a time from a bounded customer set, with a visible want bubble.

FR7. Customer service: serving a cup consumes batch inventory and resolves the customer's request through a server-authoritative service event.

FR8. Customer reaction: the customer's face, body pose, text bubble, or short moderated audio beat changes before reward payout.

FR9. Reward emit: completed service grants coins and visible progress toward the first stand upgrade.

FR10. Upgrade prompt: Upgrade Stand glows when the player can afford the first upgrade.

FR11. Stand transformation: the first upgrade changes the 3D stand silhouette from crate table to painted starter stand.

FR12. Weather widget: weather appears in HUD and world state, not only in hidden economy math.

FR13. Weather behavior: sunny supports the tutorial, cloudy slows demand, rain becomes a prep beat, and heatwave creates a visible rush with ice pressure if ice exists.

FR14. Recipe surface: classic lemonade ships first; recipe variety must change color, customer preference, or reaction before it counts as a product feature.

FR15. Twin input pipeline: twin-facing ideas for recipe names, stand colors, customer jokes, and weather reactions become acceptance notes for downstream stories.

FR16. Shareable state: the game creates the required screenshot composition after the first stand upgrade without needing an external sharing integration.

Nonfunctional Requirements

NFR1. The first loop closes in under 30 seconds for a new player.

NFR2. Every loop beat has a visible prop, avatar action, and HUD response.

NFR3. The stand upgrade reads clearly in the first-demo camera framing through silhouette, color, height, or signage change.

NFR4. The first-demo HUD avoids crowding the core top bar on desktop.

NFR5. Economy authority stays on the server for supply purchase, batch creation, price state, service completion, rewards, weather state, and upgrades.

NFR6. Reward events are idempotent per customer service id.

NFR7. First-demo state is in-memory session state only, resettable by smoke tests and not persisted through DataStore.

NFR8. First-demo implementation must not create placeholder DataStore modules, save adapters, purchase receipt handlers, or persistence acceptance criteria.

NFR9. The server remains authoritative for first-demo loop state even though it is in-memory only.

NFR10. Voice and audio references must use pre-uploaded, moderated Roblox audio assets with text fallback before runtime reference.

NFR11. Build #1 avoids paid-random progress pressure in the core loop.

NFR12. Monetization, PolicyService, Robux purchase paths, and paid-random surfaces are excluded from first-demo acceptance.

Post-MVP And Later Acceptance

These items remain useful product direction, but they are not first-demo acceptance:

• DataStore profile design: balances, stand tier, upgrade ids, recipe unlock flags, lemon variety unlock flags, tutorial state, and purchase idempotency records if paid products are approved later.
• DataStore save discipline: do not save per-cup sales history, per-customer queue snapshots, full weather history, generated media, or every squeeze/pour/serve tick; later saves should be debounced.
• Mobile-safe HUD and broader input support: later acceptance should cover mobile safe areas, touch, and controller without changing the first demo's desktop keyboard/mouse scope.
• Future paid random recipe cards or cosmetic crates require numerical odds and per-player policy handling before spend, but no such surface exists in the first demo.

Weather Product Contract

Weather changes the player's read and decisions without becoming a simulation spreadsheet.

Weather requirements:

• The first tutorial day is sunny.
• Weather must show in HUD and world.
• Weather effects must change visible customer behavior.
• Rain must not punish a brand-new player.
• Heatwave must show both opportunity and pressure.
• Weather state should be deterministic enough for tests and video capture.

Economy And Monetization Posture

The core loop must be earnable:

• Coins come from in-experience lemonade sales, tips, and progress beats.
• First stand upgrades are earned through play.
• Recipe and lemon variety unlocks improve color, choice, and reactions.
• Paid random items are not part of the first demo or Build #1 core loop.
• Robux must not appear as a gameplay reward.
• Advertising, if included later, uses earned in-experience coins and reads as more people noticing the stand.

This PRD does not authorize paid provider calls, video generation, site publishing, public URL changes, or canon amendments.

Roblox-Fidelity Gates

These are product acceptance gates for this PRD and downstream handoffs.

1. Art/world. The map, props, stand tiers, lemons, cups, signs, and weather states must read as blocky Roblox-stylized space, not generic CGI, photoreal fruit, or flat app art.
2. Avatars. Player and customer NPCs must read as Roblox R15 or R6 avatars with recognizable Roblox face grammar and blocky proportions.
3. UI/HUD chrome. Coin counter, day counter, weather widget, price sign, customer want bubble, HUD frame, and Upgrade Stand affordance must be visible in key beats.
4. Gameplay-loop visibility. A kid watching cold must be able to name the loop: buy lemons, squeeze and pour, set price, serve, earn coins, upgrade, weather, repeat bigger.

Acceptance rule: if an artifact hides the interface, removes the customer, skips a loop verb, or shows generic lemonade art without Roblox avatars, it fails this PRD's fidelity gate.

OD-005 Inherit And Contribute

Lemonade Stand Tycoon is Build #1 of the family-shared-infra portfolio. This build consumes:

• UGC wallet schema: compact entitlement and receipt/idempotency patterns for any future paid products, adapted without adding paid-random pressure to the core path.
• Persona library: existing Dad, Twin A, Twin B, Claude, and Crew persona discipline from BRAND-CANON.md and site/assets/library/personas/.
• Style-pack scaffold: the shared site/assets/library/style-packs/ structure, to be extended by the downstream LST style-pack rewrite.
• Asset-library spine: the site/assets/library/ metadata and parent-asset discipline from ASSET-LIBRARY.md.

This build contributes back:

• LST-style-pack-v1: a sunny Roblox-tycoon visual language for stands, lemons, customers, HUD, weather, and upgrade reveals.
• Persona refinements: approved Dad/Twin A/Twin B LST expressions or poses if downstream canon and asset work brings the family into customer-visible surfaces.
• Post-MVP DataStore patterns: compact stand profile schema, debounced save cadence, service-event idempotency, upgrade persistence, and policy-ready purchase records after first-demo scope is complete.
• Customer/reaction primitives: customer archetypes, want bubbles, recipe preferences, reaction beats, and reward timing conventions reusable by Build #2.
• Weather/economy primitives: day state, simple weather states, demand modifiers, and prep/rush UX patterns.

Twin-facing inheritance statement:

Our first game leaves tools for the next one.
Build #2 starts with our best parts ready.

Asset Contract

The current asset library still contains PST-era paths. This PRD does not amend ASSET-LIBRARY.md; OD-018 step 7 owns the canon and asset-library rewrite.

Required downstream LST library families:

• site/assets/library/style-packs/lst-tycoon-sunny-v1/
• site/assets/library/environments/lst-lemonade-stand-v1/
• site/assets/library/props/lemonade-stand/
• site/assets/library/props/lemons/
• site/assets/library/props/customers-park/
• site/assets/library/props/ui-cards/
• site/assets/library/props/vfx/
• site/assets/library/audio/music-references/lst/

Until these paths exist and are registered, downstream artifacts may specify target paths as requirements but must not cite them as completed assets. Customer-facing assets do not use ad hoc paths.

Product Risks And Guardrails

Downstream Handoff Notes

Do not start these steps in this issue.

• OD-018 step 7 canon rewrite: update BRAND-CANON.md, COPY-VOICE.md, JOURNEY-STORY-CANON.md, and ASSET-LIBRARY.md for Lemonade Stand Tycoon while preserving Dad/Twin A/Twin B likeness discipline.
• Storyboard step: build the 10-shot LST storyboard around the loop order: buy lemons, squeeze and pour, set price, serve customer, earn coin, upgrade stand, weather event, repeat bigger.
• Asset-library/style-pack step: create lst-tycoon-sunny-v1, stand tiers, lemon varieties, customer NPC set, weather variants, HUD chrome, and VFX paths before render or site work cites them as complete.
• G3 review: require CEO sign-off before first render spend, with all four Roblox-fidelity gates scored.
• G4 review: score whether a 6-10-year-old cold-watching the final cut would call it Roblox and name the loop verbs.
• Implementation planning: StoryCreator and ScrumMaster may break this PRD into stories later, but this issue leaves no gameplay story ready-for-dev.

Definition Of Done

• prd.md is rewritten for Lemonade Stand Tycoon.
• The PRD presents LST as Build #1 from the beginning.
• The twins-feedback pivot is framed as a brainstorm-stage event.
• OD-013 section 2 success criteria are cited verbatim and converted into acceptance checks.
• The first playable loop and screenshot moment are named concretely.
• Conservative Build #1 constraints are explicit: one map, one stand path, one queue, simple weather, simple recipes, no paid-random core loop.
• OD-023 first-demo cuts are explicit: in-memory session state, no DataStore, no monetization, no PolicyService, no Robux purchase path, no paid-random surface, single-player only, desktop keyboard/mouse only, default avatar only, no avatar customization, and no Roblox Studio editing.
• The four Roblox-fidelity gates are product acceptance criteria.
• Downstream handoff notes cover canon rewrite, storyboard, asset-library/style-pack work, and G3/G4 reviews.
• This issue avoids paid provider calls, video generation, site publishing, public URL changes, implementation story readiness flips, and canon amendments.

Sources

• OD-018 pivot directive: /srv/http/_hq/projects/project-roblox/OD-018-pivot-to-lemonade-stand-tycoon.md
• LST brainstorm: /srv/http/roblox/_bmad-output/planning-artifacts/brainstorm-lst.md
• LST domain research: /srv/http/roblox/_bmad-output/planning-artifacts/domain-research.md
• LST market research: /srv/http/roblox/_bmad-output/planning-artifacts/market-research.md
• LST product brief: /srv/http/roblox/_bmad-output/planning-artifacts/product-brief.md
• Brand canon: /srv/http/_hq/projects/project-roblox/BRAND-CANON.md
• Copy voice canon: /srv/http/_hq/projects/project-roblox/COPY-VOICE.md
• Asset library canon: /srv/http/_hq/projects/project-roblox/ASSET-LIBRARY.md
• Journey story canon: /srv/http/_hq/projects/project-roblox/JOURNEY-STORY-CANON.md

LST Domain Research: Lemonade-Economy Tycoon UX

Issue: ROB-27 Date: 2026-05-18 Workflow: /bmad-domain-research, applied headlessly for OD-018 cascade step 3 Scope: Lemonade Stand Tycoon only. This does not run market research, product brief work, storyboard work, canon rewrites, asset generation, site publishing, or video production.

Source Inputs

• /srv/http/_hq/projects/project-roblox/OD-018-pivot-to-lemonade-stand-tycoon.md
• /srv/http/roblox/_bmad-output/planning-artifacts/brainstorm-lst.md
• /srv/http/_hq/projects/project-roblox/BRAND-CANON.md
• /srv/http/_hq/projects/project-roblox/COPY-VOICE.md
• /srv/http/_hq/projects/project-roblox/ASSET-LIBRARY.md
• /srv/http/_hq/projects/project-roblox/JOURNEY-STORY-CANON.md
• Official Roblox Creator Hub pages listed in Sources.

Core Domain Finding

Lemonade Stand Tycoon should ship as a Roblox tycoon with an active stand-service loop, not as a passive cash dropper with lemonade decoration. The first playable loop must be:

buy lemons -> squeeze/pour -> set price -> serve customer -> earn coins -> upgrade stand -> repeat bigger

The loop is kid-legible because every verb has a visible prop, avatar action, and HUD response. The player should see lemons enter a crate, pitcher liquid rise, a chalk price change, an R15 customer receive a cup, coins pop, and the stand transform.

The LST promise from the accepted brainstorm stands:

> Buy lemons, make lemonade, serve customers, upgrade the stand, and grow bigger every day.

That sentence is the domain constraint. Any feature that does not make the stand economy, weather decision, customer response, recipe collection, or visible stand growth clearer should be deferred.

Lemonade Stand Loop Primitives

The first loop should close in under 30 seconds of first play:

1. Player taps Buy Lemons.
2. Lemon crate fills on the counter.
3. Player taps or holds Squeeze.
4. Pitcher fills with a bright lemonade color.
5. Player flips a simple price sign.
6. Customer approaches with a want bubble.
7. Player serves one cup.
8. Customer reacts.
9. Coin counter pops.
10. Upgrade button lights.
11. Stand changes from crate table to painted starter stand.

Required data primitives:

• DayState: day number, weather, demand modifier, prep hint, open/closed flag.
• SupplyDefinition: lemons, cups, ice, sugar, optional recipe ingredient.
• SupplyInventory: bounded counts only; no per-item history.
• RecipeDefinition: id, color, taste tag, ingredient list, unlock tier, customer preference tags.
• BatchState: empty, squeezed, mixed, chilled, ready, sold out.
• PriceSignState: cheap, fair, pricey, surge, discount; numeric price may exist under the hood, but the player-facing state should be simple.
• CustomerArchetype: kid, parent, runner, dog-walker, mail-carrier, tourist.
• CustomerRequest: weather need, recipe preference, price sensitivity, patience.
• RewardEmit: coins, tip, stand stars, recipe progress, ad meter progress.
• UpgradeDefinition: stand tier, storage, squeezer speed, cooler size, sign reach, helper, umbrella cover.

Visual primitives:

• Lemon crate, rolling lemons, squeezer lever, pitcher fill, cup stack, chalkboard price.
• Coin pop, tip jar bounce, stand-star sparkle, upgrade-button glow.
• Sidewalk queue, R15 customer avatars, weather widget, day counter, coin counter.
• Before/after stand tiers that read at thumbnail size.

Audio primitives:

• Pour, squeeze, cup tap, coin ding, customer sip, chalk sign flip, upgrade whoosh.
• Weather stings for rain, cloudy slowdown, and heatwave.
• Voice clips only on high-value beats, with text fallback and moderated asset IDs before runtime reference.

Weather Mechanic UX

Weather should change player decisions without becoming a spreadsheet. The widget is a small forecast card, not a simulator dashboard.

Recommended weather states:

Implementation rules:

• Weather should be deterministic per day for MVP, seeded by day number and player id if needed.
• Use server-owned day/weather state; clients only render the widget and local effects.
• Rain should not punish a new player in the first minute. First tutorial day should be sunny.
• Heatwave must show both opportunity and pressure: more customers, but ice stock visibly drains.
• Weather effects should alter spawn rate, patience, tips, and recipe preference. Avoid hidden multipliers with no visible explanation.

Advertising Levers

Advertising is a visible customer-spawn lever, not social-media pressure. It should read as "more people notice our stand."

MVP advertising surfaces:

• Sidewalk sign: low-cost, persistent small spawn-rate increase.
• Flyers: one-day boost, visible flyer stack empties or pinboard fills.
• Billboard: short rush window, more expensive, dramatic customer wave.
• Local post board: playful stand notice, not a real social platform mechanic.

Recommended model:

baseSpawnRate
  * weatherDemandModifier
  * adReachModifier
  * standTierModifier
  * priceFrictionModifier

Design constraints:

• Advertising spend uses earned in-experience coins.
• No player-to-player posting, no external sharing prompt, and no real social account metaphor.
• The spawn-rate change needs visible customer movement within a few seconds.
• Ad UI should show duration and reach in kid-readable terms: "Today", "Small boost", "Big rush".

Lemon Varieties And Recipe Collection

Recipes are the collection/progression surface. They should be simple enough for kids to predict and expressive enough for later content.

Starter set:

• Classic: yellow lemon, basic sugar, normal ice.
• Pink: pink lemon or berry add-in, strong visual color change.
• Strawberry: fruit add-in, higher kid-customer preference.
• Lavender: later cozy recipe, higher parent/tourist preference.
• Extra-ice: heatwave recipe, lower margin but higher rush satisfaction.

Lemon variety board:

• Yellow lemon: starter common.
• Pink lemon: early unlock, strong screenshot color.
• Meyer lemon: sweeter, boosts happy reactions.
• Blood orange or blood-lemon: rare color, use name carefully in twin-facing copy if needed.
• Giant lemon: later comic upgrade, not MVP unless scope allows.

Progression rule:

Recipe and lemon unlocks should improve choice, color, and customer reaction. They should not become paid random pressure. If random recipe cards ever become paid, odds and per-player policy handling are required before the user spends.

Stand-Tier Upgrades

Stand growth is the tycoon proof. Each upgrade must change the 3D stand, not only a stat.

Recommended tier ladder:

1. Crate table: single pitcher, hand-written sign, one cup stack.
2. Wooden cart: wheels, striped cloth, cleaner counter, tip jar.
3. Painted kiosk: roof, menu board, cooler, brighter sign.
4. Branded storefront: larger sign, display shelf, queue rail, lights.
5. Multi-location map hook: visible future expansion marker, not MVP.

Mobile-first transformation rules:

• Each tier needs a different silhouette.
• Upgrade reveal should hold for one beat before opening the next UI.
• Color and height changes matter more than tiny prop swaps on phone screens.
• The next upgrade affordance should appear on or near the stand, not only in a menu.
• Use one clear primary button: Upgrade Stand. Secondary upgrade categories can wait.

Customer-Reaction Beats

The customer reaction closes the service loop and should land before the reward UI.

Reaction beat pattern:

1. Customer approaches from sidewalk.
2. Want bubble shows recipe or weather need.
3. Player serves cup.
4. Customer drinks for one beat.
5. Face, pose, and short text bubble change.
6. Tip jar or coin pop lands.
7. Stand-star progress moves.
8. Upgrade or recipe prompt appears.

Reaction archetypes:

• Refreshed: fair price and correct recipe.
• Surprised: new recipe color or lemon variety.
• Loyal: repeat customer after good service streak.
• Heatwave saved: extra ice served during surge.
• Rain-prep praise: umbrella or cover upgrade appears after a rain prep day.
• Price-sensitive: happy at fair price, hesitant at pricey state.

Avoid one generic cheer animation. Reactions should vary by weather, recipe match, price state, and wait time.

Roblox Implementation Implications

Economy Authority

The economy must be server-authoritative:

• Server validates supply purchase, batch creation, price state, customer service, rewards, and upgrades.
• Client renders animations and prediction effects, but server confirms counters.
• Reward events should be idempotent per customer service id.
• Spawn and weather state should be reproducible for tests and video capture.
• Do not let local scripts award coins, stand stars, recipe cards, or upgrade unlocks.

DataStore Boundaries

LST should save a compact player profile, not a business ledger.

Save:

• Coin and stand-star balances.
• Owned stand tier and upgrade ids.
• Recipe unlock flags.
• Lemon variety unlock flags.
• Best stand name or approved preset stand name, if naming is used.
• Current tutorial state.
• Purchase receipt/idempotency records if paid products arrive later.

Do not save:

• Per-cup sales history.
• Per-customer queue snapshots.
• Full weather history.
• Generated images or videos.
• Large recipe/card blobs when ids and flags work.
• Every analytics tick from squeeze, pour, serve, or ad events.

Roblox Data Store guidance supports keeping related profile data together, watching object size, and avoiding storage growth from unnecessary keys. Treat weather, current queue, active rushes, and ad timers as reconstructable or short-lived runtime state where possible.

Spawn Rates And Simulation Cost

Customer simulation should stay simple:

• One queue controller per stand.
• Bounded maximum active NPCs.
• Server calculates customer requests; clients animate approach and reaction.
• Spawn rate changes should happen in coarse steps, not per-frame tuning.
• Rush windows should cap total active customers to protect low-end mobile devices.
• Rain prep mode should reduce NPC load rather than spawn customers who cannot buy.

UI And HUD Constraints

Mobile HUD must keep the loop readable while respecting Roblox safe areas:

• Top row: coin counter, day counter, weather widget.
• Stand surface: price sign and upgrade prompt.
• Bottom reach zone: primary action button for buy, squeeze, pour, or serve.
• Customer bubble: recipe icon and patience bar above customer head.
• Avoid tiny multi-tab economy panels in the first minute.
• Use ScreenGui safe-area behavior and avoid placing frequently used buttons in hard-to-reach corners.

Recommended MVP HUD:

[Day 1] [Sunny icon] [Coins 12]

Customer want bubble over NPC
Chalk price sign on stand

[Buy Lemons] / [Squeeze] / [Serve]
[Upgrade Stand] when earned

Moderated Audio And Copy

Audio and copy should be deterministic:

• Voice and sound effects resolve to approved Roblox audio assets before references land in gameplay or capture scripts.
• Use text fallback for every voice cue.
• Avoid user-generated stand names unless text filtering is implemented.
• If free-text names are allowed later, use Roblox text filtering before display.
• Do not imply Robux is earned from gameplay. Use fictional coins, tips, and stand stars.

Paid Random Item Posture

LST can support recipe packs or cosmetic crates later, but the first loop should be earnable.

Allowed future surfaces:

• Stand skins.
• Sign styles.
• Helper outfits.
• Convenience restock.
• Recipe-card collection with clear odds, free earn path, and policy controls if random paid items ever appear.

Disallowed surfaces:

• Paid-only core lemonade making.
• Paid-only first stand upgrade.
• Random paid items without actual odds before spend.
• Paid random items visible or usable for players with restricted paid-random policy.
• Robux framed as a gameplay reward.

Roblox-Fidelity Translation For Later Video

The later video must read as Roblox gameplay, not a generic lemonade commercial. Every domain beat should map to at least one of the four OD-018 fidelity axes.

Art And World

Required cues:

• Sunny sidewalk, park, or front-yard map.
• Blocky low-poly stand tiers and chunky props.
• Lemon crates, pitcher, cups, chalkboard, sign, cooler, coin pile.
• Clear material grammar: plastic, simple wood, bright fabric, flat UI panels.
• Weather variants visible in the same map: sun, clouds, rain prep, heatwave shimmer.

Avoid:

• Photoreal fruit still life.
• Generic mobile-game kiosk art.
• Soft illustration that does not show Roblox parts or walkable map space.

Avatars

Required cues:

• R15 or R6 proportions for player and customers.
• Roblox face grammar and simple accessories.
• Customer NPCs walk, stop, drink, react, and leave.
• Player avatar performs visible stand verbs: buy, squeeze, pour, serve, upgrade.
• Dad, Twin A, and Twin B appear only in project-story surfaces unless a later canon rewrite explicitly brings them into game/video content.

Avoid:

• Hand-painted mascot customers.
• Photoreal children.
• Family likeness drift from BRAND-CANON.md.

UI And HUD Chrome

Required cues:

• Coin counter.
• Day counter.
• Weather widget.
• Price sign or price popup.
• Upgrade button.
• Customer want bubble.
• Recipe card or lemon variety card.
• Optional mobile-screen frame for capture.

At least most video shots should include HUD or interaction chrome unless the shot is a deliberate hero beat.

Gameplay-Loop Visibility

Required order:

1. Buy lemons.
2. Squeeze and pour.
3. Set price.
4. Serve customer.
5. Earn coins.
6. Upgrade stand.
7. Weather event.
8. Repeat bigger.

If a shot could be mistaken for a generic lemonade picture, add HUD, an avatar action, a customer reaction, or a before/after stand change.

Five Elicitations Applied

The accepted LST brainstorm used these recommended lenses, and this research applies them as domain constraints:

1. Stakeholder Round Table: twin excitement, Dad governance, RobloxSME platform risk, downstream PM/UX/Architect needs.
2. User Persona Focus Group: first-time 6-10-year-old player, builder-twin, parent observer, Roblox capture reviewer.
3. SCAMPER Method: substitute grooming with lemonade making, combine weather with demand, adapt tycoon upgrades to stand tiers, eliminate passive factory drift.
4. Pre-mortem Analysis: generic CGI, DataStore bloat, hidden economy multipliers, unreadable mobile HUD, paid-random policy mistakes.
5. Expand or Contract for Audience: keep MVP one stand and one map; leave multi-location franchise, helper staff, and deep prestige for later.

Party-mode synthesis is folded into the domain rules rather than preserved as transcript.

Downstream Risks For Step 4 And Step 5

Market research risk:

• Step 4 must benchmark actual Roblox tycoon loops and visual grammar, not generic lemonade mobile games.
• LST comparables should inspect how Roblox games show counters, rushes, upgrades, queues, pets/customers, and mobile HUDs.
• Current player counts and shipped loops belong in market research, not this domain note.

Product brief risk:

• The first-loop screenshot moment should be the upgraded stand with customer, cup, sunny widget, coin pop, and glowing upgrade prompt.
• The product brief should cite the twins' brainstorm-stage feedback from brainstorm-lst.md: they liked the tycoon part and preferred Lemonade Stand Tycoon over the pet-salon theme.
• Avoid restoring PST as active Build #1 language outside deliberate tier-2 vault references.

Implementation risk:

• Do not persist cup-level logs or large blobs.
• Do not use unmoderated/random paid-item surfaces.
• Do not produce generic video guidance that drops R15/R6 avatars, HUD chrome, or visible loop order.

Sources

• OD-018 pivot directive: /srv/http/_hq/projects/project-roblox/OD-018-pivot-to-lemonade-stand-tycoon.md
• Accepted LST brainstorm: /srv/http/roblox/_bmad-output/planning-artifacts/brainstorm-lst.md
• Roblox Creator Hub, Data Store best practices: https://create.roblox.com/docs/cloud-services/data-stores/best-practices
• Roblox Creator Hub, Data Store error codes and limits: https://create.roblox.com/docs/cloud-services/data-stores/error-codes-and-limits
• Roblox Creator Hub, virtual item policies: https://create.roblox.com/docs/production/monetization/virtual-items
• Roblox Creator Hub, PolicyService:GetPolicyInfoForPlayerAsync: https://create.roblox.com/docs/reference/engine/classes/PolicyService#GetPolicyInfoForPlayerAsync
• Roblox Creator Hub, ScreenGui safe area and insets: https://create.roblox.com/docs/reference/engine/classes/ScreenGui
• Roblox Creator Hub, position and size UI objects: https://create.roblox.com/docs/building-and-visuals/ui/positioning-and-sizing-guiobjects
• Roblox Creator Hub, audio assets: https://create.roblox.com/docs/audio/assets
• Roblox Creator Hub, asset moderation: https://create.roblox.com/docs/studio/asset-types
• Roblox Creator Hub, text filtering: https://create.roblox.com/docs/ui/text-filtering

LST Market Research: Roblox Tycoon Comparables And Visual Grammar

Issue: ROB-29 Date: 2026-05-18 Workflow: /bmad-market-research, applied headlessly for OD-018 cascade step 4 Live data timestamp: 2026-05-18 UTC, queried through official Roblox public APIs and Roblox search.

Research Question

What are Roblox tycoon and adjacent simulator players actually seeing now, and what does Lemonade Stand Tycoon need to borrow, avoid, or sharpen so it reads as a real Roblox game for Dad, Twin A, Twin B, and their friends?

This artifact rewrites the prior PST market-research note for Lemonade Stand Tycoon. It does not run product brief, PRD, storyboard, canon rewrites, asset generation, site publishing, or video work.

Source Inputs

• /srv/http/_hq/projects/project-roblox/OD-018-pivot-to-lemonade-stand-tycoon.md
• /srv/http/roblox/_bmad-output/planning-artifacts/brainstorm-lst.md
• /srv/http/roblox/_bmad-output/planning-artifacts/domain-research.md
• /srv/http/_hq/projects/project-roblox/BRAND-CANON.md
• /srv/http/_hq/projects/project-roblox/COPY-VOICE.md
• /srv/http/_hq/projects/project-roblox/ASSET-LIBRARY.md
• /srv/http/_hq/projects/project-roblox/JOURNEY-STORY-CANON.md

Live Benchmark Table

Counts below are point-in-time API reads, not ranking claims.

Player Loop Findings

1. The pivot fixes audience fit without losing the proven tycoon shape. The accepted LST brainstorm records the twins' signal: they liked the tycoon part, did not want the pet-salon theme first, and recognized Lemonade Stand Tycoon faster. Market comps support keeping buy/make/sell/upgrade while changing the fantasy.

1. Real Roblox service loops show the job, not just the reward. Restaurant Tycoon 3's shipped description names customer serving, cooking, bill collection, and restaurant upgrades. Bloxburg names jobs and skills. LST should name and show every stand verb: buy lemons, squeeze, pour, set price, serve, earn, upgrade.

1. The lemonade category exists, but current titles are not dominant. Lightbulb's Lemonade Tycoon has 33.4M visits but only 12 players at query time; newer lemonade titles had 1-47 players. That is opportunity and warning: theme recognition is real, but a static or generic lemonade tycoon will not feel like a premium studio build.

1. Collection is expected, but paid-random pressure is not required for the first loop. Pet Simulator 99 proves collection clarity matters, while LST can translate that into lemon varieties, recipe cards, and stand skins. Build #1 should keep core recipes and first upgrades earnable.

1. Kids share visible ownership. Grow a Garden says players can flex fruits and finds on friends; Restaurant Tycoon 2 keeps friend visiting prominent; Bloxburg lets players build and decorate. LST's share moment should be a stand screenshot, not an abstract balance screen.

1. Mobile-safe HUD is part of the market expectation. Current Roblox tycoon pages consistently target mobile/tablet/desktop play, and Creator Hub safe-area guidance exists because Roblox core UI and device cutouts can hide controls. LST's first loop needs large action buttons, over-head want bubbles, and compact counters.

What LST Should Copy

• From Restaurant Tycoon 3: visible service order, station action, customer completion, bill/coin feedback, and build/upgrade loop.
• From Bloxburg: grounded kid-readable work fantasy where money comes from a recognizable job, not from invisible multipliers.
• From Pet Simulator 99: collection board clarity, big icons, clean rarity/readability language, and constant progress pips.
• From Grow a Garden: simple resource cycle, offline anticipation as a later hook, and shareable "look what grew" payoff.
• From Adopt Me: friend-readable world state, expressive avatar/NPC identity, and social-safe props that invite showing friends.
• From existing Lemonade Tycoon titles: harvest/make/serve/expand vocabulary, workers as later automation, and stock management as a light constraint.

What LST Should Avoid

• Passive-only droppers where lemonade is just a label on cash machines.
• Generic factory bloat: skill trees, rebirth worlds, and machine chains before the first stand feels fun.
• Robux or premium currency framed as a gameplay reward.
• Paid-only recipes, paid-only first upgrades, or paid random item pressure in the core path.
• Overcomplex recipe math that makes kids tune out before the first sale.
• Customer punishment beats that make the stand feel mean or chaotic.
• CGI/video prompts that show shiny lemonade but no Roblox avatars, HUD chrome, or visible gameplay loop.

Roblox-Fidelity Axes

1. Art And World

Market anchor: the strongest comps show walkable Roblox worlds, blocky props, and obvious build surfaces. Adopt Me, Bloxburg, Restaurant Tycoon, and Grow a Garden all sell place identity as much as mechanics.

LST implications:

• Use a sunny sidewalk, park, or front-yard map that reads as a Roblox space players can walk through.
• Build stands from chunky parts: crate table, wooden cart, painted kiosk, branded storefront.
• Keep lemons, pitchers, cups, signs, coolers, billboards, and coin piles large enough for phone screens.
• Weather must change the same map visually: sun, cloudy sky, rain-prep umbrella, heatwave shimmer.
• Avoid photoreal fruit, flat app-store kiosk art, and soft illustration that hides Roblox material grammar.

2. Avatars

Market anchor: the API records for the major comps expose R15/R6 avatar-type fields, and OD-018 requires the later video to show R15 or R6 Roblox avatars rather than generic mascots.

LST implications:

• Player and customers should read as R15 or R6 Roblox avatars with recognizable face grammar and blocky proportions.
• Customer NPCs need simple silhouettes: kid, parent, runner, dog-walker, mail-carrier, tourist.
• Reactions should be face/pose/text-bubble beats after drinking, before rewards.
• Dad, Twin A, and Twin B remain project-story canon unless a later canon rewrite brings them into in-game/video content.

3. UI And HUD Chrome

Market anchor: Roblox experiences are judged inside the Roblox app, with top bar, chat/leaderboard expectations, counters, game icons, and mobile safe areas. Roblox Creator Hub guidance says gameplay video should set accurate expectations and ScreenGui safe areas protect UI from core controls and device cutouts.

LST implications:

• At least most later promo shots should include HUD chrome: coin counter, day counter, weather widget, price sign, upgrade button, customer want bubble, mobile frame, leaderboard or chat where appropriate.
• First-minute gameplay UI should be compact: [Day 1] [Sunny] [Coins], overhead customer request, chalk price sign, one primary action button, and Upgrade Stand when earned.
• Do not hide the interface for beauty shots unless the shot is clearly a deliberate hero beat.
• The product brief should define the screenshot moment with HUD included, not cropped away.

4. Gameplay-Loop Visibility

Market anchor: service and production comps explain their loops in verbs: serve customers, cook dishes, collect bills, buy seeds, plant, harvest, make drinks, collect cash, upgrade.

LST implications:

• The first loop should close in under 30 seconds:

buy lemons -> squeeze/pour -> set price -> serve customer -> earn coins -> upgrade stand

• The later 60-second video must show the full OD-018 order:

buy lemons -> squeeze/pour -> set price -> serve customer -> earn coin -> upgrade stand -> weather event -> repeat-bigger

• Every loop beat needs a prop, avatar action, and UI response. If one is missing, the shot risks reading as generic lemonade art instead of Roblox gameplay.

Differentiation For LST

LST beats PST for this build because it preserves the tycoon loop the twins liked while replacing the pet-salon theme they rejected. Lemonade is easier to recognize in one second: lemons, pitcher, cups, price sign, customer, coins, bigger stand. It also fits a friend-share surface better for the current target audience: "our stand got bigger" is a fast brag.

The strongest screenshot moment for the product brief:

Fresh painted lemonade stand + customer holding cup + coin pop + sunny weather widget + glowing Upgrade Stand button.

Twin-layer candidate wording for later customer surfaces:

• "We sold our first cup and upgraded our stand."
• "Our lemonade stand looks bigger every day."
• "Friends can see our stand right away."

Parent-layer explanation for later customer surfaces:

The pivot keeps the learning value of a Roblox tycoon while moving the fantasy closer to the twins' taste. The game can teach loops, choices, tradeoffs, and iteration through props a child recognizes immediately.

Video And Storyboard Visual Grammar

For downstream step 8 and later video work, LST should use these market-backed visual anchors:

• Open on the Roblox world, not a fruit close-up.
• Show R15/R6 player avatar near the stand in the first seconds.
• Put HUD chrome in the frame early: coin counter, day counter, weather widget, price sign.
• Use overhead customer request bubbles to make orders readable without narration.
• Animate one stand verb per beat: buy crate, squeeze lever, pour pitcher, flip price, hand cup, coin pop, upgrade flash.
• Hold the stand before/after upgrade for one beat so kids can see the change.
• Add weather as a visible gameplay state, not a background mood.
• Frame at mobile-safe composition first; desktop crop can be more generous later.
• Keep the thumbnail and video honest: Creator Hub guidance favors media that tells players what the experience offers and sets accurate gameplay expectations.

Risks And Anti-Patterns

Five Elicitations Applied

The BMAD market pass carried forward the five recommended elicitation lenses from the accepted brainstorm and domain research:

1. Stakeholder Round Table: twins' excitement, Dad governance, RobloxSME platform risk, downstream PM/story/video needs.
2. User Persona Focus Group: 6-10-year-old first-time player, builder twin, friend watching a clip, parent observer, Roblox capture reviewer.
3. SCAMPER Method: substitute pet grooming with lemonade making, combine weather with demand, adapt restaurant service to a stand, eliminate passive factory drift, rearrange reward after reaction.
4. Pre-mortem Analysis: generic CGI, hidden tycoon loop, unreadable mobile HUD, lemonade incumbent sameness, Robux-as-reward mistake.
5. Expand or Contract for Audience: Build #1 stays one stand and one map; later versions can add staff, locations, recipe depth, and prestige.

Party-mode synthesis is folded into the findings rather than preserved as transcript.

Downstream Recommendations For Step 5 Product Brief

• Define LST as Build #1 from the start; do not frame it as a late rescue.
• Cite the twins' brainstorm-stage signal: they liked the tycoon part and preferred Lemonade Stand Tycoon over pet salon.
• Name the first-loop close: one cup sold and one visible stand upgrade in under 30 seconds.
• Define the screenshot moment as the upgraded stand with a customer, cup, coin pop, sunny widget, and glowing upgrade button.
• State the four Roblox-fidelity axes explicitly: art/world, avatars, UI/HUD chrome, gameplay-loop visibility.
• Keep Build #1 scope conservative: one map, one starter stand path, one customer queue, simple weather, simple recipes, no paid random core loop.

Sources

Official Roblox API query pattern:

• Universe lookup: https://apis.roblox.com/universes/v1/places/{placeId}/universe
• Game data: https://games.roblox.com/v1/games?universeIds=...
• Roblox search: https://apis.roblox.com/search-api/omni-search?searchQuery=lemonade%20tycoon

Official Roblox experience pages and API records used:

• Adopt Me!: https://www.roblox.com/games/920587237/Adopt-Me
• Pet Simulator 99: https://www.roblox.com/games/8737899170/Pet-Simulator-99
• Welcome to Bloxburg: https://www.roblox.com/games/185655149/Welcome-to-Bloxburg
• Grow a Garden: https://www.roblox.com/games/126884695634066/Grow-a-Garden
• Bee Swarm Simulator: https://www.roblox.com/games/1537690962/Bee-Swarm-Simulator
• Restaurant Tycoon 3: https://www.roblox.com/games/119048529960596/Restaurant-Tycoon-3
• Restaurant Tycoon 2: https://www.roblox.com/games/3398014311/Restaurant-Tycoon-2
• My Hello Kitty Cafe: https://www.roblox.com/games/9346039031/My-Hello-Kitty-Cafe
• Busy Business!: https://www.roblox.com/games/10914683361/Busy-Business
• Lemonade Tycoon: https://www.roblox.com/games/10675042838/Lemonade-Tycoon
• Lemonade Stand!: https://www.roblox.com/games/105446329981191/Lemonade-Stand
• My Lemonade Tycoon: https://www.roblox.com/games/138018802619610/My-Lemonade-Tycoon
• Be a Lemonade Seller: https://www.roblox.com/games/86270622488354/Be-a-Lemonade-Seller
• Smoothie Factory Tycoon: https://www.roblox.com/games/10905034443/Smoothie-Factory-Tycoon
• My Boba Store: https://www.roblox.com/games/82338394608938/My-Boba-Store
• Donuts Tycoon: https://www.roblox.com/games/118337332422903/Donuts-Tycoon

Roblox Creator Hub references:

• Thumbnails, videos, and icons: https://create.roblox.com/docs/education/build-it-play-it-create-and-destroy/icons-and-thumbnails
• On-screen UI containers and safe areas: https://create.roblox.com/docs/ui/on-screen-containers
• ScreenGui safe-area behavior: https://create.roblox.com/docs/reference/engine/classes/ScreenGui/ScreenInsets
• PolicyService paid-random posture: https://create.roblox.com/docs/reference/engine/classes/PolicyService#GetPolicyInfoForPlayerAsync

LST Storyboard Phase A.2 RobloxSME Audit

Issue: ROB-43 Source storyboard: /srv/http/roblox/_bmad-output/video-artifacts/lst-promo-storyboard-kernel.md Audit role: RobloxSME shadow, OD-020 Phase A.2 Date: 2026-05-18

Verdict

Phase A.3 may proceed after the required amendments below are folded into the shot-manifest re-spin instructions. The revised storyboard is ACCEPT on Roblox gameplay realism and OD-020 production direction, with one WEAK asset-library/reference-lock risk that must be handled before any manifest is treated as render-ready.

Fidelity Axis Table

Family Cameo Audit

R15 adaptation plausibility: ACCEPT as a storyboard direction. The family seeds exist under site/assets/library/personas/{dad,twin-a,twin-b}/, and OD-020 explicitly calls for props/avatars-lst/{twin-a-r15-admin,twin-b-r15-admin,dad-r15-helper}.png generated from those seeds. The adaptation is plausible if Phase B uses the canonical persona PNGs as reference inputs and registers parent chains in the target folder _index.yaml.

Required Amendments Before Phase A.3

ROBLOX-SME-AMENDMENT: Do not let Phase A.3 treat newly named OD-020 assets as render-ready references until they exist under site/assets/library/ and are registered in the nearest _index.yaml. Current missing/new targets include props/avatars-lst/twin-a-r15-admin.png, props/avatars-lst/twin-b-r15-admin.png, props/avatars-lst/dad-r15-helper.png, props/ui-cards/leaderboard-top-3.png, props/ui-cards/chat-bubble-customer.png, props/ui-cards/chat-bubble-admin.png, props/ui-cards/playing-now-badge.png, props/ui-cards/title-card-lst-logo.png, and props/vfx/plus-50-coins-float.png.

ROBLOX-SME-AMENDMENT: Phase A.3 shot manifests must either wait for Phase B reference-lock output or clearly mark these as planned references, not signed render inputs. ASSET-LIBRARY.md requires shot-manifest references to be library-relative paths that exist and are registered; prose intent or future filenames are not enough for paid still/motion work.

ROBLOX-SME-AMENDMENT: Beat 10 needs an explicit asset contract for the Free • Roblox tag. Either include that text inside props/ui-cards/title-card-lst-logo.png and state it in the manifest brief, or add a dedicated library path such as props/ui-cards/free-roblox-tag.png. The current storyboard says the tag appears but the required target list only names the title-card logo.

ROBLOX-SME-AMENDMENT: Family cameo manifests must cite both the R15 adaptation path and its parent canonical persona seed. This is the canon bridge that prevents a generic Roblox child/adult from replacing Twin A, Twin B, or Dad. Required parent seeds are personas/twin-a/twin-a-canonical-avatar.png, personas/twin-b/twin-b-canonical-avatar.png, and personas/dad/dad-canonical-avatar.png.

Non-Blocking Observations

• The narrator lines are TWIN-layer simple and avoid the COPY-VOICE.md TWIN banned-word list.
• The storyboard correctly keeps twins silent in spoken narration; cameos are visual/chat overlays only.
• The PRD excludes multiplayer from MVP runtime scope, but OD-020 is a promo/commercial directive. Showing multiple approaching players in beat 08 is acceptable as #1-hit promo energy, not a Build #1 MVP promise, as long as downstream public/product docs do not reinterpret it as launch MVP multiplayer.
• OD-020 remains production/universe-building only and does not alter /journey/, consistent with JOURNEY-STORY-CANON.md.

Handoff

No storyboard rewrite is required from RobloxSME. Phase A.3 may proceed if the shot-manifest worker folds the amendments above into manifest reference status and Phase B dependency notes. Paid still/motion work remains blocked until reference-lock and reviewer signatures exist.

LST Promo Audio Lock

Issue: ROB-39 Workflow: OD-018 cascade step 9, StoryCreator audio-lock pass Storyboard source: bmad-output/video-artifacts/lst-promo-storyboard-kernel.md Machine manifest: bmad-output/video-artifacts/audio/lst-promo-audio-manifest.yaml Status: locked plan only; no audio files generated

Canon References

• /srv/http/_hq/projects/project-roblox/BRAND-CANON.md
• /srv/http/_hq/projects/project-roblox/COPY-VOICE.md
• /srv/http/_hq/projects/project-roblox/ASSET-LIBRARY.md
• /srv/http/_hq/projects/project-roblox/JOURNEY-STORY-CANON.md
• /srv/http/_hq/projects/project-roblox/OD-018-pivot-to-lemonade-stand-tycoon.md
• /srv/http/_hq/projects/project-roblox/OD-016-final-provider-stack.md
• /srv/http/roblox/_bmad-output/video-artifacts/lst-promo-storyboard-kernel.md

Supersession

ROB-22's PST promo audio lock is superseded once this LST audio plan is accepted. Do not unblock, reuse, or remix PST voice, music, SFX, or proxy assets for current-state Lemonade Stand Tycoon planning.

Storytelling Lock

Framework: Roblox-fidelity gameplay-loop promo.

Story spine: the player starts with a tiny stand, buys lemons, fills the pitcher, sets a fair price, serves a customer, earns coins, upgrades the stand, reacts to hot weather, and repeats bigger.

This is not a pet-salon, bubble, battle, boss-drop, or factory-dropper track. The sound should feel sunny, quick, readable, and kid-clear.

Global Mix Direction

• Target length: exactly 60.0 seconds.
• Target final loudness for assembly: -16 LUFS integrated, true peak under -1.5 dBTP.
• Music bed: warm sunny upbeat lemonade-stand bed, light handclaps, bright plucks, soft shaker, tiny coin accents, and a clean final title hit. Lift after the first sale and again when the stand upgrades.
• Voice plan: future synthetic provider voice placeholders only, compatible with OD-016 default-library labels bill, liam, and sarah.
• Voice safety: no family, twin, or persona voice cloning. The voice labels are provider placeholders for later generation, not likeness claims.
• Generation boundary: this issue creates only lst-promo-audio-lock.md and lst-promo-audio-manifest.yaml.
• Later steps: actual ElevenLabs voice generation is OD-018 step 14. Suno music-bed generation is OD-018 step 15 and remains a manual operator action.

Locked Timing Map

SFX Cue Map

Provider Boundary

Allowed in this issue:

• Voice-line text.
• Voice assignment placeholders: bill, liam, sarah.
• Music-bed direction for the later Suno prompt.
• SFX cue names, timings, and direction.
• Machine-readable YAML plan.

Not allowed in this issue:

• ElevenLabs calls.
• Suno generation.
• Cloudflare, Runway, Hyperframes, or paid provider calls.
• Voice WAVs, music files, SFX files, stills, motion clips, final renders, public URLs, site publishing, or reference-image generation.

Handoff Notes

Step 10 reference-image generation can consume the shot-manifest order and timing alignment from this lock, but it must not treat audio as generated. Reference-image work remains blocked by the LST reference-lock rules in lst-reference-lock-needed.md and the reviewer signature fields in each lst-NNN-SHOT-MANIFEST.yaml.