Park-It-As-Debt

The prompt captures its own occasion. Mid-work, the operator hit something he couldn't solve, decided to park it — write it down somewhere, come back to it as debt later — and move on in the planned sequence rather than stall. Then he stopped and asked whether that very move deserves to be a protocol.

It is self-gating in a way few prompts are: “if you decide, via the top level RCR, that we need to have a protocol for this case, make it, run it, and move on as you were before I interrupted.” The deliberation decides whether the deliberation produces anything. Either way, the interruption closes cleanly and work resumes where it left off.

The wider frameParking is only safe if the parked thing comes back. “Write it down somewhere” is the weak version; a debt register with reservation and a return trigger is the strong one — which is the gap the parking family exists to close.

“we could not find the solution, so we are going to park it for now, write it down somewhere, and come back to it as debt later” — The move, named in full: defer the unsolvable as explicit debt so the current sequence isn't derailed. The risk it guards against is the parked item quietly disappearing instead of returning.

“By leaving it as a thing to do later, we then move on in the sequence of work as we had planned to do” — Why it matters: parking protects the plan. An unsolvable that stops the whole sequence is more expensive than one set aside with a marker — as long as the marker is honored.

“RCR on if we should make a protocol … If you decide … make it, run it, and move on as you were before I interrupted” — The self-gating structure: the top-level deliberation decides whether to build, builds if so, and either way returns control to the interrupted work — the parking discipline applied to the parking-prompt itself.