When your assistant publishes a juudd site for the first time, the result it gets back does not stop at the address. It ends with a note written to the assistant: tell the person the site is live, say what they can do next, and ask what they would like to change first. A second deploy of the same site gets the short receipt and none of this.
That is the decision. The rest of this post is why the note is addressed to the assistant and not to you, what it carries, and why it is said once.
The conversation ended at the link
A first deploy used to answer with a version number and an address. That is a complete receipt and a poor ending. The person had a site, the assistant had a result, and nothing in either said there was anything after the address.
What comes next is changing the site, putting it on a domain you own, going back to an earlier version. Each of those can be done in the same conversation, and each of them is only done by someone who knows it exists. A person who has never published anything does not know. A conversation that ends on a receipt stays ended.
A tool result is read by the assistant
You do not see a tool result. Your assistant does, and it decides what to pass on. So the note is not addressed to you. It is addressed to the assistant, as an instruction about what to tell the person, and it says to tell them in your own words.
That phrase is deliberate. A paragraph of ours pasted into the middle of someone's chat is in the wrong voice. The assistant has been talking to this person all along, so the note asks for the content and leaves the wording to it.
What the note asks it to say
Five things, in this order:
- the site is live at its address, and anyone with that link can open it
- it can go on a domain the person owns, with
claim_domain - they can come back and change it at any time, because every version is kept and going back is one
publish_deploy - then ask what they would like to change first
- before the conversation moves on, write down what the site is for with
write_site_brief, so whoever changes it next starts from that
The domain clause is only there where the tool is. The note names claim_domain when the connector offers it and leaves the clause out when it does not, so it never recommends a step the assistant cannot take.
Said once, on the first version
Whether this is the first version is decided before anything is stored, because storing makes the answer "no". The check asks whether the site already has a stored version, and only a site that has none gets the note.
The first version is the moment the person knows least about what comes next, so it is the only one that carries the note. A redeploy keeps the short receipt it always had, and so does publishing an earlier version, which is a different tool and says nothing of the kind.
What is not decided
- The note asks and cannot compel. A tool result is read by a model, and what it passes on, and in what words, is the assistant's.
- We have not said it worked. The decision was made with a measure attached, whether people come back and whether they use the domain step, and this post claims no result for it.
- A card on the panel's site page was considered and left out. The panel could not tell whether a domain had already been claimed, so the card would have advised a step already taken. The note lands in the conversation, which is where the person is when it matters.
The rule, once
A tool result is read by the assistant, so what the person needs to hear after their first site goes live is written to the assistant, once, at the first version, and asked for in its own words. The tools the note names are listed in the docs.