DM-011: Session 10 — Operational Gaps Resolved
Lakes of Fire 2026 Group Playbook
Date: April 21, 2026 Session: 10 Trigger: User-initiated continuation; three operational gaps identified after Session 9 completion
Context
Session 9 declared the playbook complete and the build queue empty. Session 10 was triggered by user continuation request. Three genuine gaps were identified that the prior playbook did not address:
- Night navigation and lighting — particularly relevant given the new raw site terrain (rolling hills, cedar swamps)
- Group communication plan — cell coverage unreliable at rural Michigan sites; 3-person group needs a zero-tech coordination protocol
- Matt's participation path — the DJ-without-rig situation finalized in Session 9 needed to be absorbed into a practical plan, not just a constraint note
All three were produced this session.
Decisions
Night Navigation and Lighting (NIGHT-NAV-lighting-guide.md)
Keep: - Three-layer lighting framework: personal navigation (headlamp per person), camp landmark (Matt owns), personal wearable lighting - Red-light mode norm acknowledged (burn culture awareness) - First-night 10-minute landmark orientation walk as required camp protocol - Specific responsibility assignments per layer
Standardize: - Each person owns their own headlamp — no sharing - Matt owns camp LED string and flag/landmark design - Flag color/design chosen before the event (not decided on-site)
Confidence: High. New raw site with no ambient infrastructure makes personal lighting non-negotiable. Cedar swamp + rolling terrain makes navigation errors genuinely risky.
Next action: Add headlamps, LED string, camp flag, LED bracelets to PACKING-framework.md (update separately if needed; flagged in memo).
Group Communication and Connectivity (COMMS-group-connectivity-plan.md)
Keep: - Camp-as-home-base as primary coordination method (zero-tech, always works) - 7 PM evening check-in rhythm as the critical daily anchor - Physical notepad at camp for departure notes - Offline maps downloaded before event for each person - FRS walkie-talkie pair recommended (Developer or Matt procures)
Standardize: - Meeting point at Center Camp equivalent (finalize when site map released, June–July) - Lost-person protocol: Camp → common areas → Rangers - Developer identifies Ranger HQ location on Day 1 (already in DM-010 protocol; confirmed here)
Confidence: High. Cell reliability at rural Michigan events is consistently low; the zero-tech fallback stack is the correct design.
Next action: Developer procures 1 pair FRS walkie-talkies. Each person downloads offline maps before July 14.
Matt's Participation Path Without a DJ Rig (SOUND-matt-dj-without-rig.md)
Keep: - Five redirected participation modes: Expert Listener, Camp Sound Curator, Connector/Collaborator, 2027 Reconnaissance, Infrastructure Leadership (existing) - Camp Bluetooth speaker = Matt's domain for camp ambiance - Honest psychological acknowledgment: the gap is real; the response is to play the hand as dealt - 2027 theme camp = revisit in fall 2026, not 2026 planning
Standardize: - Camp playlist / morning/dinner ambiance = Matt owns - Developer communicates the "2027 reconnaissance" reframe when sending the theme camp update to Matt
Confidence: High. The sound permit situation is resolved; the participation reframe is practical and honest.
Next action: Developer uses this memo's framing when communicating with Matt about the theme camp decision (if not already communicated).
Session 10 Summary — What Changed from Session 9
| Area | Before Session 10 | After Session 10 |
|---|---|---|
| Night navigation | Not addressed | Three-layer framework with responsibility assignments |
| Group communication | No protocol | Zero-tech stack: camp home base, 7 PM check-in, notepad, FRS radio |
| Matt's participation | Constraint noted (no rig) | Practical participation path with five modes |
What Is Still Genuinely Undone
Site map (expected June–July 2026): - Campsite selection notes cannot be finalized until the Luther site map is released - Meeting point for COMMS plan needs to be confirmed against the actual site layout - SITE-arrival-new-luther-MI.md may need a minor update once site map is available
Post-lottery confirmation: - If any group member does not receive a ticket via the lottery (opening April 20), an alternative plan is needed. The playbook assumes all three people attend. If the group is incomplete, the ops model (particularly Matt's logistics role) needs adjustment. This is a revisit trigger, not a planning gap to fill now.
Playbook Status After Session 10
Completed artifacts: 39 files - Session 10 adds: NIGHT-NAV-lighting-guide.md, COMMS-group-connectivity-plan.md, SOUND-matt-dj-without-rig.md, DM-011
True remaining triggers for Session 11: 1. Site map released (June–July) → campsite selection notes update 2. Lottery results confirmed → adjust ops model if group incomplete 3. Group member raises a specific gap not covered by the playbook 4. Significant event rule change from org
Otherwise: playbook is done.
Decision Memo Standard Close
| Item | Decision |
|---|---|
| Night nav lighting framework | Keep — standardize per roles |
| Group communication zero-tech stack | Keep — standardize |
| FRS walkie-talkie pair | Keep — Developer or Matt procures |
| Matt's rig-free participation path | Keep — five modes standardized |
| 2027 theme camp planning | Revisit fall 2026 |
| Site map integration | Revisit when released (June–July 2026) |
| Lottery outcome contingency | Revisit if any member does not receive ticket |