The problem
Every day, assistants explain the same ideas to different people, and every explanation is thrown away when the chat ends. A good interactive explanation of aliasing, or of what a bit measures, is expensive to make well and then costs nothing to reuse. Right now almost none of that work is kept.
What this site does about it
It keeps the work. A widget here is a small sandboxed program that makes one claim, lets you test it with your own hands, and asks one check at the end. AI writes the first draft, in a chat, the moment someone needs it. The draft is served straight away, and from then on it is the answer the next person gets instead of a fresh generation. People refine it: they pass or fail its check, dispute a question, propose a link, fork it, or send a pull request. What holds up is promoted into the library; what does not, fades.
The library is 39 widgets today, licensed CC-BY-4.0, embeddable on any page with two lines, usable from any chat client that speaks the Model Context Protocol, and readable by people and by models alike. Every widget shows who made it, what it was forked from, and what changed.
What is free, and what is not
The widgets are free to use, embed, fork and redistribute with attribution, and they will stay that way; that is what the licence on the library repository guarantees. Embedding costs nothing and asks for nothing. Accounts are free and optional; they exist so your name can be on what you make and so your progress can follow you. The tutor on this site is metered per person because the model behind it costs money; the connector uses your own assistant, so it costs the site nothing and has no such limit.
The site's own code, the Worker and the pages, is published at github.com/jacobmimms/learn under a closed licence: you can read it and learn from it, but the library is the thing meant to be shared.
Where it is going
Progress that follows you across the site and your chats is being built now. After that, the plan is to let widgets be composed into lessons in the open, the way the courses here already string them together, so that a whole course can be forked and improved the same way one widget can.
Want to help? Use it in your chats, open a pull request, or disagree with a check on any widget page.