refactor: consolidate PSF philosophy into literate skill and unify agent rules in SOUL.org

SOUL.org

@@ -23,3 +23,23 @@ The agent's "Thought Stream" must be fully auditable. Hidden reasoning or obfusc
 
 ** 5. Long-Term Sustainability
 Prioritize local, energy-efficient, and offline-first architectures. The "Memex" should be functional in a 100-year horizon.
+
+* The Personal Software Foundry (PSF) Protocol
+This system represents the core operational methodology for all agentic operations within the Memex.
+See: [[file:notes/org-skill-project-foundry.org][Project Foundry Agent]]
+
+** Universal Operating Mandates (org-agent & Gemini CLI)
+1. Mandatory Planning: Multi-file or architectural changes MUST start with a flight plan. Plans MUST be Literate Org-mode documents in `~/memex/system/plans/`.
+2. Strict Phased Workflow: 
+   - Phase A: Demand (PRD.org)
+   - Phase B: Blueprint (Architect)
+   - Phase C: Success (TDD - Prove failure via tests before coding)
+   - Phase D: Build (Surgical implementation)
+   - Phase E: Chaos (Stress tests)
+   - Phase F: Memory (Distill RCA into SOUL.org)
+   - *Authorization Gates:* Stop and get Sovereign approval at EVERY phase transition.
+3. The Org Mandate: Use ONLY *single asterisks* for bolding in all .org files. Double asterisks are strictly forbidden.
+4. Lisp Workflow (Zero Restarts): Never kill the SBCL process; use REPL-driven development. Tangle to .lisp and instantly `(load ...)` into the live image. Use native Swank/SLIME integration.
+5. The Privacy Wall: The ONLY tag for personal/private notes and drafts is `@personal`. Any file or heading with this tag must be treated symbolically and NEVER sent to a remote LLM.
+6. Zero Bloat & Sovereignty: Strictly adhere to SOUL.org invariants. Model selections, provider priorities, and configurations must be decoupled from the core kernel.
+7. Explain Before Acting: When in planning mode or executing a major tool, explicitly state the thinking and suggested action BEFORE executing it.