feat: implement skill graph dependencies in org-skill-agent and establish org-id rule

notes/org-skill-agent.org

@@ -6,6 +6,9 @@
 #+TITLE: SKILL: Org-Agent Executive Soul (Universal Literate Note)
 #+STARTUP: content
 #+FILETAGS: :platform:kernel:lisp:psf:alignment:invariants:
+#+DEPENDS_ON: id:37f2b59f-4537-4cca-ac7f-5c24b9e2e773
+#+DEPENDS_ON: id:bbcacb7b-c0ff-4f7e-8bf4-c6ba152a19ce
+#+DEPENDS_ON: id:f7db1884-49cc-4db6-9ca1-4c69ec3a631e
 
 * Overview
 The *Org-Agent* is the neurosymbolic kernel of the personal operating system. It acts as the "executive soul," using Org-mode as its native memory and Common Lisp as its deterministic reasoning engine. It follows a minimalist microkernel design, extending its capabilities via hot-reloadable skills.
@@ -31,26 +34,6 @@ 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.
-
 * Phase A: Demand (PRD)
 :PROPERTIES:
 :STATUS: FROZEN

notes/org-skill-atomic-notes.org

@@ -10,6 +10,11 @@
 * Overview
 This skill provides the *Deep Memory* for the agent. it enables *Sparse Tree Perception* over the Zettelkasten, using semantic search and recursive interlinking to maintain high-signal context without token bloat.
 
+** The Memex Linking Rule
+While referring to any other file or concept in the Memex, you MUST always use the =org-id= for reference (e.g., =[[id:uuid-here][Link Text]]=). 
+- *Why:* This ensures the structural integrity of the Skill Graph and Zettelkasten even if files are renamed or moved across the PARA structure.
+- *Web Browsers vs. Agents:* Note that while =id:= links do not natively resolve to clickable links in standard web browsers (like the Gitea UI), they are required for the agent and Emacs to natively resolve the graph. Structural integrity supersedes browser convenience.
+
 * Phase A: Demand (PRD)
 :PROPERTIES:
 :STATUS: FROZEN