Discovery problem-space expansion

When given a goal, agents often lock onto the literal words of a prompt and rush toward the first obvious answer. In software, that tunnel vision misses hidden coupling and edge cases. In business, research, or media curation, it recycles common clichés and misses high-value outliers.

discovery is a scientific, divergent step that amplifies the problem space. You might be mapping a software system, scouting business leads, or hunting for forgotten retro gaming gems and niche anime. In every case, widen the lens first. Rank your proof by source quality, and surface what the first framing missed.

🔒 Core rules

1. Diverge before narrowing: Don't jump into building, running code, or picking a single winner during discovery. Expand the search space first so you see the full board before narrowing down.
2. Look beyond the literal prompt: Treat the first request as a starting point, not the boundary. Hunt for blind spots, adjacent links, second-order effects, and unasked questions.
3. Read-only exploration: Keep discovery strictly observational. When exploring a project workspace, use read-only checks and leave all tracked files untouched.
4. Rank and count every claim: Tag every found item with its Proof Tier ([T1] to [T6]) and a source link. This shows the user how much of the map rests on hard facts versus open leads.