What it will not do.

01

The door doesn't open by accident

Every request to your Mind starts from zero. Nobody gets in because a zone was left open by mistake, and no agent inherits access it was never given. A person or a process has to be granted a specific zone, by name, before a question can be answered from it.

Say a contractor joins your Mind with access to the client-facing zones and nothing else. They ask a question that would need the pricing model, kept in a zone they were never granted. The gate does not weigh how reasonable the request sounds. It refuses, the same way it would refuse a stranger who wandered in off the street. There is no ambiguous middle case where it guesses in your favor.

02

New capability starts on probation

Nothing gets to act inside your Mind at full trust on its first day. New code, a new automated behaviour, a new integration all arrive through what we call the airlock. Each is reviewed before it runs and starts at the least trust that lets it do anything useful at all.

Trust after that is earned on a track record, not granted at install and left alone. Update something that already earned trust and the update goes back through the same door: being established once does not exempt anything from being checked the next time it changes. Nothing is grandfathered in quietly.

03

What we can see, and what we structurally cannot

Once your Mind is set up, Mensara's own infrastructure holds no standing credential that could open it. The boxes running your Mind reach out to us, using tokens that expire quickly and are replaced. We do not reach in.

That is not a setting we could change on a bad day, and not a rule a new hire could quietly override. It is the direction the connection runs. Our central infrastructure has no standing way to read into your Mind, because the architecture never gave it one to begin with. You are not trusting a policy here. You are trusting a shape.

Certain rules about how your Mind is allowed to behave sit above even that. Changes to them go to a human for review every time, with no fast path, regardless of how much trust anything else in the system has earned elsewhere.

04

Refusals are not silent

When something is denied, held at the gate, or simply goes wrong, that event gets a receipt of its own. It is not swept aside just because the action never went through. You can find it later, see exactly what was asked, and see exactly why it did not go through.

You have already seen one of these, on the Receipts page: a real denied read against a zone marked secrets, chained directly to the allowed request that came before it. This page will not repeat that artefact. The mechanism behind it is the one this page has just described, and the refusal it shows is the same kind.