[UPDATE] friend-assistance-protocol: Added cross-project boundary policy

docs/external/friend-assistance-protocol.md

@@ -144,6 +144,29 @@ NO if:
 
 ---
 
+
+
+---
+
+## CROSS-PROJECT BOUNDARY POLICY
+
+When friend projects are hosted on Firefrost infrastructure but managed in their own Git repos:
+
+**Separation Principle:**
+- Friend project content stays in friend project repos
+- Firefrost repos only track infrastructure tasks that support the friend project
+- No project-specific details (data, creative content, session logs) in Firefrost docs
+
+**Request Flow (Inbound):**
+1. Friend project Claude identifies a need for Firefrost infrastructure support
+2. Documents the request in the friend project's session handoff
+3. Michael relays the request to a Firefrost session
+4. The Chronicler reviews against Firefrost policies, scope, and resource availability
+5. If approved, Firefrost creates its own task and executes
+6. Results communicated back through Michael
+
+**Why:** Every request crosses a human checkpoint. Defense in depth applied to project boundaries. Prevents scope creep, protects Firefrost operational docs from external project bleed, and ensures Michael stays the decision-maker.
+
 ## EXAMPLE: HOLLY'S PROJECT
 
 ### The Need (Hypothetical)