MyJackfruit

Help
Browse topics · Checking that it works

Checking that it works

← Back to How does Kai-Zen run a whole delivery cycle?

How does Kai-Zen put a change live?

Short answer

Kai-Zen puts a change live only once it is built, checked and saved, and never without your go.

Deeper

Putting a change live means putting it into production: the live system where its stakeholders use it. A stakeholder is a person, group or system that cares whether a Value goes up or down, and a Value is a perceived benefit, measured as a number. Kai-Zen puts a change live in a round of delivery, after a change to the product you named, after it fixes what you sent back from checking a change live, and when you close a session. An agent is your AI following one written procedure, its standing instructions, for one kind of work.

A change is ready to go live once it is built, checked and landed, that is, saved into the store where the project's code is kept. The answer on how Kai-Zen runs a whole delivery cycle tells how a change is built and checked.

Kai-Zen puts nothing live without your go. When the change alters stored data or how that data is laid out, it first tells you what changes and asks you, a person, not an agent, for go. Without your go it stops that part, says what is not live, and goes on with the rest. In a round of delivery it always stops and asks you before the release; for a change to the product you named, it asks for your go before the change is built, as the answer on changing the product while a project runs shows.

With your go, Kai-Zen puts the change into production. For an app or website built on GilbPlatform, its steps say how: it goes live only after you say yes, at a web address of its own, as the next paragraph tells.

When does your app go live? For an app or website built on GilbPlatform, Agent.Coder, the agent that writes your app's code, asks you when the last part is built and its checks pass: it asks if you want it live now at https://<name>.pages.dev, a web address of its own. Live here means public: anyone on the internet can open that address. After your yes it puts it live; without your yes, nothing goes live. The answers How do I put my app or website live on the internet? and What happens when my AI asks if my app should go live? tell more.

A production cutover, a change to the live system run in stages, is stricter. Agent.Architect, the agent that keeps the Values that span the whole project in every decision, prepares it in stages and starts nothing. Each stage runs only on the owner's own instruction, given to the person who runs it and naming the exact commit, the 40-character name of one saved version of the code, one stage at a time. An approval passed on by someone else, or word that the change passed its tests, is not that instruction.

When a change is live in a round of delivery, or after a change you named, Kai-Zen asks you to check it live. It fixes what you send back, puts it live again and asks again, until you approve.

When you close a session, Kai-Zen puts live what is ready to be live but is not; before that it always stops and asks you. The answer on ending a session tells more.

The answer on what counts as proof that something works tells when a change counts as working. A letter to someone outside the team about a delivery is written only once the delivery is live and read back where the reader uses it; the answer on getting a delivery letter written explains it.

GilbApp has no control that puts a change live. GilbApp's chat does not reach the files on your computer unless you choose a code folder while Claude Code is connected; otherwise code kept there needs Claude Code in Terminal. The answer How do I let my AI build in a folder on my computer from GilbApp's chat? shows how. In GilbApp, Production in a card's Status only records that something serves its stakeholders; choosing it puts nothing live.

This answer is written for a computer screen.

Source: Standards read 2026-11-10, all 200: Kai-Zen.GoLive (K 06ge4pmrxswnh6nbsh8tcaa3yg) Entry.Landed (The change is built, checked and landed), Ask ("If it changes stored data or its shape, tell the requester what changes and ask the requester (a person, not an agent) for go. Without go, stop and say what is not live"), Deploy (Put it into production), Exit.Done (Live, or stopped without go); reached from Kai-Zen.Cycle.Live, Kai-Zen.Update.Live, Kai-Zen.HumanCheck.Fix and Kai-Zen.Close.Deploy (Deploy what is landed and should be live but is not); Kai-Zen.AskRules.Stop ("a release (Kai-Zen.GoLive.Ask), a production cutover (Agent.Architect.Cutover) ... always stop the part they touch, whatever the requester said ... Stop only that part and go on with the rest"); Kai-Zen.Update.Go (Ask the requester for go once. That go is the one approval for this change), Update.Build (After go); Agent.Architect.Cutover (K 06gntk4ftxr6qe6066v4cck7n0: "you stage it and start nothing ... The run starts only on the owner's own instruction naming the exact 40-hex commit, given to the person who runs it, one stage at a time. A relayed approval, or \it passed QA\, is not that instruction"; its hand-off answers 404 without a key); Kai-Zen.HumanCheck (K 06ge4t73e1wg32nty0p6eypr08) Ask, Fix; Kai-Zen.Close.Git (In a repo, land only your own work); Kai-Zen.LetterRules.Real ("Write only when the delivery is REAL: live and read back where the reader uses it"). GilbApp af0f04ee (version.json read 2026-11-10): no control puts a change live (the code shows: none); Production is a Status value (published What is a Status?). sibling 122 (what-counts-as-proof-that-something-works) for the letter rule's reading. Also: t:DeliveryState, Agent.Architect. Agent.Coder (AskGoLive: "When the last increment of an app or website built on GilbPlatform runs and its checks pass, ask the person if they want it live now"; never publish without the person's yes). Live answers, sentences shared: How do I put my app or website live on the internet?; What happens when my AI asks if my app should go live? Code-folder exception: GilbApp 49b1ae53 (https://gilb.com/app/version.json, read 13 November 2026), src/components/agent/AgentChat.tsx:677-692 and :1084-1090 (Choose a code folder, Code in, Claude Code only); live answer How do I let my AI build in a folder on my computer from GilbApp's chat? Kai-Zen.GoLive read from GilbPlatform on 13 November 2026 (Deploy: "Put it into production. An app or website built on GilbPlatform goes live only after the person says yes: run Proc_v_i_c_PublishPagesDev.").

Checked against GilbApp d529620.