Observe the current player-visible game state as semantic text, including approximate UI bars rather than hidden ratings.

Return the displayed calendar, weather range and icons, daily event, and current location.

Return only rules stated by the visible help text or exposed by the setup controls.

Browse every location as a player can: name, description, rent, and approximate popularity/satisfaction bars.

Return the visible report for the most recently completed day, including P&L, satisfaction, missed sales and displayed feedback.

Return the completed-day values available from the current month's Results views: sales, revenue, visitors and earnings.

Return the player-visible balance sheet, inventory, approximate location bars, staff, upgrades and month-to-date P&L.

Browse all upgrades as displayed: names, card descriptions, prices and ownership state.

Buy a named permanent stand upgrade.

Browse available staff as displayed: names, card descriptions, daily costs and hired state.

Hire or fire one staff member for subsequent days.

Move the lemonade stand to a named location for the next day.

Set the exact lemons, cups of sugar, and ice cubes used per pitcher before starting the day.

Set the selling price per cup, in cents and in 10-cent increments.

Set the advertising budget for the next day, in whole-dollar increments.

Buy one of three fixed package sizes. The response reports whether the purchase was applied and includes the updated state.

Buy several visible supply packages in one ordered basket. Each line reports how many packs were applied; later lines may still succeed after an earlier rejection.

Return the displayed units and cost of every supply package.

Start the configured day. If supplies are insufficient, returns a structured game_rejected_action error.

Atomically start and skip the configured day, capture its visible results, and return the next decision state. expected_career_day prevents accidental duplicate execution after a timeout.

Advance a running day and return the next decision state. Use skip for benchmarks, fast or realtime for visible observation.

Read your private persistent player notebook. It contains only notes you previously chose to write and survives context compaction and runner restarts.

Replace your persistent player notebook with a concise set of hypotheses, experiments, and facts you want to remember.