AI Change Control

Prompt and skill edits are code changes with production impact, and they are routinely made without any of the controls a code change would attract — no review, no staging, no rollback plan, no record of what changed. The justification is that they are text, which is also true of most configuration that has caused outages. Change control means an edit is proposed, reviewed by someone accountable, staged against known cases, released deliberately and revertible afterwards. The cost is small; the alternative is a production behaviour change nobody can attribute.

Skills carry owners and review cadences as fields on the record, and version history makes reversion a matter of restoring a prior version. Because the Interaction Log ties each execution to the skills and prompt that governed it, a behaviour change reported by users can be matched to the specific edit that caused it rather than investigated from the output alone.