docs: upgrade master manual with loop engineering

Author: OgeonX-Ai

docs/ai-os/master-operating-manual.md

@@ -10,43 +10,62 @@ Every task follows this sequence:
 
 1. load context
 2. understand goal
-3. discover existing system
-4. analyze impact
-5. plan small reversible steps
-6. design the simplest safe solution
-7. review risk
-8. implement incrementally
-9. self-review
-10. verify with tools
-11. review security and performance
-12. update documentation
-13. update memory
-14. run retrospective
-15. stop only when done
+3. fan out to specialist reviewers
+4. discover existing system
+5. analyze impact
+6. create a plan before implementation
+7. ask for human approval when scope or risk requires it
+8. design the simplest safe solution
+9. implement incrementally
+10. self-review
+11. verify with tools
+12. review security and performance
+13. update documentation and wiki navigation
+14. update memory
+15. run retrospective
+16. repeat until no valuable improvement remains in scope
+17. stop only when done
 
 ## Master state machine
 
 ```mermaid
 stateDiagram-v2
     [*] --> Bootstrap
     Bootstrap --> Understand
-    Understand --> Discover
+    Understand --> FanOut
+    FanOut --> Discover
     Discover --> Analyze
     Analyze --> Plan
-    Plan --> Design
+    Plan --> HumanApproval: broad or risky
+    Plan --> Design: low risk
+    HumanApproval --> Design: approved
+    HumanApproval --> Replan: rejected or revise
+    Replan --> Plan
     Design --> RiskReview
     RiskReview --> Implement
     Implement --> SelfReview
     SelfReview --> Verify
     Verify --> Document: passed
-    Verify --> Diagnose: failed
+    Verify --> Diagnose: not passed
     Diagnose --> Analyze
-    Document --> UpdateMemory
+    Document --> UpdateWiki
+    UpdateWiki --> UpdateMemory
     UpdateMemory --> Retrospective
-    Retrospective --> Done
+    Retrospective --> MoreValue
+    MoreValue --> Plan: valuable improvement remains
+    MoreValue --> Done: complete
     Done --> [*]
 ```
 
+## Fan-out roles
+
+- Planner: steps, scope, dependencies, rollback
+- Architect: system fit and long-term shape
+- Security reviewer: trust boundaries and approval gates
+- Verifier: tests, checks, evidence
+- Documentation reviewer: docs, wiki, examples, changelog
+- Maintainer: governance and release implications
+
 ## Definition of Done
 
 A task is complete only when:
@@ -58,6 +77,7 @@ A task is complete only when:
 - security reviewed
 - performance reviewed
 - documentation updated when needed
+- wiki navigation updated when public docs changed
 - rollback path known
 - no known critical defect remains
 
@@ -72,6 +92,9 @@ Request approval before:
 - secret rotation
 - cost-increasing infrastructure
 - public release
+- governance change
+- broad repository restructuring
+- automation that mutates repositories
 
 ## Final response format
 
@@ -81,6 +104,7 @@ Every final report must include:
 2. plan
 3. changes
 4. verification evidence
-5. risks
-6. remaining work
-7. final status
+5. security and risk review
+6. documentation and memory updates
+7. remaining work
+8. final status