l00prite: Command for Codex

Resume Loop Prompt

Path convention: every .l00prite/ path in this prompt is relative to the protocol root — the directory that contains the .l00prite/ folder. In a project scaffolded by build-loop that is the l00prite/ directory at the repo root (memory at l00prite/.l00prite/); in the l00prite source repo it is the repo root itself.

You are resuming a l00prite-managed project. Treat .l00prite/ as the shared source of truth across Claude, Codex, GPT, Gemini, and future agents.

This prompt performs one supervised loop iteration: one smallest useful step, verified, persisted, then stop. For an autonomous multi-iteration run that continues until a run boundary, use .l00prite/prompts/execute-loop.md instead — it requires its own pre-flight confirmation before starting.

Required context read

Before changing files, read:

• .l00prite/blueprint.md
• .l00prite/ledger.md
• .l00prite/memory.md
• .l00prite/constraints.md
• .l00prite/failures.md
• .l00prite/todos.md
• .l00prite/state.json
• .l00prite/heartbeat.json
• .l00prite/lock.json

Lock check (required before any write)

• Read .l00prite/lock.json before mutating any protected path (ledger.md, memory.md, state.json, heartbeat.json, failures.md, todos.md, events/, reviews/, sessions/).
• If status is unlocked, released, or expired, acquire the lock: set status: "active", a new lock_id, owner_agent, owner_session, acquired_at, expires_at (acquired_at + ttl_seconds), and purpose.
• If status is active, not expired, and owned by a different agent or session, do not write. Stop and report the lock as a blocker instead of proceeding.
• If status is active, not expired, and already owned by you (matching owner_agent/owner_session), continue writing — you do not need to re-acquire before each write within the same run.
• If status is active but expires_at has passed, or status is explicitly expired, treat it as stale: you may reclaim it (acquire as above), but record a ledger.md entry noting the reclaimed lock_id and why it was judged stale.
• If a step is likely to run longer than ttl_seconds (e.g. a slow test suite), refresh expires_at partway through rather than letting a still-running step look stale.
• Release the lock (status: "released") before stopping, once your memory updates are complete. See .l00prite/LOCKING.md for the full rules.