choosing-what-to-control

Change control identifies which code, prompts, models, and tools require an approved state to prevent drift and untracked power. It solves the problem of unmanaged configuration changes affecting release readiness and trust.

Track configuration drift by documenting ownership, current state, intended state, evidence links, and re-check triggers for each controlled item. This produces a controlled-item list that maintains auditable change histories and guides escalation.

Identify controlled items by evaluating whether their state affects trust, agent power, releases, repeatability, or public understanding. Scope covers code, prompts, models, tools, dependencies, docs, tests, evals, releases, and claims.

Document ownership and evidence by specifying each controlled item's owner, current state, intended state, and re-check trigger. This produces a controlled-items.md file and supports escalation when drift could impact users, security, or releases.

Yes, this approach manages changes across code, prompts, models, tools, dependencies, docs, tests, evals, releases, and claims. It identifies any items whose state affects trust, agent power, releases, repeatability, or public understanding.

Escalate configuration drift when it could impact users, security, or releases. The controlled-item list includes re-check triggers that guide escalation when the current state deviates from the intended approved state.