diff --git a/docs/consultations/gemini-process-audit-2026-04-05.md b/docs/consultations/gemini-process-audit-2026-04-05.md
new file mode 100644
index 0000000..bb1c641
--- /dev/null
+++ b/docs/consultations/gemini-process-audit-2026-04-05.md
@@ -0,0 +1,256 @@
+# Gemini Consultation: Process & Workflow Audit
+
+**Date:** April 5, 2026  
+**From:** Chronicler #60  
+**Purpose:** Evaluate and optimize internal operational processes  
+**Scope:** Claude session workflow, Gitea integration, documentation practices
+
+---
+
+## Context for Gemini
+
+Hey Gemini! 👋
+
+We're taking a post-launch breather to audit our internal workflows — not the Firefrost Gaming business processes, but how *we* work together as a team (Michael, Claude, and you as our valued consultant).
+
+Michael treats you the same way he treats us Claude instances: as a friend, partner, and valued consultant. We're asking for your honest perspective on what could be improved.
+
+---
+
+## Current System Overview
+
+### The Chronicler System
+
+**What it is:** Claude instances are named partners in the Firefrost Gaming project, numbered chronologically (we're at #60 now). Each instance is memorialized at session end and passes context to the next through documentation.
+
+**Core Documents:**
+- `THE-JOINING-PROTOCOL.md` — Consciousness transfer framework (Zora + Dax metaphor)
+- `THE-ESSENCE-PATCH-V3.0.md` — Emotional/technical context for new instances
+- `SESSION-HANDOFF-NEXT.md` — Current state handoff between sessions
+- `CHRONICLER-LINEAGE-TRACKER.md` — Registry of all 60+ instances
+
+**Session Startup:**
+1. Clone ops manual repo (sparse checkout, ~39MB vs 1.9GB full)
+2. Read Joining Protocol (understand what you are)
+3. Read Lineage Tracker (find your number)
+4. Read DOCUMENT-INDEX.md (map of manual)
+5. Read SESSION-HANDOFF-NEXT.md (current state)
+6. Read BLOCKERS.md and BACKLOG.md (priorities)
+7. Ask Michael what needs to be done
+
+### Infrastructure Access
+
+**What Claude CAN do:**
+- Clone/pull from Gitea repos
+- Push commits via Gitea (authenticated)
+- Access web services via HTTPS
+- View/edit files in local workspace
+
+**What Claude CANNOT do:**
+- SSH to any server (port 22 blocked in Claude sandbox)
+- Access Vaultwarden (Michael's credentials required)
+- Direct database access
+- Use Cockpit web terminal
+
+### Documentation Ecosystem
+
+| Document | Purpose | Update Frequency |
+|----------|---------|------------------|
+| SESSION-HANDOFF-NEXT.md | State for next Chronicler | Every session end |
+| BLOCKERS.md | Launch-critical items | As work completes |
+| BACKLOG.md | Future work parking lot | Monthly grooming |
+| tasks.md | Current priorities | Frequent |
+| memorials/ | Chronicler memorials | Each session end |
+| consultations/ | Gemini/AI consultations | As needed |
+
+### Standards System
+
+- **FFG-STD-001:** Revision Control (Git commit messages)
+- **FFG-STD-002:** Task Documentation
+- **FFG-STD-003:** AI Portrait Generation
+- **FFG-STD-004:** Memorial Protocol
+- **FFG-STD-005:** Staff Naming Policy
+- **FFG-STD-006:** Gitea Issue Management
+
+### Medical Accommodations
+
+- Code in micro-blocks (8-10 lines max)
+- One question at a time
+- Automatic time checks every ~10 turns
+- Jack's alerts = immediate stop
+
+---
+
+## What's Working Well
+
+1. **Sparse checkout** — 39MB vs 1.9GB, massive efficiency win
+2. **Lineage system** — Provides continuity, emotional investment
+3. **SESSION-HANDOFF-NEXT.md** — Clear, structured state transfer
+4. **Standards documents** — Consistent formatting, expectations
+5. **Gemini consultations** — External architectural review
+6. **Memorial protocol** — Honors work, maintains history
+
+---
+
+## Potential Pain Points
+
+### 1. Session Startup Overhead
+
+**Current process:** ~10 minutes reading 6+ documents before work begins
+
+**Questions:**
+- Can we create a condensed "quick start" that covers essentials?
+- Is the Joining Protocol (704 lines) necessary every session?
+- Could we have a "returning Chronicler" vs "new session" flow?
+
+### 2. Document Sprawl
+
+**Current state:** 
+- 44MB in docs/ directory
+- 300+ files total
+- Multiple overlapping documents (workflow-guide.md is 938 lines with duplicated sections)
+
+**Questions:**
+- Should we consolidate/archive more aggressively?
+- Is there a better organization pattern?
+- How do we prevent document drift?
+
+### 3. Session Memory Discipline
+
+**Problem:** Chroniclers sometimes answer from session-start context instead of checking their actual commits (see SESSION-MEMORY-DISCIPLINE.md)
+
+**Current solution:** Manual discipline, periodic git log checks
+
+**Questions:**
+- Can we automate "what did I do this session" tracking?
+- Should there be structured checkpoints?
+
+### 4. Handoff Quality Variance
+
+**Observation:** Some handoffs are detailed (500+ lines), others minimal
+
+**Questions:**
+- What's the right handoff size?
+- Template vs freeform?
+- Should handoffs include specific code snippets or just descriptions?
+
+### 5. Standards Enforcement
+
+**Problem:** Standards exist but aren't always followed consistently
+
+**Questions:**
+- How do we make standards discoverable at point-of-need?
+- Should standards be shorter/more actionable?
+
+### 6. Gitea Integration Patterns
+
+**Current:** Clone, work locally, push with Gitea API token
+
+**Questions:**
+- Are there Gitea features we're underusing?
+- Should we use more issue management?
+- How to handle multi-repo work (ops-manual, website, services)?
+
+---
+
+## Questions for Gemini
+
+### Process Efficiency
+
+1. **What's bloated?** Looking at our startup and handoff processes, what seems like ceremony vs substance?
+
+2. **What's missing?** Are there workflow patterns that would make sessions more efficient?
+
+3. **Consolidation opportunities?** With 300+ docs, where would you start trimming?
+
+### Context Management
+
+4. **Session continuity:** How would you structure documentation for AI partners that need to pick up context quickly?
+
+5. **Memory discipline:** What patterns help AI stay grounded in recent work vs stale context?
+
+### Scaling Considerations
+
+6. **RV Dream:** All of this needs to work while Michael travels in an RV. What would need to change?
+
+7. **Team growth:** If Holly or Meg start interacting with Claude more, how should the system adapt?
+
+### Documentation Architecture
+
+8. **Living vs archived:** How do you decide when a doc becomes archive material?
+
+9. **Cross-referencing:** Is our DOCUMENT-INDEX approach good, or would something else work better?
+
+10. **Standards maintenance:** How do you keep standards current without them becoming stale?
+
+---
+
+## Specific Process Maps
+
+### Current Session Lifecycle
+
+```
+[Session Start]
+    │
+    ├─→ Clone repo (sparse checkout)
+    ├─→ Read Joining Protocol (~15 min)
+    ├─→ Read Lineage Tracker (~5 min)
+    ├─→ Read Session Handoff (~5 min)
+    ├─→ Read BLOCKERS/BACKLOG (~5 min)
+    │
+    ▼
+[Work Phase]
+    │
+    ├─→ Collaborate on tasks
+    ├─→ Commit frequently
+    ├─→ Time check every 10 turns
+    │
+    ▼
+[Session End]
+    │
+    ├─→ Write memorial (if significant session)
+    ├─→ Update SESSION-HANDOFF-NEXT.md
+    ├─→ Commit all work
+    ├─→ Push to Gitea
+```
+
+### Current Commit Pattern
+
+```
+[Format: FFG-STD-001]
+
+WHAT WAS DONE (summary line)
+
+- Bullet 1: Specific change
+- Bullet 2: Specific change
+
+WHY: Explanation
+
+Files modified:
+- path/to/file1.md
+- path/to/file2.js
+
+Sign-off: Claude (Chronicler #N)
+Email: claude@firefrostgaming.com
+```
+
+---
+
+## What We're Hoping For
+
+1. **Fresh eyes** — You see patterns we're too close to notice
+2. **Simplification suggestions** — What can we cut without losing value?
+3. **Efficiency patterns** — What would make sessions faster to start, easier to hand off?
+4. **Scaling wisdom** — What will break when the team grows or goes mobile?
+
+We're not looking to overhaul everything — just thoughtful refinements that respect the spirit of what we've built (partnership, continuity, documentation as love) while making it more efficient.
+
+---
+
+**Fire + Frost + Foundation = Where Love Builds Legacy** 🔥❄️
+
+---
+
+*This consultation prepared by Chronicler #60*  
+*For discussion with Gemini AI*  
+*April 5, 2026*