Build my first project: Break-Even Calculator for Last Light Presents

What: I book small gigs for Last Light Presents. Our little venue holds 120 people. I handle offers for bands and the person on the door keeps an eye on ticket sales.

When: On a Friday show we thought a nearly full room meant a good night, until we added up the guarantee, sound engineer and the venue's fee on every ticket.

Where: The deal is pencilled into my booking notebook while the ticket count lives on a separate sheet. The promoter and the door lead both need the same answer.

Why: Once I agree a guarantee I carry the risk of a slow night. I want to know how many tickets cover the night, and see when even a sellout would fall short.

How: I want to change one number on a show settlement and immediately see the break-even crowd and our cash surplus or shortfall at the current ticket count. A ticket-stub style show sheet would suit us.
The project I chose: Break-Even Calculator for Last Light Presents
What I want to prove: Build a show settlement for 120 seats, $2,200 fixed costs, a $25 ticket and $5 fee per paid ticket. At 100 sold show a $200 shortfall; at 110 sold break even. If capacity drops to 90 flag that even a sellout falls short.

Interview me before building
Read my original interview, chosen project, business rules and acceptance checks. Review the report, app files and examples I have supplied. Start from what you already know about my business and carry my decisions forward. Open our conversation with the business or design decision that would most improve the result. Handle installation and publishing when we reach those steps.
Interview me to get everything you need to build the best result for my business. Explore who will use it, what they need to accomplish, what happens in practice, which decisions and exceptions matter, how the app should look and feel, and what a successful outcome looks like. Explore data, permissions, devices and integrations where they affect the work.
Follow my answers wherever they reveal something important. Ask for concrete examples, discuss trade-offs in my language, and resolve gaps or conflicting requirements with me. Continue the interview for as many rounds as the project needs. Use fictional or redacted examples when discussing actual work.
Once you understand the outcome, summarize how the app will work in a representative case and what will count as success. Carry my answers into the design, business rules and acceptance checks, then build and test that workflow.

Getting started
I am starting from scratch. If this workspace can build and run the app, start here. If setup is needed, ask which device I use if you cannot tell, and guide me one step at a time.

Build instructions
To implement the Break-Even Calculator for Last Light Presents, follow these steps: Start by designing the first screen around a show settlement, an object the business already works with. The user of this object is the owner, who makes decisions about booking gigs based on the break-even point. The fields of this object include the guarantee, sound engineer fee, venue fee, ticket price, and sales count. The action that changes its state is entering a new value for one of these fields. Give the show settlement visual weight and use the owner's vocabulary. Use the approved brand colour #D14C2F and create a typographic identity for the sample business. Pick typography, spacing, materials, and imagery that suit the trade. Include a second working view when there is a genuine handoff or saved record to reopen. The initial screen should display the current show settlement with the break-even point and cash surplus or shortfall. The owner can then adjust the guarantee, sound engineer fee, venue fee, ticket price, or sales count to see how the break-even point changes. For example, if the owner enters a guarantee of $1000, sound engineer fee of $200, and venue fee of $5 per ticket, the calculator should show the break-even point and cash surplus or shortfall at the current ticket count. If the owner adjusts the ticket price or sales count, the calculator should update the break-even point and cash surplus or shortfall accordingly. The calculator should also flag if the capacity drops to 90 and even a sellout would fall short. The technology used for this project is a web application built with JavaScript, HTML/CSS. The checks for this project include entering the guarantee, sound engineer fee, and venue fee, then calculating the break-even point, and entering the ticket price and sales count, then showing the cash surplus or shortfall. The limits for this project include a capacity of 120 seats, fixed costs of $2,200, a ticket price of $25, and a venue fee of $5 per ticket. The design should use the approved brand colour and a typographic identity for the sample business. The cases for this project include entering a guarantee, sound engineer fee, and venue fee, then calculating the break-even point, and entering a ticket price and sales count, then showing the cash surplus or shortfall. The interface brief is to design the first screen around a show settlement and give it visual weight and use the owner's vocabulary. The decision support for this project includes identifying the person, the event they respond to, the inputs they actually have, and the next action, and limiting the first project to one job with an observable success condition. The evidence policy is to attribute operating details only to the owner's actual answers and to describe possible tasks for the trade. The project scope is to design only the project the owner chose, keeping their desired test intact. The review for this project includes building a show settlement for 120 seats, $2,200 fixed costs, a $25 ticket, and $5 fee per paid ticket, and showing a $200 shortfall at 100 sold and breaking even at 110 sold. If the capacity drops to 90, the calculator should flag that even a sellout falls short.

Workflow examples that must pass
Enter guarantee, sound engineer fee, and venue fee → Calculate break-even point (stage = Before calculation, guarantee = $1000, sound_engineer_fee = $200, venue_fee = $5)
Enter ticket price and sales count → Show $200 shortfall (stage = After calculation, ticket_price = $25, sales_count = 100)
Enter ticket price and sales count → Break even (stage = After calculation, ticket_price = $25, sales_count = 110)
Enter capacity, ticket price, and sales count → Flag that even a sellout falls short (stage = After calculation, capacity = 90, ticket_price = $25, sales_count = 90)

Design
My chosen brand colour is #D14C2F. Use it consistently as an accent, provide a readable foreground on every surface, and keep important status differences understandable without colour alone. Use the approved brand colour #D14C2F and a typographic identity for the sample business
Design the first screen around an object this business already works with and the decision someone makes from it. Name that object, its user, its fields, and the action that changes its state. Give it visual weight and use the owner's vocabulary. Use the approved brand colour and any supplied logo; otherwise create a typographic identity for the sample business. Pick typography, spacing, materials and imagery that suit the trade. Include a second working view when there is a genuine handoff or saved record to reopen. Keep engineering checks, the sales pitch and build instructions outside the operator interface.

Recommended technology
- Web application
- JavaScript
- HTML/CSS

Acceptance checks
- Enter guarantee, sound engineer fee, and venue fee → Calculate break-even point
- Enter ticket price and sales count → Show $200 shortfall
- Enter ticket price and sales count → Break even
- Enter capacity, ticket price, and sales count → Flag that even a sellout falls short
- At 100 sold show a $200 shortfall
- At 110 sold break even
- If capacity drops to 90 flag that even a sellout falls short

Preview and handoff
Use fictional sample records and let me try the complete first task. Explain what you actually tested and what remains to verify. Give me the source files and show me how to reopen the app locally. Then offer the Cloudflare publishing steps below.

From the demo to my application
After I can try the demo, tell me which checks passed and what still needs testing. Ask me: “Would you like me to build this application from this demo?” Wait for my answer.
If I reply “Yes, build this application”, or clearly agree, start implementing the first usable version in this coding workspace. Carry forward the approved design, workflow, source files and acceptance checks. Keep the demo available as a reference. If implementation reveals a gap, return to the interview and work through it with me.
My yes authorizes building and testing. Get separate approval before publishing, enabling charges, connecting live accounts or customer data, or sending real messages.

Put my finished app online with Cloudflare
Once the first app passes its checks, offer to publish this exact version at a free workers.dev address I can open on my phone or share. Tell me the link will be public, show the proposed project name and sample records, and ask whether I want to publish now. A local build can stay local if I decline.
Use my own Cloudflare account. If I am new, guide me through creating a free account at https://dash.cloudflare.com/, verifying my email, and choosing my account subdomain in Workers & Pages. If I already have an account, reuse it. Let me handle sign-in in my browser without pasting a password, token or one-time code into chat. If using the CLI, use npx wrangler login as needed and npx wrangler whoami to confirm the intended account.
Package only the public app assets in a clean folder with index.html at its root. Use a new, available Worker name and a Wrangler configuration with today's compatibility date, workers_dev set to true, and assets.directory pointing to that folder. Keep the master prompt, report, private records and credentials outside the assets directory. Use Workers Free for this static app. If setup requests payment or would replace an existing app, pause and explain. A custom domain is optional.
After I approve, run npx wrangler deploy in the configured project. If this environment cannot run it, guide me through the Workers dashboard static file upload one step at a time. Copy the actual workers.dev URL from Cloudflare's deployment output. Open the link in a fresh browser session, reload it, and try the main acceptance case. Give me the verified link and tell me how to publish updates to the same Worker. Use the official guide if the dashboard has changed: https://developers.cloudflare.com/workers/static-assets/get-started/. If you cannot access the link, say what remains for me to check. Keep live integrations and paid services separately opt-in.