01 / Capture and preserve
A durable learning record.
Reader integrations and imports feed a canonical archive. Stable source identities preserve provenance while a rebuildable index keeps the review experience responsive.
An independent engineering case study
A self-hosted learning pipeline connecting readers, a durable knowledge archive, review history and personal reflections. The infrastructure keeps ideas available across devices, with a wider design for connecting learning to the projects it can inform.
Public demo: synthetic reading only. No account. No private collection.
Learning in context
Weave sits within a wider learning system built around existing reading tools, knowledge records, databases and workflows. The goal is to help ideas return both for deliberate review and when they can deepen understanding of a project already under way.
The current review engine is implemented. Automated recommendations based on current projects are a proposed next layer.
01 / Capture and preserve
Reader integrations and imports feed a canonical archive. Stable source identities preserve provenance while a rebuildable index keeps the review experience responsive.
02 / Review and connect
Source-balanced selection, separate review history, personal reflections and device synchronization form a usable learning loop. Scoped permissions, backups and readback make it maintainable.
03 / Project-aware direction
Project-linked records and earlier learning workflows provide a foundation for bringing relevant ideas to work in progress. The next stage is permissioned retrieval from project databases, with source attribution and clear user control.
01 / A connected reading practice
The goal is not another reader. It is a useful path from a passage on a device to a quiet review, and from that review to a note you can keep.
Kindle
KOReader with the Readest plugin. Native Readest Cloud handles acknowledged progress and notes; a WebDAV metadata mirror feeds the existing bridge.
Local reading and network delivery are separate. The bridge is designed to resume queued work while the reader is awake and connected.
Phone + laptop
Readest on a GrapheneOS phone and in the web reader. Reader WebDAV sync carries books and reading state; the review app is a separate browser surface.
Reading and reviewing remain separate experiences, connected by stable source and highlight identities.
Obsidian
Highlights remain source records in Markdown. Weave reads a derived index and keeps review actions separately. Reflections are exported to Notes, not written over source text.
Database save and Markdown export have distinct states and receipts.
The documented architecture
The existing reader bridge polls WebDAV metadata read-only, sends it to a token-authenticated receiver, and passes accepted records to a scoped writer. CouchDB LiveSync carries the resulting Markdown to Obsidian.
Weave is a separate Node.js 24 application behind the existing Caddy HTTPS service. Its positively scoped connector can read Highlights and write Notes only. A cached index and durable review state live in its own SQLite database. It is not the reader bridge and does not replace the reading applications.
02 / A small, explainable review
The selector is a transparent set of heuristics, not a claim to know what you have learned. The defaults are six cards, a 35% recent-material share, and a seven-day cooldown.
Remove hidden, excluded, non-text, snoozed, reviewed-today and cooldown items before selection. A smaller session is preferable to silently breaking those rules.
Group eligible items by source before weighted random
selection. In mixed sessions, take at most two from a source
and reduce its weight by (1 + picks)² after
each pick.
Reserve round(size × recency) places for
eligible highlights actually created within 45 days. Import
time does not make an old highlight new. Freshness and
revisit signals are capped at 90 days.
Source-frequency and category controls range from 0 to 3. Favorites get a modest 1.15× weight, not a mandatory place. Recent, rediscover and focused-source modes offer different starting points.
What counts as a review?
Previous / NextNavigation only. No review recorded.
Mark reviewedExplicit action. Records a review.
Snooze 7 daysAdvances without recording a review.
03 / Learning principles, carefully applied
Returning to an idea is useful only if we distinguish an interface choice from an established learning result. Weave does not measure recall or infer mastery.
Cepeda and colleagues’ 2006 meta-analysis covered 317 experiments. Distributed practice can support retention; effective spacing depends on timing and the intended retention interval. It does not establish one universal schedule.
Read the primary research ↗What that means here
A cooldown creates distance between encounters. The seven-day default is a product heuristic, not a validated optimum or a trial of this app.
Roediger and Karpicke’s 2006 experiments compared studying with free recall. Retrieval practice improved performance on delayed tests relative to repeated study, even though rereading could create greater confidence.
Read the primary research ↗What that means here
Seeing a highlight again is not a recall test. Current Weave does not quiz you. Quizzes and measured retrieval remain future work.
Kornell and Bjork’s 2008 study examined spaced, interleaved examples in learning to recognize artists’ styles. Its structured learning task is narrower than a feed of unrelated passages.
Read the primary research ↗What that means here
Source balancing makes a review more varied. Random highlights are not scientifically equivalent to structured interleaving, and variety alone does not prove better learning.
This is not the Free Spaced Repetition Scheduler (FSRS), an adaptive mastery model, or a reproduction of a proprietary review algorithm. It is inspectable weighted selection.
04 / Small permissions. Visible boundaries.
Two environments share an interface and selection logic, not a data connection. The public version demonstrates the product without exposing the private system.
This public demo
The static host may retain ordinary request logs. Demo notes and actions are never uploaded.
Try it for yourself ↗The private application
A documented design, not a fresh production audit. The first scheduled backup execution has not yet been observed.
A reflection first receives a durable database save. Markdown export to Notes is a separate step with a pending state, delivery receipt and read-back. Saving locally must not be presented as confirmed delivery to Obsidian.
Planned concept / not an extension
A web passage should be able to join the same collection without a second inbox to maintain. The intended flow starts with a selection and an explicit Save, not background page collection.
Minimal permission on activation, rather than access to every site. Private, unpacked distribution is planned. The extension and capture service are not implemented.
A clear explanation preserves the decision, the alternatives, and the reason one of them was chosen.
Illustration only. Nothing is captured.
05 / Choices behind the interface
06 / Evidence, not implication
A working configuration, a successful test and acceptance on a real device are different states. This snapshot keeps them separate.
| Capability | State | Evidence or remaining work |
|---|---|---|
| Private web review app | Implemented | Production release 0.2.3. Recorded suite: 65 tests; five responsive viewports passed. |
| Phone / real-device acceptance | Follow-up open | Responsive checks are not acceptance on the actual phone. Device follow-up remains open. |
| Kindle reading bridge | Integration tested | Recorded reading, highlight and retry checks passed. Ongoing device health and fresh-delivery acceptance are maintained separately. |
| SQLite recovery | Restore tested | Consistent backup + fourteen-copy retention configured; isolated restore tested. First scheduled execution not yet observed. |
| Reflection to Notes | Explicit states | Database save first. Export can remain pending until delivery receipt and read-back confirm it. |
| Public demonstration | Static + local | Synthetic fixtures and local browser state only. No private-system connection. |
| Web clipper | Planned concept | Preview and explicit-save design only. No extension or live capture implementation. |
| Kindle review, offline Weave, quizzes, AI discussion | Deferred | Not deployed features. The current focus is highlight review. |
Built to be inspected, not taken on faith
Use the demo to explore the experience. Use the diagrams and explicit limits to judge the engineering.
Spend a moment with Weave