A detective walks back into a room three days after the break-in, and nothing has moved, yet something is still off. That’s the exact puzzle a Reddit prompt engineer just tackled. How do you find a change that’s still affecting things, long after the moment that caused it is gone? This Redditor, u/No_Understanding6388, posted the second half of a huge prompt framework called FRR v0.4 (Fluid Relational Reasoning) to r/PromptEngineering. Buried inside the dense language is a genuinely useful trick for anyone building prompts that reason over multiple steps.
Think of this framework like a detective’s toolkit for chasing down where a clue is actually hiding, instead of assuming it vanished. In an AI conversation, an idea from three turns back can still be shaping the current answer. That’s true even though it’s nowhere on screen. Most prompts don’t have a way to ask “where did that come from.” This one does.
The Detective Kit, Mapped 🕵️
The original post gives five “handles” for figuring out where a vanished detail is still hiding. Here’s what each one means in plain terms, mapped to a detective story:
- Shadow: the clue is still in the room, you just summarized it away. Like a fingerprint that’s there but nobody dusted for it.
- Echo: the clue only shows up in how you got here, not in where you’re standing now. Two suspects can look identical today but behave differently because of what path they walked.
- Reflection: the clue only appears because you’re checking. The act of testing creates the difference, like an alarm that only trips when someone probes it.
- Wake: the clue isn’t in the room anymore, it changed the room itself. A broken lock doesn’t prove who broke in, but it changes what the next visitor can do.
- Mirror: the same pattern shows up somewhere else entirely, in a different file, a different report, a different case. Same shape, different substrate.
The author’s own words on why this matters, quoted exactly from the framework:
«Through what part of the coupled system can the earlier distinction still affect a later possibility?»
That one line is the whole detective’s opening move. Ask it before you ask anything else.
How to Apply It 🔎
You don’t need the full academic version to use this. Drop the location question into any prompt where you suspect the AI’s answer is being shaped by something you can’t see anymore:
«When a distinction returns, locate what carried it. When an action passes, inspect what it changed behind itself. Do not confuse memory in a state with memory in a trajectory, an interaction, a translation, or a field.»
Reproduce that exact wording if you use it. It’s doing real work. It forces the model to separate “this fact is stored somewhere” from “this fact only shows up because of the steps that got us here.” That’s the chain-of-thought move at play, except it’s aimed backward instead of forward.
A second block from the post is worth stealing for research-heavy prompts. Use it when you want the model to check its own sources instead of trusting the first plausible answer:
«Preserve the intuition’s lineage. Search by function as well as vocabulary. Follow every failure into its repair literature. Count convergence only when the routes are genuinely independent.»
Use that one when you’re asking an AI to verify a claim, not just generate one. It stops the model from treating five search results that all cite the same source as five independent confirmations.
One variation worth trying: shorten the location question to a single follow-up you can paste after any answer. “Is this from right now, from how we got here, from you testing it, from something you changed earlier, or from a pattern borrowed elsewhere?” Same five modes, way less overhead.
Use Cases 📋
- Debugging a multi-turn agent that gives inconsistent answers to the same question. Ask which mode explains the drift before you assume the model is broken.
- Auditing a RAG pipeline where a document was edited or removed but the model’s answer still reflects the old version. That’s a shadow or an echo, and the fix is different for each.
- Checking a fine-tuned model for behavior that traces back to training data you thought was filtered out. Ask if it’s a shadow (still in the weights) or a wake (baked into how the model now responds).
- Reviewing research assistants that cite sources. Force the “independent convergence” check so the model doesn’t count the same original claim five times.
One commenter on the thread, u/TheUntrueSolitude, flagged the real value here, catching prediction that stays accurate while the causal story stays wrong. Your AI can give you the right answer for the wrong reason, and this framework is built to catch exactly that.
This isn’t a plug-and-play prompt you paste once and forget. It’s a way of asking better follow-up questions when an AI’s answer feels haunted by something you can’t quite place. Go read the full FRR v0.4 thread on r/PromptEngineering for the rest of the framework. It also covers crystallization and dormancy, rules for when to let an idea settle versus keep it open.
Frequently Asked Questions
Q: What’s the difference between a “shadow” and an “echo,” and why does it matter?
A shadow is information hidden by your observation method, existing in the underlying system but masked by your current view. An echo is when the system’s history determines its behavior even when present conditions appear identical. This distinction matters in simulation and modeling because you might predict the right outcome without understanding why, which fails when conditions change. The causal path, not just the prediction, is what carries forward.
Q: Should I keep old versions of my ideas, or just move forward?
Keep them as dormant branches rather than overwriting them entirely. Most people lose the reasoning that led them there, so they can’t see where they went wrong. Version control for ideas is as valuable as version control for code.
Q: How do I know when my literature review is actually complete?
When the same papers and ideas keep appearing across different search angles, that’s a warning sign, not confirmation. Rephrasing a question five ways and hitting the same five papers doesn’t mean you’ve covered the space. It means you’ve hit the limits of that particular lens. Break the pattern by approaching the problem from a fundamentally different angle or domain.
FRR v0.4 part 2 of 2
by u/No_Understanding6388 in PromptEngineering