I’m trying to figure out if this idea is actually doable or just looks good in YouTube demos.
I have around 7 firmware architecture/spec documents, totaling roughly 2,000–3,000 pages. These are deep technical documents (secure boot, HSE, programming flows, APIs, etc.), where everything is interconnected — not just plain text you can search.
What I want is something like:
- A “second brain” system
- Similar to Obsidian graph view
- Where concepts are actually connected meaningfully (not just embeddings)
- And I can query it without losing context or missing details
But I’m skeptical because:
- Most tools I see feel like fancy search, not real understanding
- These docs have flows, dependencies, cross-references
- I don’t want hallucinated or partial answers — it needs to be reliable
So I’m wondering:
- Has anyone here actually built something like this for large-scale technical docs (2k–3k pages)?
- Is a true knowledge graph from PDFs even realistic?
- Can tools like Obsidian + Claude + NotebookLM actually work together for this?
- Or is there a better approach people use in real-world setups?
- How much of this ends up being manual work vs automation?
I’ve seen a lot of “AI second brain” videos, but they all feel small-scale or oversimplified.