Introductory guide · map derived from the surfaces registry

One conversation, and the pages that govern it

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.

13administration pages4Settings sections

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.

One conversation, two channelsHow Settings is arrangedWho may see whatWhen you cannot find a page
01

One conversation, two channels

You can talk to Metnos from the instance's web chat or from Telegram. It is the same conversation and the same authority; only the delivery changes. One difference matters to you: the 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.

02

How Settings is arranged

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. The path you see is an interface label, not translated text: the Settings shell is rendered in Italian even when the rest of the conversation is in another language, so the path stays exactly as you read it here.

Map of the Metnos interfaceFrom the two conversation channels to Settings, and from Settings to the four sections with their administration pages, each with its own address.the same conversationweb chatTelegramSettings opens here onlySettings/admin · status overview01ActivityTurns/admin/turnsScheduler/admin/runsTimers/admin/timersIndex builds/admin/builds02LifecycleChanges/admin/changesExecutors/admin/executorsStatistics/admin/executors/stats03MemoryPraxis/admin/praxis04SystemServices/admin/servicesSafety/admin/safetyUsers/admin/usersDevices/admin/devices
Reference map: paths and addresses are the ones held by the surfaces registry. What each page shows, and what you can do there, the Tutor recounts on the instance in front of you.

Overview

  • SettingsSettings · /admin

    Status overview and access to the administration areas.

Activity

  • TurnsSettings > Attività > Turni · /admin/turns

    Requests with channel, actor, steps, and outcome.

  • SchedulerSettings > Attività > Scheduler · /admin/runs

    Scheduled-task runs with outcome and duration.

  • TimersSettings > Attività > Timer · /admin/timers

    System timers, state, and available controls.

  • Index buildsSettings > Attività > Build indici · /admin/builds

    Index builds with progress, state, and ETA.

Lifecycle

  • ChangesSettings > Ciclo di vita > Modifiche · /admin/changes

    Change proposals and their approval lifecycle.

  • ExecutorsSettings > Ciclo di vita > Executor · /admin/executors

    Installed executors, membership, state, and exclusion reasons.

  • StatisticsSettings > Ciclo di vita > Statistiche · /admin/executors/stats

    Operational executor statistics.

Memory

  • PraxisSettings > Memoria > Praxis · /admin/praxis

    Cognitive-engine layer state and related configuration.

System

  • ServicesSettings > Sistema > Servizi · /admin/services

    Metnos services with state, health, installation, PID, and controls.

  • SafetySettings > Sistema > Safety · /admin/safety

    Signatures governing executor authorization and confirmation.

  • UsersSettings > Sistema > Utenti · /admin/users

    Users, roles, and associated channels.

  • DevicesSettings > Sistema > Dispositivi · /admin/devices

    Paired remote devices that run executors.

03

Who may see what

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.

04

When you cannot find a page

You do not need to memorize this map. Ask the Tutor 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.