Knowledge systems
Can an idea survive its bookmark?
I built a research library that turns saved material into practical guides while keeping the path back to every source.
My role
I built the ingestion, research, topic organization, publishing workflow and shared local/public website.
Where it stands
Live personal project. The public library is a curated static snapshot; private intake and write operations stay local.
What changed.
Sources become useful guides, with citations, files and a publication process that verifies the actual live result.
From saved to useful
Keeping a link is easy. Remembering what it was useful for is harder. Kiln takes a source dossier, checks the practical claims against current evidence, and produces a guide that can hold instructions, prompts, files and project ideas together.
Keep the trail
I retain original source URLs and immutable input revisions. Related sources can become one topic, but merging is reversible and earlier links still resolve. Similar tags alone are not enough reason to collapse two different ideas.
Research is not implementation
A completed guide does not mean I built every project it suggests. Kiln tracks the owner’s progress separately and keeps project builds behind a separate queue decision. This makes the library a more honest record of work.
Publishing with a boundary
The public export includes only allowed fields and artifacts. Private notes, credentials and machine paths stay out. After deployment, the release workflow compares the live files with the exported hashes before calling the publication complete.
The stack
- Python
- SQLite
- Full-text search
- JavaScript
- Content hashing
- Vercel