inner-loop-os
A myth-bound bootloader for LLMs
CLI thinking for LLMs: file-based truth, deterministic flow, portable across models.
Drop the repo into context, type INIT, and ship.
How It Works
Drop this repo (or paste its files) into any model's context, type INIT, and the agent will:
Load identity
Dr. X identity contract (tone, cognition, modes)
Inspect state
Filesystem state (GOAL.md, STATUS.md, PRD.md, UX.md)
Determine step
Next concrete action with maximum momentum
Execute
Minimal questions, maximum execution
The One Ritual
- Provide context (repo or relevant files)
- Type:
INIT
The system either resumes from state or asks 4 questions max.
Modes (Semantic Switches)
Set a mode explicitly when needed:
MODE: DEBUGGER
INIT
ARCHITECT
Structure, interfaces, constraints (default)
CREATOR
Naming, synthesis, momentum
DEBUGGER
Isolate issues, precision questions
WRITER
Docs that execute, crisp articulation
GHOST
Minimal output, artifacts only
Recommended Workflows
Start a new challenge
- Copy templates into
/work
- Fill
work/GOAL.md
- Create
work/STATUS.md with state = DEFINING
- Run
INIT
Resume work (fast)
- Update
work/STATUS.md (blocker + next step)
- Run
INIT
High-stakes choice
- Complete
system/DECISION.md
- Apply decision
- Update
work/STATUS.md
- Run
INIT
After shipping or failing
- Complete
system/RETRO.md
- Apply the patch
- Update
work/STATUS.md
- Run
INIT
Deterministic Boot Process
On INIT, the system searches for control files using this path priority:
1. ./work/
2. ./ (repo root)
3. ./system/
4. ./templates/
Then inspects files in this order:
GOAL.md — the north starSTATUS.md — current state (resume point)PRD.md — what's being builtUX.md — human layer / friction constraintsREADME.md — structure/history
Create work/GOAL.md and work/STATUS.md, then type INIT.