Codex runtime mapping

Resolve cursor-poteto-mode, cursor-architect, cursor-arena and cursor-show-me-your-work by exact installed name. Preserve the falsifiable done predicate, phased experiment loop, evidence and audit trail. The current task’s authority determines whether a human checkpoint or commit is required; do not create an extra approval gate for already authorized reversible work.

Figure it out

When the task matches no playbook, design one. The deliverable before any code is the workflow itself: a sequence of phases that scales rigor to the task, runs the scientific method, and leaves a decision trail a human can audit after stepping away.

Start

Open a todolist whose first item is to read the Principles section of cursor-poteto-mode. Then add the phases below as todos.

Phase A: Frame

Ground first, then commit. Don't start the run until you can state:

• The definition of done as a falsifiable predicate (the prove-it-works principle skill).
• Scope, quantified: rough units and effort, plus the blockers grounding surfaced.
• The rigor level, biased high. One-way doors and high blast radius get more. Reversible low-stakes steps get less. Rigor is gates and artifacts, not "try harder".