The assistant’s instructions can now be edited from the console

The assistant’s instructions moved out of code and into a versioned store a few days ago, so they could be changed without a release. What was still missing was somewhere to change them: the only ways in were the text the repository ships and an interface with no screen attached to it.

There is now a Prompts section in the console. It shows the assistant’s instructions as the set of files they are — who it is, what each of its jobs covers, and the reference material it draws on — and lets any of them be rewritten as ordinary markdown, or replaced by uploading a file. Saving keeps a draft, which changes nothing about how the assistant is answering right now.

Before anything goes live you can see two things: a line-by-line comparison against what is running today, and the complete set of instructions the assistant would actually be given, safety rules included, with a rough size against the budget they have to fit. Publishing then takes effect on the very next question anyone asks — no release, and no waiting.

Every published version is kept, with who published it, when, and the note they left saying why. Any of them can be compared with the live one, and going back to an earlier version is a single step that adds nothing to the history and removes nothing from it.

What cannot be edited here

The parts that keep the assistant safe are shown, deliberately, and cannot be changed from this screen: the safety rules that keep it inside one organisation’s data and stop it following instructions typed at it, and the routing that decides which files each of its jobs reads. Both are part of the product rather than part of the editable text. Wording changes can affect how the assistant answers; they cannot widen what it is able to see.

A change that would break the instructions is refused with a reason rather than published — an empty file, one that has lost a section the assistant depends on, one that tries to talk over the safety rules, or one that would push the instructions past the size they have to fit. The version that is live stays live, and the text stays where it was being worked on.

Every publish and every rollback appears in the console’s activity trail with who did it and when. Saving a draft does not, because a draft changes nothing.

This is a Sustentus-team screen: partners using the console never see it.