Feature
The reading order your sources never gave you.
You're starting with three textbooks on the same topic, a stack of papers that reference each other in circles, and a codebase README that assumes you already know the architecture — and none of them tell you which one to open first. SILKLEARN reads across all of them, maps what depends on what, and gives you the dependency order your source material never made explicit.
Why this matters
A feature is only valuable if it makes the compiled graph more defensible in real use.
What it does
This feature turns hidden assumptions into something you can inspect.
Capability 01
Researchers: find which papers assume which priors — and stop assembling your model backwards.
Capability 02
Developers: see which architecture decisions your code depends on — before you ship something that breaks one of them.
Capability 03
Students: see where your textbooks disagree before that gap distorts your reasoning.
In depth
Most sources don't fail because the information is wrong — they fail because the reading order is invisible. When you're dropped into a new research area, a large codebase, or a pile of conflicting textbooks, there's no signal about what to read first. You build a mental model by accident, filling gaps in whatever order you happen to encounter them. SILKLEARN's dependency mapping makes that prerequisite structure explicit. It traces what each concept assumes you already know, finds where two sources give you different answers to the same question, and builds the graph your brain was trying to construct anyway — surfaced, inspectable, and ready to follow.
How it works
Step by step
- 01
Ingest your sources
Upload whatever you're trying to learn from — research papers, technical docs, textbooks, codebases, PDFs. SILKLEARN begins identifying the conceptual relationships between them.
- 02
Identify dependencies
Using structural analysis, it finds where one concept assumes another has been understood — and makes those implicit assumptions into explicit prerequisite edges.
- 03
Build the graph
The result is a directed acyclic graph (DAG) showing which concepts must come before others. The order is extracted from your sources, not invented.
- 04
You review it
Before you follow the path, you inspect the graph. You see every edge, every source reference, every place where your sources conflict. You decide what to trust.
- 05
Follow the path
The approved graph becomes your reading order — the exact sequence your material demands, with contradictions flagged and dependencies visible.
Common questions
- Does this work with research papers?
- Yes. Research papers are one of the best inputs for SILKLEARN — they're dense, heavily cross-referenced, and assume a lot of prior knowledge. SILKLEARN surfaces those assumptions as explicit edges so you can see what you need to read before a given paper will make sense.
- What if my sources contradict each other?
- That's exactly what SILKLEARN is built to surface. When two sources give conflicting accounts of the same concept, the graph flags the contradiction so you can see it — and decide which source to trust — instead of unknowingly building a mental model on inconsistent foundations.
- How is this different from just asking an AI to summarize my sources?
- Summarization answers questions about what's in your sources. SILKLEARN synthesizes the structure — what depends on what, where sources agree, where they don't, and what order you should encounter the material in. It's not a query interface. It's a map.
- Does it work with unstructured sources?
- Yes. SILKLEARN is designed for dense, unstructured source material — PDF papers, technical wikis, raw documentation, textbook chapters. You don't need clean formatting to start.
Related paths
See where this capability becomes operationally useful.
Next step