--- name: parked-task-workflow description: "What \"park\"/\"parked\" means as an owner instruction — keep in memory, never act until explicit go" metadata: node_type: memory type: feedback originSessionId: 0b7c5f41-bb34-4ab4-93be-fdb363f5eb40 --- When the owner says to PARK a task (or calls something "parked"), keep it recorded in memory but DO NOT execute it until the owner explicitly says go. "Parked" is reserved for genuinely later-down-the-road tasks — NOT near-term deferrals or "do this last in the current queue" items. **Why:** The owner wants a clear distinction. A queued/deferred item still gets done as part of the current program; a PARKED item is set aside indefinitely and only starts on an explicit owner go-ahead. Treating "parked" as "do it eventually/soon" violates intent. **How to apply:** On "park X" — record X in memory, mark it PARKED (do-not-start), and leave it out of the active work order. Never auto-start a parked task, even when the queue empties. Surface parked items only when relevant or when the owner asks. For what is currently parked, read the `parked-*` memory files and `QUEUE.md` — don't keep a list here.