Versioning makes your trained AI available to users. Each version is an immutable snapshot of your AI’s complete configuration at a point in time, including guidance, tools, and knowledge. You can continue editing while users interact with a stable, deployed version.
Core Concepts
Profiles
A profile is your AI’s current working configuration: guidance instructions, tool settings, LLM parameters, and audience rules. You edit profiles at any time, then “build” to save everything into a new version.
Versions
Versions are sequentially numbered snapshots (#1, #2, #3). Each captures the full profile configuration plus a knowledge snapshot of all data provider sources at build time. Versions are immutable. Once built, they never change.
Aliases
An alias is a named pointer to a specific version. The Production alias represents what users see. All channels connect to aliases, not directly to versions. When you update an alias from version #12 to #13, every channel switches immediately.
Building and Deploying
- Edit your profile: update guidance, add knowledge, enable tools
- Test using the preview in Behavior → Guidance, or run test suites
- Build via Behavior → [Review your changes]
Build options:
| Option | Effect |
|---|
| Build Version, Set Active | Creates version and deploys to all channels immediately |
| Build Version | Creates version without deploying. Set active later via Behavior → General → Versions |
“Build Version, Set Active” deploys to all connected channels immediately. Test thoroughly before using this for significant changes.
Rolling Back
If a deployment causes issues, roll back by setting a previous version as active:
- Go to Behavior → General → Versions
- Click ⋮ next to the previous good version
- Select Set as Active
All channels revert immediately. The problematic version remains in your history for review.
Knowledge Snapshots
Each version freezes your knowledge sources at build time. When data providers sync new content, you see an orange indicator prompting you to rebuild. Schedule regular builds (weekly, monthly) based on how often your content changes.
Knowledge updates don’t reach users until you build a new version. If your data providers sync frequently, rebuild regularly to keep the AI current.
