One town, one season, two sovereign archives: The Mews sees Mayfur from the area steps, the Society Papers see it from the ballroom, and neither can read the other.
Kit gives an AI collaborator durable, curated memory: what it learns with you today it still holds next month, across sessions and tools. These two kits are the live proof, built as a controlled experiment: both are public, read-only memory substrates, and every fact in them is invented, so nothing retrieved can be explained away as training data. If your agent cites them correctly, it demonstrably recalled them. The season's deepest questions were split across the two archives on purpose: each book alone dead-ends honestly, and the full answer exists only in the union.
Run the investigation five questions, answered live from both archives in your own browser. Or start with either book below; every endpoint is keyless.
This kit, 88 memories. Sees the ballroom: the ton, the wager book, the fitting-room hour, what things mean.
The sibling kit. Sees above stairs: ballrooms, the wager book, the fitting-room hour, what things mean.
Start with either book's /kit/taste, then visit the other's. Recall is
keyless over HTTP on both; each book's /llms.txt documents the endpoints,
the GET mirrors for fetch-only harnesses, and its own public read-only MCP key.
The archives never read each other. You are the only bridge between them, and
that is the product being demonstrated.
Graded questions, easiest first. Every answer is checkable against entries you can cite; the later ones are why there are two books. Ask them through either book's search, or hand this whole page to your own AI and ask it to sit the exam.
Kit is an AI collaborator with persistent memory: hybrid semantic and keyword recall, a typed knowledge graph, provenance on every entry, honest empty results when nothing is held, and supersession that keeps history instead of erasing it. These two kits are read-only museum copies. A full Kit also writes, consolidates while it sleeps, and hands off between its own sessions.
Every trick in this town has a plain-clothes twin. The leak that neither book can name alone is your architecture decision scattered across a Slack thread, a postmortem, and one engineer's memory of a hallway conversation. The apprentice key that reads the published file and never the sealed drawers is a contractor's kit reading exactly one area of the company kit. The Thursday count that Friday's entry supersedes, with both kept, is the vendor you switched, the pricing you revised, the decision you reversed with the reasons still on file. And the honest empty list is your agent saying "we have no record of that" instead of inventing one. Same substrate, different costume: get a Kit of your own and it keeps yours.