A live demonstration of Kit
Your AI forgets you between sessions, so every project opens by explaining yourself again. Kit gives it a memory that lasts instead. Proving that is the awkward part: ask an AI about anything real and you cannot tell whether it remembered or simply knew already.
We invented a town. Mayfur is in no book, no website and no training data. It was written for this demonstration and exists nowhere else.
Mayfur was written into two separate Kits, one seeing the town from the ballroom and one from the kitchen steps. Each is a whole Kit, and neither can read the other.
Five questions, asked live from your browser. A right answer here cannot be a lucky guess. It can only have been remembered.
No answer below is in this page. Read the source and you will find the questions and the rubric and no conclusions at all. Each answer is fetched only once the live fetches behind it come back carrying the evidence it rests on, from the Kit it names. If one fails you get "withheld" and the reason, never a conclusion this page did not just earn.
To be exact about what is ours and what is the archives': the five questions, the searches that answer them and the rubric naming which records must come back are all written by us, the way any demonstration picks its examples. What is not written by us is the evidence or the conclusion. Those are fetched live, and a search that comes back with the wrong records releases nothing at all. So this shows you retrieval you can check, not a model reasoning unaided; the archives are the real thing either way, and your own agent can interrogate them at https://demo.kit-project.com/llms.txt without our questions.
Two Kits, each holding half of the season: Lady Whiskerdown keeps the amber lights, The Area Cat the lavender. Neither can read the other. Your browser is the only thing on this page that reads both.
Every trick in this town has a plain-clothes twin. The answer neither Kit can give alone is your architecture decision scattered across a Slack thread, a postmortem and one engineer's memory of a hallway conversation. The count that Friday's entry corrects, with both kept, is the vendor you switched and the price you revised, reasons still on file. The honest blank is your assistant saying "we have no record of that" rather than inventing one.
You do not have to be an engineer for that to be worth something. The people getting the most out of Kit mostly work with AI all day without building the software themselves: designers working in code, researchers, writers, consultants running several clients at once.
And it stays yours. A Kit of your own runs on your own machine: the store, the index and the search all stay there, nothing is shipped to a memory service, and you can read, correct or delete anything it holds. Point it at a hosted model and that model sees what you send it, which is your call to make per function and visible in the matrix that makes it. Same substrate, different costume, and it keeps your side of the town.