Prompt Version Control

Prompts are operational logic, and logic without history cannot be audited. When a prompt is edited in place — a phrase softened, a constraint added, a model swapped — every answer produced before the edit was produced under different rules, and nothing in the output records which version applied. Investigations then rely on memory. Version control makes the question answerable: given a date, the instruction set can be reconstructed, and given an answer, the governing wording can be identified. It also makes rollback possible, which matters because prompt changes have non-obvious blast radius and a regression may not surface for weeks.

Prompts and skills are records in the organization's own SQL environment, so they carry version history in the same way content does. The Prompts and Skills registries expose current state as live feeds, and the Interaction Log ties each execution to the skills and prompt that governed it, so a past answer can be matched to a past configuration rather than to a recollection of one.