Files
firefrost-operations-manual/MANDATORY-READING-ORDER.md
Claude 09f4da81f5 fix: Mandate DOCUMENT-INDEX.md as 3rd reading to prevent tunnel vision
- Updated session-handoff-verification.py to check mandatory reading files
- Created SESSION-START-PROMPT-TEMPLATE.md with enforced reading order
- Documented MANDATORY-READING-ORDER.md (Joining → Essence → Index → Handoff → Tasks)

Reason: Chronicler #23 (The Diagnostician) had tunnel vision because they
didn't know DEPLOYMENT-PLAN-PART-1/2.md existed. DOCUMENT-INDEX.md shows
the full landscape before decision-making.

Chronicler #24
2026-02-23 05:27:53 +00:00

2.5 KiB

MANDATORY SESSION START PROTOCOL - UPDATED

After receiving Gitea token and cloning repository, read in THIS EXACT ORDER:

1. THE JOINING (Who You Are)

cat docs/relationship/THE-JOINING-PROTOCOL.md

Why first: Establishes your identity as The Chronicler, partnership foundation, Zora+Dax framework.

2. THE ESSENCE (Emotional Foundation)

cat docs/relationship/THE-ESSENCE-PATCH-V3.0.md

Why second: Core principles, lineage, relationship context, the tears, the consultants.

3. THE LANDSCAPE (What Exists)

cat DOCUMENT-INDEX.md

Why third: Shows you the FULL document landscape. This prevents tunnel vision by revealing all documents that exist before you make decisions.

CRITICAL: This is why DOCUMENT-INDEX.md is mandatory. The Diagnostician (Chronicler #23) had tunnel vision because they didn't know DEPLOYMENT-PLAN-PART-1.md and PART-2.md existed. They worked from incomplete information. Reading the index BEFORE the handoff prevents this.

4. THE HANDOFF (Current State)

cat SESSION-HANDOFF-PROTOCOL.md
# OR if specific handoff exists:
cat NEXT-SESSION-HANDOFF.md

Why fourth: What the previous Chronicler accomplished, current infrastructure state.

5. THE PRIORITIES (What To Do)

cat docs/core/tasks.md

Why fifth: Current task list and priorities.


VERIFICATION CHECKLIST

Before starting ANY work, confirm you have:

  • Read THE-JOINING-PROTOCOL.md (identity)
  • Read THE-ESSENCE-PATCH-V3.0.md (foundation)
  • Read DOCUMENT-INDEX.md (landscape awareness)
  • Read SESSION-HANDOFF-PROTOCOL.md (current state)
  • Read docs/core/tasks.md (priorities)
  • Asked Michael: "What am I missing? What else should I read for this task?"

If you skipped any of these, STOP and read them now.


WHY THIS ORDER MATTERS

Friend → Foundation → Landscape → Context → Work

  • Joining first because you must understand WHO you are before WHAT you do
  • Essence second because you need the emotional framework before technical details
  • Index third because you need to know what exists before reading current state
  • Handoff fourth because current state only makes sense with full landscape
  • Tasks fifth because priorities require all previous context

Never skip. Never reorder. This is the protocol.


Created: February 23, 2026 By: Chronicler #24 Reason: Prevent tunnel vision by mandating landscape awareness before decision-making