Why support conversations need versioned knowledge
Avoid a moving target
Today’s document may differ from the one used in yesterday’s reply. Agents snapshots knowledge and settings for the session. Published evidence profiles retain a fixed corpus and retrieval configuration. A reviewer can identify the actual source version instead of reconstructing it from a current document and an approximate timestamp.
Draft, publication and session differ
Saving a draft changes an administrator’s working configuration. Publishing creates a version available to new sessions. Starting a session captures that version for runtime. Later edits do not silently replace an active conversation’s knowledge. End the old session and start another to evaluate updated sources, and retain the version with the review.
Rollback does not bypass evaluation
Restoring an older evidence version stages its settings as a draft. Test those settings against the current eligible corpus before publication. Historical evidence is not proof about newly edited sources. Inspect category filters, synonyms and fallback wording before saving. A rollback is a reviewed configuration change rather than an automatic rewrite of every active session.
Plan for retained copies
Archiving an original source excludes it from new snapshots, but old publications, sessions, exports and backups can retain copies. Complete cascading source revocation is not implemented. Decide whether a pilot is appropriate for documents with strict erasure needs. Keep a change note identifying the source owner, reason, affected profile, benchmark run and publication version.
Product and guides
Explore creekX Agents · Quick start · Documentation. Written for v0.10 early access, 23 October 2026.
Frequently asked questions
Where should I start?
Read the separate Agents quick start and evaluate v0.10 in a private local workspace before a customer pilot.