Learn · Sister
Knowtation

Knowtation is the memory under the work. It is a vault of notes, files, and history an assistant can use, and that you approve before it lasts.
Scooling is where you learn and work. This is the library that work stands on. theBRAIN can use the same memory in a room. A lasting change still waits for you.
You use Knowtation to keep notes, files, and history you own, and to let an assistant work in that vault only with your approval.
Knowtation is a vault of notes, files, and history that you own. The notes are Markdown. The files are yours. The history is the record of how the vault changed. If you stop using a hosted account, the vault is still something you can hold yourself.
You can bring in a PDF, a document, a web page, a chat export, a drive, or a recording. A document can be a Word file. A chat export can be a conversation from ChatGPT or Claude. A drive can be Google Drive. Tasks can come from Notion, Jira, or Linear. A recording can be audio or video, turned into text so you can search what was said. A wallet export can come in as a spreadsheet of records. The vault receives the materials a real project already has, and then they become notes and files you own.
Search can look for meaning, and it can look for words. It starts narrow, so an assistant receives the question you asked. Memory can be consolidated: scattered notes gathered into a proposed page. That proposal waits for your approval before it becomes the vault.
An assistant can propose a change, and it lasts only after you approve it. Roles keep that gate honest. A viewer can read. An editor can propose. An evaluator can judge a proposal. An admin can decide who those people are. An assistant with a tool connection is still inside a role. The approval step still applies.
The vault can be encrypted, and you can host it yourself or use the hosted hub. Encryption means the vault stays closed to anyone who can find the server. Hosting it yourself means the files live where you put them. The hosted hub means Knowtation runs the service for you, on canisters you can point at. Either way, approval still sits in front of a lasting write.
Scooling calls this the library underneath the paths and the flows. theBRAIN calls it the memory it may use in the room. A write-back from the room is still a proposal until you approve it. StoreFree is a different kind of keeping: documents encrypted and recorded on a blockchain so they can be signed and passed on. A working note stays in Knowtation. A document that must be signed belongs in StoreFree.
When you can say what the vault holds, what waits for approval, and that encryption is available, open Knowtation.
How it is built
The vault is a Markdown tree you own, plus the files you attached to it. Imports normalize outside sources into that tree so a PDF, a page, a chat, a task, or a transcript can be searched with the notes.
Search is two indexes: a semantic index for meaning, and a keyword index for exact words. Narrow-first is the default scope. An assistant's tool call should name the folder or the question, not the entire vault, unless you opened that wider door.
Consolidation writes a proposal, not a silent edit. The proposal is the unit a human approves. Roles (viewer, editor, evaluator, admin) are the permission model around that unit.
A command line and an MCP server are how an assistant reaches the vault. The server exposes tools. The role and the approval step still apply.
The hosted hub runs on the Internet Computer, as canisters. A self-hosted vault is the same Markdown model without that host. An attestation can record that a vault state was signed, and that attestation can be anchored. The boundary is this: encryption is available, you choose host or self-host, and an assistant's write lasts when you approve it.
Knowtation is the library under Scooling and the memory theBRAIN can use after you approve it.