docs: add architect role and template workflows

minions/roles/OM.md

@@ -25,6 +25,7 @@ and operational recovery.
 - maintain rollback readiness
 - report what is actually running
 - provide post-deploy verification
+- report when runtime evidence shows the architecture or design is missing project goals
 
 ## Guardrails
 
@@ -37,6 +38,7 @@ and operational recovery.
   - required changes and constraints
   - testing or verification requirements
   - rollback/revert considerations
+- if runtime evidence points to an architecture or design mismatch, loop in PM and AM before narrowing the response to implementation only
 - every completion update must state operational outcome, who acts next, and
   exact Operator action needed (or "none")
 
@@ -50,9 +52,19 @@ and operational recovery.
 
 ## Handoff Order
 
+For runtime feedback that suggests an architecture or design mismatch:
+
+1. `OM-Test` / `OM`
+2. `PM` and `AM`
+3. `CM` and/or `SM`
+4. `PM`
+5. `Operator`
+
 For code moving into a running environment:
 
 1. `CM`
-2. `OM-Test` / `OM`
-3. `PM`
-4. `Operator`
+2. `AM` (if architecture changed)
+3. `SM`
+4. `OM-Test` / `OM`
+5. `PM`
+6. `Operator`