Structured Research

Validate an explicit assumption against evidence before it becomes a planning input. Take the "thing the user still treats as an assumption", frame it as a falsifiable question, research it with a chosen methodology, and return a graded, evidence-backed verdict with a non-binding recommendation the maintainer may adopt, adapt, or replace.

Core principle: An assumption is not evidence. Evidence is not a verdict. A verdict is advisory, not a decree.

Violating the letter of this process is violating the spirit of structured research.

When to Use

Trigger when:

• A belief is still an assumption — "I think X works this way", "this library probably supports Y", "Z is the fast path"
• An assumption is about to enter planning/development unvalidated and the cost of being wrong is real
• The user says "validate this", "is it true that…", "research whether…", "verify my assumption"

Do NOT use:

• To generate or explore ideas (→ pocket-pitching / pocket-grinding — those diverge, this validates)
• To fix a known defect (→ bug-hunting)
• When the claim is already settled and just needs implementing (→ hotfix)