Find the installed version
Open Settings in your Mind’s Portal. Its About footer shows the Portal’s Mensara version. Have the authorised owner or operator confirm the matching Core release when a procedure depends on it. App versions are separate: inspect the installed bundle, not only the latest store card.
The Portal’s Connection status includes Version supported. A pass there establishes that connection’s compatibility check; it does not prove every optional app or feature is enabled.
Use the requirement on the relevant guide
For example, team Views require Core 0.20.11 and Portal 0.3.47 or later. Telegram capture requires compatible Telegram connection support and the selected sensor. Network also depends on owner permission, workspace enablement and an accepted peer connection.
Compare the requirement with your actual installation. When a required control is absent, first check role, delegation and feature enablement. An absent button is not proof that your data is missing or that another person has the same view.
Changes in the release used by these guides
Mensara 0.20.11 pairs Core with Portal 0.3.47. It adds local, reviewed Views over saved records, with viewer-scoped reads and a View-building skill. It also improves search and query behaviour, history presentation and the handling of a pending Network invitation lookup.
Search and query results can include a matched passage and date. Open the source to check the claim rather than treating a result excerpt as the whole record. Saved history preferences guide answer form; they do not authorise actions or widen access.
Earlier 0.20.10 installations remain a distinct compatibility case. The earlier selected app snapshot is retained in these guides where it still describes the offered bundle. It does not prove the newest published app artifact has been selected or installed in your Mind.
Upgrade through the supported owner route
Before an upgrade, inspect release notes for the affected job, back up the Mind and keep a current Recovery Kit. Have the authorised operator use the supported upgrade process for that environment. Do not edit version files or install a source checkout to make a missing feature appear.
After the upgrade, check the actual version, a harmless read, important permissions and any affected scheduled job. Record a useful output from the normal route. Installation success alone does not establish that a scheduled model or external service ran.
If the guide and interface disagree
Keep the installed versions, role, relevant app and the exact difference. Follow help by symptom and use the supported handoff rather than guessing a replacement call. A procedure can explain a refused or unavailable route without claiming that positive task was completed.
Related
Practical guides for people and agents