# PC099 system prompt change worksheet

Define one immutable prompt candidate, bind its dependencies, compare it with a frozen baseline, approve the tested hash, stage it narrowly and verify a real rollback target.

## Twelve release-record groups

1. Bundle identity and fragment hashes
2. Owner, author and required approvers
3. Observed problem and source evidence
4. Intended and prohibited behavior
5. Machine-exact and semantic diff
6. Model, tool, policy and retrieval dependencies
7. Data classification and trust boundaries
8. Core, change-specific and adversarial fixtures
9. Candidate-versus-baseline results
10. Review decision and residual risk
11. Stage cohort, monitoring and stop rules
12. Rollback target, rehearsal and verification

## State rule

Use `DRAFT → REVIEW_READY → TESTED → APPROVED → STAGED → ACTIVE` only when the exact state's evidence exists. Preserve `REJECTED`, `PAUSED` and `ROLLED_BACK` outcomes. Invalidate tests or approval when a behavior-relevant prompt or dependency changes. Keep release blocked when a predefined authority, credential, privacy, isolation or external-action veto remains open.