The bargain · Yours, provably
Your Mind is a repository in your own account. This is what that means on an ordinary afternoon, and exactly what happens if you ever decide to leave.
01
The repository, the keys, and the receipts live in an account with your name on it. Not a tenant inside ours. Not a workspace we administer on your behalf. Yours, in the sense your accountant would recognise. We hold no credential that opens it after the first day.
02
You can clone it. Every file is plain text, readable without us and without any particular software. The history is there too, so you can see when a thing was decided and what it replaced. If you want to read the whole score on a plane with no signal, that is an afternoon's work and nobody's permission.
This is the part people underestimate until the first time they use it. Not the moment you leave. The ordinary Tuesday you want to check something and find you simply can.
03
Most owners would rather not run servers, so we run them. That is the whole of what hosting means here. The account is yours, the keys are yours, and we are operating equipment inside a boundary you control. What someone runs for you, they can end up holding over you. We built the boundary specifically so that cannot happen, and the rest of this section is the evidence for that sentence rather than the promise of it.
04
Not a policy, a procedure. You take the repository, the keys, and the receipt chain. You point it at your own machine or a provider of your choosing. It works. The gate still refuses what it refused before, the receipts still verify against each other, and the score is the score.
There is no export request, no thirty-day window, no negotiation with a retention team. The thing you would be leaving with is the thing you have had the whole time.
05
We could hold it for you. It is a better business: the longer a company holds your knowledge, the more it costs you to go. We took the other side of that bet on purpose, and it is the reason to trust the rest of what we say. Build the Mind, hand over the keys, earn the renewal on the gardening.
I ran a company out of my own head for years, and the thing I would not have accepted from anyone is a version where the memory was theirs. So I did not build one. Our first client can leave any day, with everything, working. That capacity is the product, not a risk we tolerate.
FILED
your account, your keys, from day one
NEXT Held at the gate Deny by default, and what Mensara cannot see →The founding cohort is small on purpose. Each Mind is brought up personally.
MENSARA.AI · YOURS, PROVABLY · MACHINE SURFACE · TEXT/MARKDOWN
# Yours, provably > A Mensara Mind is a git repository in the customer's own account; the customer holds the keys. Mensara operates hosting machinery inside that boundary and holds no credential granting access to the repository after provisioning. Departure is a clone, not an export request. Canonical: https://mensara.ai/how-it-works/ownership ## Where it actually sits The repository, the keys, and the receipts live in an account with your name on it. Not a tenant inside ours. Not a workspace we administer on your behalf. Yours, in the sense your accountant would recognise. We hold no credential that opens it after the first day. ## What that buys you on a Tuesday You can clone it. Every file is plain text, readable without us and without any particular software. The history is there too, so you can see when a thing was decided and what it replaced. If you want to read the whole score on a plane with no signal, that is an afternoon's work and nobody's permission. This is the part people underestimate until the first time they use it. Not the moment you leave. The ordinary Tuesday you want to check something and find you simply can. ## Hosting is machinery, not custody Most owners would rather not run servers, so we run them. That is the whole of what hosting means here. The account is yours, the keys are yours, and we are operating equipment inside a boundary you control. What someone runs for you, they can end up holding over you. We built the boundary specifically so that cannot happen, and the rest of this section is the evidence for that sentence rather than the promise of it. ## Leaving, as a procedure Not a policy, a procedure. You take the repository, the keys, and the receipt chain. You point it at your own machine or a provider of your choosing. It works. The gate still refuses what it refused before, the receipts still verify against each other, and the score is the score. There is no export request, no thirty-day window, no negotiation with a retention team. The thing you would be leaving with is the thing you have had the whole time. ## Why we refuse We could hold it for you. It is a better business: the longer a company holds your knowledge, the more it costs you to go. We took the other side of that bet on purpose, and it is the reason to trust the rest of what we say. Build the Mind, hand over the keys, earn the renewal on the gardening. I ran a company out of my own head for years, and the thing I would not have accepted from anyone is a version where the memory was theirs. So I did not build one. Our first client can leave any day, with everything, working. That capacity is the product, not a risk we tolerate. **Status:** your account, your keys, from day one ## Prompt ```prompt Clone my Mind's repository to this machine, then tell me: how many files it contains, the date of the earliest entry in the history, and whether the receipt chain verifies end to end from the local copy alone. ``` ## Related - [Held at the gate](https://mensara.ai/how-it-works/governance) - [The score](https://mensara.ai/how-it-works/the-score)