When a prompt goes stale

A prompt goes stale when a decision it depended on changed. We flag it, quote the cost to refresh it, and leave the choice to you.

Why we mark instead of rewrite

You may have already pasted that prompt and built on the result. Silently rewriting it would put your plan and your codebase out of sync without telling you — which is the exact failure we exist to prevent.

What happens when you change a decision

We trace which prompts read from the section you edited and mark only those.

1Edit any blueprint section — free, always.
2We show which prompts depend on it and mark them outdated.
3You tick the ones worth refreshing; the quote updates live.
4Refresh runs and the untouched prompts stay exactly as they were.
A prompt you already built from can stay outdated on purpose. That is a valid choice, and we record it.

Reading the states

Ready means unlocked and unused. In use means you pasted it and are building. Done means you ran the verification list. Outdated means a dependency moved. Locked means a prerequisite is not finished.

Did this answer it?
Still stuck on this? A person reads every message and replies within one working day.Contact support