1) Pick the closest template
Accuracy is not the goal. Legibility is. If the template is “close enough,” it will surface the risk shape.
PanoSight · clarity instruments · decision legibility
Pick a scenario. Get a Decision Clarity Label. Share it. It scores the decision environment — not you.
🔒 Not therapy. Not coaching. Not crisis support. A quick mirror for hidden consequences.
Tip: Press S to share, R to reset, D to surprise me.
Mini-challenge: pick a scenario you once regretted, generate a label, and share it with one sentence: “This was a low-clarity environment, not a low-intelligence moment.”
Try: Budget airline · Free trial · Lease in a rush · Mixed signals.
This is the fastest way to turn regret into a map.
Choose the closest match. The goal is not accuracy — it’s legibility.
Quick tweak (optional)
Is this scenario more forgiving or more punishing than typical?
cheap entry · strict rules · hidden edges
social + institutional ambiguity
clear pricing · reversible choices
Use this if you want precision for your exact situation. Otherwise: pick a template and share.
This is a weather report for optionality. It doesn’t tell you what to do — it tells you how much the environment is likely to hide consequences until after you commit.
Accuracy is not the goal. Legibility is. If the template is “close enough,” it will surface the risk shape.
If your situation is unusually forgiving or unusually punishing, nudge the whole label. This captures the “my version is worse than typical” effect.
People share these when it reduces shame and restores agency: “I didn’t fail — I entered a foggy system.”
Low clarity doesn’t mean “don’t proceed.” It means “you’re missing a map.”
Legible environment. Costs and rules are visible, mistakes are survivable, and you retain leverage.
Some edges are unclear. You can proceed — but only after naming the top 1–2 failure modes.
Consequences are delayed or stacked. Small mistakes can become expensive. Systems like this punish speed.
The label is built from five “fog generators” that show up across contracts, relationships, purchases, and institutions.
Do you understand the full cost, including edge fees, time cost, friction cost, and penalties?
If low: ask “What does this cost if everything goes slightly wrong?”
How many conditions must you remember to avoid accidental failure?
If low: ask “What are the top 3 rules that would burn me?”
If you make a small mistake, how harsh is the consequence?
If low: ask “What’s the penalty for being late / wrong / canceling?”
Can you change your mind later without humiliation, major loss, or prolonged friction?
If low: ask “What does exit actually require?”
After you say yes, who holds leverage — you, them, or a third-party system?
If low: ask “What can they do that I can’t?”
These aren’t moral failures. They’re consequence shapes. If a vignette stings, run the closest template and share the label instead of self-blaming.
Ticket looks like $49. After bag rules, seat fee, check-in window, and a missed condition — the “cheap” choice becomes the most expensive.
You forget the cancel date. The cancellation path is buried. You get charged and feel stupid — but the system is optimized for forgetting.
Comp is clear. Scope isn’t. You say yes, then discover invisible expectations, unclear authority, and shifting rules. You’re paying with nervous system bandwidth.
You’re rushing. Fine print hides fees, deposits, and maintenance responsibilities. Later you realize you signed into a rules maze.
Ambiguity isn’t always malicious — but it shifts power. If one person controls clarity, the other person pays with anxiety.
Policies are visible. Mistakes are survivable. Exit is real. You can decide without carrying a defensive cognitive load.
If you recognize a vignette: run the closest template → share the label.
The label is a “regret translation layer”: it turns shame into legibility, and legibility into better moves.
This instrument is designed to remove self-blame and increase consequence legibility — especially after regret.
Fog isn’t stupidity. It’s structural: many environments delay information and front-load commitment. Humans are bad at simulating edge cases under time pressure — so we confuse momentum with clarity.
It’s a weather report. Low clarity means “slow down and gather info.”
It scores the environment, not your worth or intelligence.
One click is enough to interrupt a bad momentum loop.