Why a Synthesis Layer, not another notes app
Every knowledge tool of the last decade made one promise: you will not lose what you read. They kept it. And it changed almost nothing — because the bottleneck was never storage. It was the distance between saved and shipped.
The gap no tool closes
A year of reading decays to roughly a third by the next day (Murre & Dros, 2015). What survives in your vault is text you can search — not knowledge you can build on. When the deadline comes, you do not open the 4,000-note archive. You open a blank page and an LLM, and you ship something plausible instead of something grounded.
Indelis is built for the second half of the job:
- Capture → distil — sources become atomic notes, encoded for retrieval, not for filing.
- Your gate → verify — every claim gets a trust band: solid, contested, tentative. Nothing is dressed up as a fact it hasn’t earned.
- Hold — spaced retrieval (FSRS) until the ideas are yours, not your database’s.
- Synthesise — Weaver proposes non-obvious, auditable connections between things you actually hold; you accept or dismiss.
What it refuses to be
No machine-authored synthesis with your name on it. No streaks, no feed, no engagement metrics — time spent counts against the score, never for it. The only number that matters is grounded synthesis: work you shipped whose claims trace to notes you verified.
Self-hosted, your models or your keys, full Markdown export at any moment. The composition stays yours — that is the whole point.