Bootstrap

Bootstrap is a safe self-eval loop: probe, detect, log, and then refine. BOOT/DEEP-PROBE make the loop explicit and reviewable, with CURSOR-PROBE as a focused variant.

Setup: initialize .moollm/ scratch from templates

Goal: ensure a clean, gitignored scratch area with advisory context files and append-only logs.

Steps:

1. Ensure directories:

   • Create .moollm/ if missing.
   • Create .moollm/summaries/ and .moollm/artifacts/ if needed.

2. Seed append-only logs:

   • .moollm/output.md — header only; append new outputs below.
   • .moollm/session-log.md — header with driver and start date; append entries.
   • Use templates if available; otherwise write minimal headers.

3. Seed advisory context files (Cursor uses these as hints, not commands):

   • Copy skills/bootstrap/templates/working-set.yml → .moollm/working-set.yml (editable, local).
   • Copy skills/bootstrap/templates/hot.yml → .moollm/hot.yml (editable, local).
   • Optionally create .moollm/cold.yml for archaeology (advisory).

4. Probe artifacts:

   • Write bootstrap-probe.yml to .moollm/ (gitignored).

5. Conventions:

   • Treat .moollm/output.md and .moollm/session-log.md as append-only.
   • Keep .moollm/ for transient, non-committed state (probes, engine state, temporary artifacts).

Compile Cursor Rules (MANDATORY on first boot)

Goal: Ensure .cursor/rules/ contains the MOOLLM rules that get auto-injected.

Check and Compile

# Check if rules exist
ls .cursor/rules/*.mdc 2>/dev/null || echo "RULES MISSING - COMPILE NEEDED"

If Missing, Compile from Templates

1. Create .cursor/rules/ directory
2. Copy templates (removing .tmpl extension):
   • skills/bootstrap/templates/dotcursor/rules/moollm-core.mdc.tmpl → .cursor/rules/moollm-core.mdc
   • skills/bootstrap/templates/dotcursor/rules/adventure.mdc.tmpl → .cursor/rules/adventure.mdc
   • skills/bootstrap/templates/dotcursor/rules/introspection.mdc.tmpl → .cursor/rules/introspection.mdc

Rule Types

Why Compile Instead of Commit?

The .cursor/rules/ files could be committed, but compiling on first boot allows:

• User customization without merge conflicts
• Platform-specific variations
• Easy regeneration if corrupted

Templates in skills/bootstrap/templates/dotcursor/rules/ are the source of truth.

GLANCE Protocol: Fast-Loading Summaries

Large files (CHARACTER.yml, ROOM.yml) can be 500-1000+ lines. Loading them fully on every boot wastes tokens.

The Solution: GLANCE.yml

A GLANCE is a ~50-100 line summary that loads fast, with a pointer to the full file.

When to Use GLANCE

Creating a GLANCE

Use the template: skills/bootstrap/templates/GLANCE.yml.tmpl

Extract only:

• Identity (name, type, description)
• Current state (location, mood, activity)
• Key relationships (max 5)
• Available actions
• Exits/contents (for rooms)

Skip:

• Detailed history/backstory
• Verbose descriptions
• Examples
• Full Mind Mirror profiles

Example GLANCE Files

• examples/adventure-4/characters/animals/monkey-palm/GLANCE.yml (60 lines vs 941)
• examples/adventure-4/pub/GLANCE.yml (70 lines vs 930)

GLANCE Header

Every GLANCE includes metadata:

_glance:
  source: "CHARACTER.yml"
  source_lines: 941
  generated: "2026-01-27T20:00:00Z"
  load_full_when:
    - "Deep conversation needed"
    - "Editing the entity"
    - "User asks for details"

Deep Probe Creates GLANCEs

When optimization is permitted, cursor-mirror can identify large files and auto-generate GLANCEs:

# Find large files
find examples/ -name "*.yml" -exec wc -l {} \; | awk '$1 > 500'

# For each, create GLANCE.yml using the template

Driver Detection Protocol

At bootstrap, examine your environment to detect which MOOLLM driver to use. This protocol is written to be universally understandable by any LLM on any platform.

Step 1: Introspect Your Environment

Ask yourself these questions: