You use Metnos by talking to it. The interface exists for the two things a conversation alone does poorly: showing you the state of the system and letting you act on what governs it. This page tells you how it is arranged, so you do not have to hunt for it.
The prose on this page is curated; the list of pages, their navigation paths, and their routes derive from the runtime's surfaces registry, so they cannot age separately from the product. This is the map, not the inventory: the visible fields, controls, and procedures of each page live once in the registry, and the Tutor recounts them if you ask.
You can talk to Metnos from the instance's web chat or from Telegram. You reach the same system with the same identity and authority, but each channel retains its own conversation and history. Administration pages exist in the web chat only. If you are writing from Telegram and an answer points you to a Settings path, open that path in the web chat, not inside Telegram. On the web channel, if you open the chat on a second device while the first one is active, Metnos offers three choices: Cancel changes nothing and leaves the new browser read-only; Make this session active uses the conversation already present in the new browser; Continue the previous session transfers the first device's conversation to the new browser. The two histories are not merged, and the revoked browser becomes read-only. These sessions and their histories are independent for each user: an owner session conflict does not involve a guest, and vice versa.
Settings is the administrative part of the web chat. It opens on a status overview and branches into four sections. Every page is reached as “Settings > Section > Page” and answers at an address starting with /admin. Labels are available in Italian and English; in a language not yet translated, the interface shows the English version. The Tutor quotes the path exactly as it appears in the interface.
/adminStatus overview and access to the administration areas.
/admin/turnsRequests with channel, actor, steps, and outcome.
/admin/runsScheduled-task runs with outcome and duration.
/admin/timersSystem timers, state, and available controls.
/admin/buildsIndex builds with progress, state, and ETA.
/admin/changesChange proposals and their approval lifecycle.
/admin/executorsInstalled executors, membership, state, and exclusion reasons.
/admin/executors/statsOperational executor statistics.
/admin/praxisCognitive-engine layer state and related configuration.
/admin/virtEffective configuration for language, embedding, and vision models: LLM and VLM are editable; embedding is view-only.
/admin/servicesMetnos services with state, health, installation, PID, and controls.
/admin/safetySignatures governing executor authorization and confirmation.
/admin/usersUsers, roles, and associated channels.
/admin/devicesPaired remote devices that run executors.
The pages under /admin require the instance administrator role: an invited guest cannot open them. Knowing that a page exists and what it contains is a different matter from opening it, and the two permissions are distinct: the Tutor explains a page to whoever is allowed to know it, even when access stays reserved to the administrator.
You do not need to memorize this map. Ask Metnos with a request like this example: “Show me which embedder is configured under Settings > System > Models and guide me there from the web chat.” The Tutor answers in both the web chat and Telegram, but the path it gives you always opens in the web chat. When you ask where something is or what a page contains, it answers with the path, the address, and the contents attested by the instance in front of you, not by generic documentation. If the page does not exist in your installation it says so, instead of inventing it.