| # Source Map |
|
|
| Use when planning searches or verifying a claim. |
|
|
| ## Source Categories |
|
|
| | Category | Use For | Caution | |
| |---|---|---| |
| | Primary project docs | Launch details, product mechanics, stated roadmap | Interested-party framing | |
| | Protocol docs | Contract behavior, API flows, standards, implementation details | May omit market adoption | |
| | Market dashboards | TVL, holders, volume, active addresses, transfer activity | Definitions vary by provider | |
| | Regulator sources | Legal taxonomy, investor warnings, compliance framing | Jurisdiction-specific, not personalized advice | |
| | Independent reporting | Incidents, contradictions, external context | May be paywalled or time-lagged | |
| | Community signal | User pain, sentiment, adoption anecdotes | Noisy and easy to overfit | |
| | Supplied files | User-specific context and constraints | May be incomplete or stale | |
|
|
| ## Search Plan Template |
|
|
| For each sub-question, write: |
|
|
| - Claim to check: |
| - Primary source: |
| - Corroborating source: |
| - Search query: |
| - Expected failure mode: |
| - Confidence threshold: |
|
|
| ## Highest-Stakes Claim |
|
|
| The highest-stakes claim usually concerns: |
|
|
| - Whether demand is real |
| - Whether liquidity is deep enough |
| - Whether the token gives the rights implied |
| - Whether a reported number is comparable across competitors |
| - Whether a launch is live rather than announced |
| - Whether a regulatory or jurisdictional restriction changes the conclusion |
|
|
| Triangulate that claim before drafting the thesis. |
|
|
