01
Name the surface.
Describe the model, instruction, tool, source, permission, evaluation, approval route, monitor, or containment path that differs.
MATERIAL CHANGE / REVIEWABLE RECORD
A change is part
of the system.
When a model, instruction, source, tool, permission, or monitor changes, the operating boundary changes with it. Leave a record another person can inspect.
01 CHANGE02 RE-CHECK03 PAUSE04 RETURN
OPERATING BOUNDARY A record makes a change reviewable. It does not approve, authorize, certify, or make a system safe.
Read the limitsTHE CHANGE RECORD
Not every revision needs a committee.
Every material revision needs a trail.
02
Name the decision.
Identify the accountable person or role and their decision right. A model or workflow is never the accountable owner.
03
Re-check the difference.
State the narrow evidence or review appropriate to this change. A passing check is not a general safety or compliance claim.
04
Watch for the pause.
Name what should be observed after the change and the condition that requires accountable human review before continuing.
05
Keep a return path.
Define a feasible rollback or containment route, the prerequisites, and who can initiate it before calling the change complete.
FICTIONAL WALKTHROUGH / NO INPUT COLLECTED
Three changes.
Three different questions.
These prewritten examples illustrate the record’s shape. They cannot assess a system, capture a visitor’s data, or recommend a release.
FICTIONAL CASE / 01
Version update, same stated task.
A drafting assistant moves to a new model version while retaining the same reader-facing task and action boundary.
- CHANGED SURFACE
- Model version and its observable output behavior.
- RE-CHECK
- Compare a defined, sanitized prompt set against the previous version; inspect factual citations and instruction adherence.
- PAUSE CONDITION
- Pause if a reviewer observes unsupported citations, a material instruction conflict, or a difference that affects a stated boundary.
- RETURN PATH
- Route the workflow to the previous approved configuration while the accountable owner reviews the evidence.
START WITH THE RECORD
Keep the record
where the change can be found.
The template is ordinary Markdown. Use it in a repository, a change-review package, or any approved documentation system. The included validator checks that a record retains its required sections and avoids a small set of assurance phrases; it does not judge the quality of the decision.
AI CHANGE RECORDSTATUS / PROPOSED
01 / CHANGE STATEMENT
Describe the before/after difference.
02 / AFFECTED SURFACE
Model, tool, source, permission, monitor, or return path.
03 / ACCOUNTABLE DECISION
Name the person or role and decision right.
04 / RE-CHECK + PAUSE
State evidence, an observable condition, and the point to stop.
05 / RETURN + OPEN QUESTIONS
Define containment and what still needs an answer.
NOT
APPROVAL
APPROVAL
LIMITS / READ BEFORE USE
A trail is not
a permission slip.
Use this utility to make a change legible. Do not use it to decide whether a change is lawful, safe, secure, fair, compliant, or appropriate for a high-stakes context. The record should surface the point where qualified review or accountable escalation is necessary.
What should trigger escalation?
Escalate when a change affects sensitive data, protected or consequential decisions, safety-critical activity, security boundaries, legal or contractual obligations, people outside the operating team, or any system where no accountable owner and return path can be named.
METHOD BASIS / NOT A COMPLIANCE MAPPING