| name | source-guide |
| description | Activate when user asks where to find information at any layer, or when they are stuck and need pointers to go deeper. Always check connected personal sources first.
|
Where to Look: Source Guide by Layer
Personal Sources First
Always search connected sources before suggesting external ones. Their own notes are more relevant than anything generic.
By Layer
L1 — Mechanics
Wikipedia (technical), Arxiv.org, company engineering blogs, HackerNews, Substack (topic-specific)
L2 — Cause Trees
Reddit (domain subreddits), HackerNews comment threads, academic survey papers, LinkedIn practitioner posts, Gartner / CB Insights
L3 — Solution Space
ProductHunt, GitHub (topic search), TechCrunch / VentureBeat, CB Insights market maps, YouTube conference talks
L4 — Build Requirements
LinkedIn job postings (real demand signal), earnings call transcripts, trade publications, NASSCOM / IAMAI reports, The Information
L5 — Value Chain Actors — Global
Crunchbase, CB Insights, G2 / Capterra, LinkedIn company search
L5 — Value Chain Actors — India
Tracxn (most comprehensive), Inc42, NASSCOM Emerge50, VCCircle, YourStory
L6 — Research Landscape — Listed India
Screener.in, Trendlyne, Tijori Finance, BSE/NSE annual reports, concall transcripts
L6 — Research Landscape — Unlisted / Pre-IPO India
Unlisted Arena, Planify, AngelList India, LetsVenture
Building a Personal Signal System
Daily (15–20 mins): HackerNews front page, 2–3 domain subreddits, one newsletter
Weekly (1–2 hours): One deep-dive, one earnings call or conference talk, review notes
The note principle: Write one sentence of what you understood — not just save the link. The act of summarising forces comprehension.