Kaisen Fork, and Improve brief now counts as spend
Kaisen builds can be forked from their current files or a restore point, and Improve brief presses now count toward Kaisen spend and caps.
Fork a build
We just shipped Fork for Kaisen builds. It creates a new build in the same project with the same brief and the same files, either the current ones or, if you use Fork from here on a restore point, that version. Use it to try another direction, say the same app on a different database, while the original stays as it is.
A fork costs nothing until you run it: no model is called. It starts idle with no runs, so you can ask for a change, press Build or Deploy as it is.
Not copied: runs and history, spend, the live app (a fork gets its own app, address and empty database when you deploy, and uses one of the project's app slots), restore points, secret values (the page lists the names so you can set them again), uploaded files, GitHub output settings and token, and test results. A fork counts toward the project's build limit, and you can't fork current files while a run is in progress.
Improve brief is now real spend
Each Improve brief press used to be audit-only. It now counts as Kaisen spend: it adds to the project's day and 30-day totals, the daily cap and the member's daily limit, and a press is refused when a cap is already reached. When you build from that brief, the presses are added to that build's cost.