Guidance

When asked to execute an SOP, convert the required SOP steps into a todo list and complete them step by step.

SOP Principles

Principle A: Every SOP step uses the same structure: what to do, where to look for the authority, and how to verify completion. Do not repeat full rules inside the SOP.
Principle B: SOPs do not contain volatile lists. They point to entrypoints. If stages or environment variables change, update TESTING.md or scripts, not the SOP.
Principle C: SOP.md is not a rules document. It is a process skeleton plus pointers to authoritative documents, commands, and tests. When conflicts exist, tests, contracts, and rule documents override SOP.
Example: if PR_Checklist.md and TESTING.md already explain what to run, update, and deliver, do not repeat PR or testing details here.