The Tutor lets people ask Metnos what it can do and how to use it, with answers derived from the system actually installed. It is local, owns no tools, and cannot turn an explanation into an action.
The planner is designed to compose operations. Using it as a manual would produce unnecessary plans or answers based on prompt memory. Before the planner, the Tutor intercepts only high-confidence explanations; actions and uncertain cases continue through the normal path.
They describe capabilities, availability, effects, and arguments of loaded and verified executors. The compiler indexes both the general description and each argument's bilingual description, so details such as multiple accounts, allowed values, and credential bindings are not lost. Catalog changes update knowledge without editing Tutor cards.
Every indexable HTML page published from docs/ on metnos.com is automatically a source. Deployment and Tutor share the same validated inventory; noindex redirects and pages outside the site do not enter it.
tutor/sources.toml remains only for selected non-public or runtime sources. User data, logs, reports, and internal documents stay excluded unless deliberately admitted.
An explicit projection of the canonical registry supplies the identity and structure of Settings > Services. Active status remains live page data, not a Tutor catalog claim.
Precedence by claim type. The manifest wins for installed capabilities; the curated guide for UI steps; documentation provides explanation and context; the runtime registry governs components listed by Settings. A conflict remains visible.
The compiler first separates each page along headings and sections, then splits oversized blocks into bounded units. It produces local BGE-M3 embeddings and stores text, vectors, hashes, and metadata in the same signed SQLite artifact. The candidate passes integrity and signature checks before atomic swap; a last-known-good enables recovery. Rebuilds reuse unchanged vectors by hash.
Retrieval passes only semantically relevant chunks to the composer and, when continuity is useful, adjacent chunks from the same page. A long manual is never placed in the answer-composition prompt as a whole.
Ranking combines dense similarity with a small lexical signal derived dynamically from the texts. It contains no synonym lists or anticipated formulations.
Tutor admission is semantic too: after structural checks for secrets, control
commands, and canonical operational verbs, a closed local classifier distinguishes
EXPLAIN, ACT, MIXED, and
UNKNOWN. There is no list of phrases such as “how do I,” no special
topics, and no per-question exceptions.
If F2 is not loaded yet. On the first HTTP startup, compilation completes before the listener accepts requests. If compilation fails and no valid catalog can be recovered, Metnos still starts the operational engine: a question recognized as Tutor receives the localized “Tutor temporarily unavailable” message and is not turned into a plan or action. Operational requests continue along their normal path. On the reference node on July 23, 2026, validation of an unchanged catalog took about 2 seconds; an incremental rebuild of 2,047 units took about 26 seconds. These are observations, not an SLA: time varies with hardware and corpus size, while hash reuse avoids recomputing unchanged vectors.
Each public page's language comes from <html lang>; a new valid
language enters the inventory without a compiler change. Fallback is per concept:
requested language, then English, then another available translation. The embedding model is multilingual;
the composer answers in the current language even when the source is English.
Manifest descriptions are i18n maps: IT/EN required for active executors, other
languages admitted.
| Constraint | Guarantee |
|---|---|
| No tools | The composer receives only the query and filtered sources. |
| Audience before model | An admin source never enters a user's context. |
| Safe fallthrough | ACT and UNKNOWN return to the engine; MIXED asks for separation. |
| Pending preserved | A help question never consumes an existing approval or dialog. |
| Honest gap | No sufficient source means “not documented,” not “impossible.” |
| Distinct outcomes | A source gap is not conflated with a technical catalog or composer failure. |
| Follow-up questions | The latest Tutor exchange remains in memory for 15 minutes, isolated by user, role, channel, and conversation. It is used only when it materially improves semantic retrieval; it is not written to telemetry and disappears on restart. |
| Natural example first | For an operational or configuration question, the answer starts with an adaptable natural request example; contract and technical details follow. |
| Settings surfaces | When the source is a UI page, the Tutor gives its literal path and visible content first. On Telegram it states that the path starts in the Metnos web chat; for example Settings > Sistema > Servizi, route /admin/services. |
The complete domain reference covers all 26 canonical domains, their boundaries, and adaptable natural-language requests. The page is also a Tutor source: publishing or updating it enriches the catalog at the next rebuild without a separate registration.
Scheduled activities include recurring tasks, reminders, and schedules. You do not need to open the console or learn a special syntax. Ask Metnos in natural language, stating what it should do and when. For example: “Every morning at 8, read my email and flag deadlines and urgent messages.” Metnos shows the resulting schedule and applies the normal gates. Name a delivery channel if you want the result sent elsewhere. For a one-off run, omit the recurrence and ask for the operation directly.
To search, name the local archive or folder and describe what you want to find. Metnos can use an existing persistent index or propose creating one when it is missing; index creation passes through the normal gates. For example: “In the 2025 Photos archive, find pictures of Roberto by the sea.” Web search and Google Photos are separate capabilities: name them explicitly when you want to use them instead of the local archive.
Settings > Sistema > Servizi and presents its path and visible content.Counterexample: “Read all my email” is an action and does not belong to the Tutor.
Not released yet. F3 will add typed, ownership-aware capsules for service, task, device, and executor state. F4 will cluster redacted gaps locally, distinguish missing sources, stale sources, conflicts, and composition problems, then produce observable change intents with replay and rollback.
F4 gap examples: “Can I run the digest only when the laptop comes back online?”, “How do I connect a mailbox from a provider the manual does not name?”, and “Why do two pairing explanations have different depth?”.