# I found a fault just before going live. Should I wait or publish anyway?

Checked 2026-11-15 against GilbApp d5296208bbffa2ab70076e6194f5537c4be1ddf7.

You decide: say no for now and have it fixed first, or say yes and have it fixed in an update afterwards.

## Deeper

This answer is advice. Whether to wait is your choice; no rule decides it for you, and nothing here promises a result.

The choice is yours. Agent.Coder, the agent that writes your app's code, asks if you want your app live when the last part of what you asked for runs and its checks pass, and it never publishes without your yes. An agent is your AI following one written procedure, its standing instructions, for one kind of work.

If you wait. Say no, and tell your AI the fault in the same answer: where it happened, what you expected, and what happened instead; the answer [How do I tell my AI about a fault so it can fix it?](http://support.gilb.com/help/how-do-i-tell-my-ai-about-a-fault-so-it-can-fix-it) shows how. Nothing goes live. Your AI tells you that the app is not live, and where it runs instead. The fault is fixed and tested again, and you can try it again on your computer. You can tell it later, in your own words, that you want it live.

If you publish anyway. Your app goes live with the fault, and it is public: anyone on the internet who has that address can open it. Tell your AI about the fault, as How do I tell my AI about a fault so it can fix it? shows; the fix is built, checked and, with your yes, put live again at the same address, and uses no new site; see [How do I update my app after it is live?](http://support.gilb.com/help/how-do-i-update-my-app-after-it-is-live) Until then, people who open the app can meet the fault. You cannot take a site off the internet yourself today; see [How do I take my app off the internet?](http://support.gilb.com/help/how-do-i-take-my-app-off-the-internet)

What to weigh. Many people wait when the fault:
\- could show one person's data to someone else, or let someone change what they should not;
\- could lose or spoil what people save: going back in the code does not take back what was written to a vault, the place where a person or a group keeps their records;
\- puts a password or a key in your app's files, where anyone could open it;
\- stops the main thing your app is for, or stops people signing in.
A smaller fault, such as a wrong word or a button in the wrong place, while people can still do what they came for, is often fixed in the next update instead. If only a few people get the address at first, fewer meet the fault, but the app is public all the same; see [Can I let a few people try my app before everyone can see it?](http://support.gilb.com/help/can-i-let-a-few-people-try-my-app-before-everyone-can-see-it)

A fault or a change? If the app does what was agreed but you want it different, that is a change to the product, not a fault. The answer [How do I change the product while a project runs?](http://support.gilb.com/help/how-do-i-change-the-product-while-a-project-runs) shows how.

If the fault seems to be in GilbPlatform or GilbApp rather than in your app, write to support@gilb.com: what you did, what happened, and at what time.

This answer is written for a computer screen.

Source: Standards read from GilbPlatform on 13 November 2026: Agent.Coder \(AskGoLive: ask when the last increment runs and its checks pass; No: say it is not live, and where it runs; never publish without the person's yes; AfterIncrement: on FAIL fix and test again\), Kai-Zen.Update, Kai-Zen.GoLive \(Deploy: only after the person says yes\), Standard Rule\_Code\_deployment \(RuleDeployPagesDev: "Not live yet: takedown and abuse handling"\). GilbPlatform 0fc5a548 \(https://id.gilb.com/version, read 13 November 2026\): src/routes/publish.ts:278, :413, :442 \(no take-down door for a person\). Live help pages, sentences shared: What happens when my AI asks if my app should go live?; How do I tell my AI about a fault so it can fix it?; How do I update my app after it is live?; Can I undo what I've built, or go back to an earlier version? \(going back in the code does not take back what was written to a vault\); Who can see and use my app once it is live?; How do I change the product while a project runs?
