Event budget ↗
Ticket income, event costs, and the amount left over. Change attendance or adapt the cost rules.
Try it: Add a booking fee or change the cost per guest.
Example
Data apps / Generated Why explanations
You write the formulas, controls and labels in Bosatsu; the page and its Why view are generated from that program, so the explanations never drift from the formulas.
Ticket income, event costs, and the amount left over. Change attendance or adapt the cost rules.
Try it: Add a booking fee or change the cost per guest.
How much water does one rainfall event collect, and how much overflows the tank?
Try it: Change the roof size or tank capacity.
Run NOAA weather observations, or your own daily rainfall CSV, through an inspectable daily tank model. Change capacity and demand, inspect captured data, and share a saved report.
Try it: Increase daily demand, then inspect the day the tank runs dry.
Read the daily model, shared tank model, and report configuration.
Estimate runtime from a battery energy budget, a constant load, and a usable-capacity assumption.
Try it: Compare the same battery powering different devices.
Scale ingredient weights to a different number of servings. Replace the ingredients with your own.
Try it: Replace these ingredient weights with your recipe.
Convert file size and connection speed into transfer time, allowing for a chosen efficiency.
Try it: Compare a faster connection with a smaller file.
A subscription business month by month, laid out as a spreadsheet: customers, revenue, costs, hiring and the cash left in the bank. Every number in the table has its own Why.
Try it: Hire faster, then click the month the cash runs lowest.
It models demand, supply, and a per-unit tax using three straight lines.
These are illustrative Bosatsu models, not forecasts or policy recommendations.
The archive lists earlier UI runtime fixtures.
Ask your agent about anything here; it has the detail.
What this is about: Data apps with Why