You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Engram currently requires content to live in an Outline wiki before it can be extracted into the knowledge graph. This adds an intermediary step that most learners won't set up. ivvi takes raw audio; many other tools take raw text, URLs, or file uploads.
Proposal
Support direct ingestion from multiple unstructured sources without requiring an Outline wiki:
Paste text — paste lecture notes, article text, or any content directly into an ingest screen
URL fetch — provide a URL, Engram fetches and extracts (web articles, documentation pages)
All paths feed into the existing ExtractionService → knowledge graph → FSRS pipeline. The Outline wiki becomes one input source among many, not a prerequisite.
ExtractionService already handles the Claude extraction — this is about diversifying what feeds into it
Why this matters
The wiki requirement is the biggest assumption baked into Engram's architecture. Most learners don't maintain a wiki. Meeting them where their content already lives (browser, clipboard, files) removes the highest barrier to adoption.
Problem
Engram currently requires content to live in an Outline wiki before it can be extracted into the knowledge graph. This adds an intermediary step that most learners won't set up. ivvi takes raw audio; many other tools take raw text, URLs, or file uploads.
Proposal
Support direct ingestion from multiple unstructured sources without requiring an Outline wiki:
All paths feed into the existing
ExtractionService→ knowledge graph → FSRS pipeline. The Outline wiki becomes one input source among many, not a prerequisite.Relationship to existing work
ExtractionServicealready handles the Claude extraction — this is about diversifying what feeds into itWhy this matters
The wiki requirement is the biggest assumption baked into Engram's architecture. Most learners don't maintain a wiki. Meeting them where their content already lives (browser, clipboard, files) removes the highest barrier to adoption.