REUSABLE AI WRITING INSTRUCTION CHANGE CARD Use this card before adding, removing, or rewriting a permanent instruction. The purpose is to fix recurring problems without turning a reusable instruction set into a record of one-off edits. ============================================================ 1. CURRENT INSTRUCTION ============================================================ Instruction name or layer: ____________________________________________________________ Current instruction: ____________________________________________________________ ____________________________________________________________ Current version: ____________________________________________________________ Current owner: ____________________________________________________________ ============================================================ 2. OBSERVED PROBLEM ============================================================ What happened? ____________________________________________________________ ____________________________________________________________ How often has the problem occurred? [ ] Once [ ] More than once [ ] Recurring [ ] Frequency is not yet known Examples or outputs reviewed: ____________________________________________________________ ____________________________________________________________ Is the problem material enough to justify a permanent change? [ ] Yes [ ] No [ ] Test first ============================================================ 3. WHICH LAYER OWNS THE PROBLEM? ============================================================ [ ] Stable core [ ] Job module [ ] Source rule [ ] Output contract [ ] Exception rule [ ] Assignment packet [ ] Workflow or human decision [ ] Not yet clear Why does this layer own the problem? ____________________________________________________________ ____________________________________________________________ Does this belong in reusable instructions at all? [ ] Yes [ ] No [ ] Test first If no, where should it move? [ ] Current sources [ ] Assignment packet [ ] Workflow control [ ] Human approval or decision [ ] Other: __________________________________________________ ============================================================ 4. PROPOSED CHANGE ============================================================ Proposed instruction: ____________________________________________________________ ____________________________________________________________ What behavior should change? ____________________________________________________________ What behavior should remain unchanged? ____________________________________________________________ Does another instruction already control this behavior? [ ] No [ ] Yes If yes, identify the instruction: ____________________________________________________________ Could the proposed change conflict with another rule? [ ] No [ ] Yes [ ] Not sure Possible conflict: ____________________________________________________________ ============================================================ 5. SWAP TEST ============================================================ Would the proposed instruction still make sense if today's assignment were replaced with a different assignment in the same job family? [ ] Yes [ ] No [ ] Only under these conditions: ____________________________________________________________ If no, move the requirement to changing sources or the assignment packet instead of the reusable instruction set. ============================================================ 6. THREE-ASSIGNMENT TEST ============================================================ Keep the stable core unchanged. Test the proposed instruction on three different assignments within the same job family. ASSIGNMENT 1 Description: ________________________________________________ Result: _____________________________________________________ Manual repair required: _____________________________________ ASSIGNMENT 2 Description: ________________________________________________ Result: _____________________________________________________ Manual repair required: _____________________________________ ASSIGNMENT 3 Description: ________________________________________________ Result: _____________________________________________________ Manual repair required: _____________________________________ Did the change fix the original problem? [ ] Yes [ ] Partly [ ] No Did the change create a new problem? [ ] No [ ] Yes If yes, describe it: ____________________________________________________________ Did the change encourage any of these failures? [ ] Hidden missing information [ ] Unsupported factual claims [ ] Ignored source conflict [ ] Changed quotation, date, commitment, limitation, or qualification [ ] Unauthorized sending, publishing, approval, or record update [ ] Other: __________________________________________________ ============================================================ 7. FINAL DECISION ============================================================ [ ] ADOPT The change fixed a recurring problem without creating an unacceptable new failure. [ ] REVISE AND RETEST The direction is useful, but the wording or ownership is not yet stable. [ ] REJECT The change did not solve the problem or created a worse one. [ ] MOVE TO ASSIGNMENT PACKET The requirement changes with the assignment. [ ] MOVE TO SOURCE RULES The issue concerns current evidence, missing facts, or source use. [ ] KEEP HUMAN-LED The decision should not be delegated through instructions. [ ] HANDLE IN THE WORKFLOW The issue is review, approval, handoff, logging, or publication. Decision evidence: ____________________________________________________________ ____________________________________________________________ New version: ____________________________________________________________ Change summary: ____________________________________________________________ Change owner: ____________________________________________________________ Effective date: ____________________________________________________________ Review date: ____________________________________________________________ RULE TO REMEMBER Change the instructions when the system changed. Change the inputs when the assignment changed.