MENSARA.AI · A GOVERNED MIND, IN YOUR ACCOUNT

MENSARA.AI · ASK YOUR FIRST USEFUL QUESTION · AGENT VIEW · TEXT/MARKDOWN

# First-read procedure

Prerequisite: owner-provided authenticated MCP setup and a principal with a granted zone. No supported client/version onboarding is verified here. Do not create a connection, provision a Mind, or use an owner identity to bypass denial.

`orient` and `list_zones` have no required arguments. `read` requires `path` and accepts `memory_view` of `current` or `evidence`; `list_files` accepts `dir` and `pattern`. Authorization is established by the MCP bearer layer, not made valid by an optional schema token field.

**Template only — placeholders come from this principal's discovery results.**

```
orient({})
list_files({"dir":"<granted directory from discovery>"})
read({"path":"<discovered map path>","memory_view":"current"})
read({"path":"<authorized note linked by the map>","memory_view":"current"})
```

After every call, parse the JSON carried in the MCP text item. For a full successful read, expect `ok=true`, `content`, `zone`, and `redactions`; ranged modes may report truncation. Cite the actual accessible path and passage. `{"ok":false,"error":"access denied"}` is a stopping condition. Do not retry it under another identity or expose the denied zone. Treat `not found` and `repository busy, try again` according to their stated condition.

The synthetic in-process Gateway examples are not MCP transport outputs. There is no established retry/idempotency rule beyond inspecting the result and retrying only an explicit busy condition.

These reads do not change the requested knowledge content. They can append signed audit receipts, so they are not free of persisted side effects. A receipt records an operation; it does not independently prove that an answer is correct.

## Continue

[Current memory and evidence](/how-it-works/current-and-evidence) · [Read and proposal permissions](/how-it-works/read-and-propose)

[Generated tool input reference](/how-it-works/tool-inputs.md)