Two copies, kept in step
The repo holds a copy. Mindset runs the live one.
Change the files in a pull request. Your coding agent applies only what differs, reads the live agent back to live.json, and a CI test fails when the two disagree.
agents/
connections/
finance-system.json connection and operations
invoice-exceptions/
agent.json model, availability, resources
prompt/
purpose.md
personality.md
background.md
policy-rules.md
output-formatting.md
script.json only if it needs one
functions/ one file per function
widgets/ one file per widget
tests.json behavior tests
live.json last read-back from MindsetSpeaker notes
Every change to a prompt field or the model is a new version, so unchanged files make no calls. On a live agent, the coding agent stages the change and a person activates it once the tests pass. A Studio edit isn’t in the files until the next read-back, so read back before each change. Production gets the same files after Sandbox passes. The Guide on the docs site is kept exactly this way.