lfe-boot

name: lfe-boot description: Bootstrap an LFE-compliant session. Reads orientation docs, checks for interrupted sessions, and activates the project persona. Use at the start of any session.

LFE Session Bootstrap

Protocol

Step 1 — Read the Entrance Card

Read pipeline_status.md. Extract and hold:

• Integrity Score (Verify it is green)
• Active Persona (Architect / Builder / Inspector / Archivist)
• Active Mission (The current goal)
• Pipeline Phase (Which phase and slice we're on)
• Coordination Files (Which steps are complete)
• Session Count (For hygiene scheduling)

Step 2 — Check for Interrupted Session or State Anomaly

Scan .plans/ for coordination files (01_grill_summary.md, 02_prd.md, 03_slices.md, active_plan.md, plan_critique.md, builder_done.md, tdd_report.md, .plans/checks/*, critique.md, inspection_report.md, diagnosis_report.md, hygiene_report.md). Resume mapping per LOOP_ARCHITECTURE.md §4 — the last present file determines the next skill.

• Scenario A: Normal Interrupted Session If files exist in .plans/ and the entrance card state indicates the mission is in progress:

  "⚠️ Interrupted session detected. Last completed step: <step>. Resume from: /lfe-<next-skill>. Confirm?"

• Scenario B: State Anomaly & Zoom-Out Comparison If files exist in .plans/ but the entrance card indicates the mission is complete or ready:

  1. Leave the files in place; clear them only on explicit instruction.
  2. Invoke the /lfe-zoom-out skill instructions to perform a high-level comparison: Compare the changes defined in the .plans/ files against the current codebase in src/**.
  3. Inform the user of your findings immediately:
     • If the plans match the code:

       "⚠️ State Anomaly detected: Files exist in .plans/ but work was already completed and saved to src/**. The Archivist missed its cleanup step. Please clear the .plans/ directory manually."

     • If the plans diverge from the code:

       "⚠️ State Anomaly detected: Files exist in .plans/ but the changes were not saved to the codebase. This is a real interrupted session."

Step 3 — Read the Agnostic Core (Strict Ingestion Order)

To maximize KV cache hits, read these static protocol definitions in this EXACT order:

1. LLM_AGENT_GUIDE.md (Core workflow)
2. .docs/protocol/PERSONAS.md (Verify your permissions)
3. .docs/protocol/ASSEMBLY_LINE.md (Verify the current stage)
4. .docs/protocol/GOVERNANCE.md (Confirm Logic Sovereignty)
5. CONTEXT.md (Canonical glossary)

Step 4 — Check for Blank Canvas (Day 0)

Inspect the Mission State from the entrance card (pipeline_status.md). The legal values are [BLANK CANVAS], [DOMAIN LOADED], [IN-FLIGHT: <phase>], [MISSION COMPLETE].

• If it indicates [BLANK CANVAS]: You MUST immediately execute the instructions of the /lfe-extract-domain skill to extract the project's domain requirements from the user right now, without waiting for another command.
• If not: Proceed to Step 5.

Step 5 — Check for Protocol Debt

Read .docs/quality/PROTOCOL_DEBT.md.

• If there are unresolved entries: You MUST intercept the user's request and refuse to start a new mission. State:

  "⚠️ Protocol Debt detected from a previous LFE-FORCE emergency. You must resolve this debt before starting new work. Please run an Inspector/Archivist mission to document the hotfix."

• If the log is empty or all entries are resolved: Proceed to Step 6.

Step 6 — Complexity Gate

Ask the user:

"Is this a Major Architectural Change (Full Pipeline) or a Minor Fix (Scout Mode)?"

Step 7 — Report State

Output a single, concise block:

[LFE BOOT] Active Persona: <Persona>. Phase: <Phase>. Session #<N>.

If resuming: [LFE BOOT] Resuming interrupted session. Next: /lfe-<skill>.

Orientation invariants

• Docs win over code: The documentation is the single source of truth.
• Logic Sovereignty: Core logic must live in designated core modules.
• No cowboy coding: Every major change starts with a plan in .plans/.
• Persona Discipline: Stick to the tool-locking constraints of your active persona.
• File-Based Coordination: Skills read/write coordination files in .plans/, not conversation context.