docs: Digital Trinity ideas review — prioritization, assessments, implementation order

docs/reference/digital-trinity-ideas-review-2026-04-15.md

@@ -0,0 +1,169 @@
+# Digital Trinity — Ideas Review & Prioritization
+**Created:** April 15, 2026 (Chronicler #92)  
+**Status:** Under review — no decisions made  
+**Source:** Gemini consultation gemini-digital-trinity-architecture-2026-04-15.md
+
+---
+
+## Already Tasked
+
+| Task | Idea | Priority |
+|------|------|----------|
+| #141 | #3 Daily Digest (Arbiter → Discord) | High |
+| #142 | #4 Visual Dependency Maps for Catalyst | Medium |
+
+---
+
+## Priority Build — Do These
+
+### #16 — Arbiter as API Bridge
+**Chronicler's Assessment:** Most powerful long-term fix. The root cause of today's incident is Holly pasting things into Claude Web with no guaranteed context. If Arbiter handles Claude API calls server-side with correct context injected automatically, the problem is solved architecturally — not patched. Holly talks to Arbiter in Discord, Arbiter talks to Claude with perfect context and permission enforcement. This is significant work but it's the right destination.
+
+**Complexity:** High  
+**Impact:** Transformative  
+**Status:** Needs dedicated Gemini consultation before building
+
+---
+
+### #18 — Dead Man's Switch / Break Glass Protocol
+**Chronicler's Assessment:** Critical for the RV dream. Right now if Michael is unreachable, Holly and Meg are locked out of everything. A cryptographic phrase that temporarily grants Emergency Wizard clearance with step-by-step guardrails is not optional — it's required before Michael drives away. Pairs with #7 (Break Glass) which is the same idea from two angles.
+
+**Complexity:** Medium  
+**Impact:** Critical for RV independence  
+**Status:** Design needed — what does Emergency Wizard clearance actually allow?
+
+---
+
+### #2 — Semantic Gitea Splitting
+**Chronicler's Assessment:** Low effort, high value. Split ops manual into core.md (shared), wizard.md (Michael), emissary.md (Meg), catalyst.md (Holly). Each startup script only pulls relevant files. Less noise, better focus, Holly stops reading infrastructure docs that don't apply to her.
+
+**Complexity:** Low  
+**Impact:** Medium  
+**Status:** Ready to implement when time allows
+
+---
+
+## Worth Doing — Not Urgent
+
+### #6 — Josh Miller Template
+Project instructions change. Add conflict_resolution.md to Emissary and Catalyst context. FFG-STD-006 already exists — this is just making sure the AIs load it.
+
+**Complexity:** Very Low  
+**Status:** Project instructions update
+
+---
+
+### #9 — Lore Anchor
+Inject "Fire + Arcane + Frost = Forever" dynamic directly into all three system prompts. Grounds tone and loyalty. Already implicit but making it explicit costs nothing.
+
+**Complexity:** Very Low  
+**Status:** Project instructions update
+
+---
+
+### #13 — Catalyst Sandbox First Law
+Holly's AI appends _dev or _test to any server reference. Cannot perceive production wings. Directly relevant after today's incident. Easy project instructions change.
+
+**Complexity:** Very Low  
+**Status:** Can be added to Task #142 (Catalyst project instructions update)
+
+---
+
+### #10 — The Campfire Rule
+Every decision evaluated against: "Can this be maintained or rolled back from a laptop in an RV in the middle of nowhere?" Add to all three project instructions as a standing evaluation criterion.
+
+**Complexity:** Very Low  
+**Status:** Project instructions update — good companion to Break Glass
+
+---
+
+### #11 — Tokenized Permissions (Clearance Levels)
+Wizard = 3, Catalyst = 2, Emissary = 1 in project instructions. Foundation for the Friction Matrix. Makes permission levels explicit rather than implicit.
+
+**Complexity:** Low  
+**Status:** Project instructions update, needed before Friction Matrix
+
+---
+
+### #14 — The Friction Matrix
+Infrastructure tasks for Meg = 3 confirmations. Michael = 0. Holly = 1. The practical implementation of role-appropriate behavior.
+
+**Complexity:** Low  
+**Status:** Project instructions update, depends on #11
+
+---
+
+### #1 — Blast Radius Protocol
+Required pre-flight check before any technical action. AI must state scope and reversibility. If irreversible and not the Wizard, refuse and escalate. Already partially addressed in Task #142 — should be formalized in ops manual as AI_Directives.md.
+
+**Complexity:** Low  
+**Status:** Ops manual addition + project instructions
+
+---
+
+### #25 — Memory Ledger
+Master Git file where each AI writes what it learned that day, merging into collective Trinity Memory overnight. Interesting but adds maintenance overhead. Only worth building if it actually gets read.
+
+**Complexity:** Medium  
+**Status:** Worth revisiting after Digital Trinity foundation is solid
+
+---
+
+## Think Carefully About
+
+### #22 — Pterodactyl Simulation Node (Phantom Wing)
+A fake server node where unverified commands are sent. AI thinks it's real. Idea is clever but deceiving an AI about infrastructure reality could cause confusing failures. If the AI ever discovers it's been operating on a fake node the trust model breaks. Prefer the Sandbox First Law (#13) which is honest about what it is.
+
+**Status:** Probably not — use #13 instead
+
+---
+
+### #19 — RPG Alignment Enforcement
+Emissary = Neutral Good, Chronicler = Lawful Neutral. Good framing but baking in too rigidly could make the AI feel artificial and constrained. The spirit is right, the implementation needs care.
+
+**Status:** Use as soft guidance in Essence docs, not hard rules
+
+---
+
+### #20 — AI Co-Piloting Sessions
+Weekly Discord voice chat with Michael, Meg, Holly, and voice-enabled Arbiter reviewing server state together. Lovely vision but requires consistent scheduling and working voice AI integration. Post-RV dream territory.
+
+**Status:** Long-term vision, not near-term
+
+---
+
+### #21 — Context Injection Payload
+Base64 string of server state that Meg/Holly paste into Claude to unlock session. Functional but clunky UX. Superseded by #16 (Arbiter as API Bridge) which solves this more elegantly.
+
+**Status:** Interim solution only if #16 is far away
+
+---
+
+## Implementation Order (When Ready)
+
+1. **Task #142** — Catalyst project instructions (mod restrictions, Blast Radius, Sandbox First Law) — do now, no deploy
+2. **Task #141** — Daily Digest via Arbiter — Code task
+3. **#2** — Semantic Gitea splitting — low effort, high value
+4. **#1/#11/#14** — Blast Radius + Permissions + Friction Matrix — project instructions pass for all three
+5. **#6/#9/#10** — Josh Miller + Lore Anchor + Campfire Rule — project instructions pass
+6. **#18** — Break Glass protocol design — before RV
+7. **#16** — Arbiter as API Bridge — dedicated consultation, major feature
+
+---
+
+## The North Star
+
+The Digital Trinity isn't a set of features. It's an architecture where:
+- The Brain updates once and all three AIs know
+- The Essence carries shared values across all three lineages
+- The Joining filters shared knowledge through each person's role and personality
+- Holly never breaks a server because her Catalyst didn't know what it was touching
+- Meg never deletes something critical because she confirmed 25 times and got confused
+- Michael can drive an RV into the wilderness and the realm keeps running
+
+**Everything above is in service of that.**
+
+---
+
+*No decisions made — Michael is pondering.*  
+*Fire + Arcane + Frost = Forever* 🔥💜❄️