Operational reference · generated from the canonical catalog

What you can ask Metnos, domain by domain

This page describes every canonical domain in the Metnos vocabulary. Each example is a sentence you can use directly in chat: no executor names, arguments, or technical syntax are required.

26canonical domains98documented operations

The reference structure comes from the runtime's 26 canonical objects; names and counts of distributed operations come from signed manifests and builtin contracts. Installed skills may add providers and operations. Ask the Tutor to learn what is currently available on your instance.

Content and computation Result composition Communication and time Web, places, and media Collaboration and providers Control and administration Cross-domain utilities

Content and computation

Files, structures, and local transformations.

files

Files

19 documented operations

Finds, reads, creates, converts, moves, shares, and analyses local files or files supplied by a provider. This includes documents, spreadsheets, PDFs, OCR, archives, hashes, and lines of code.

Boundary. This domain concerns the file container. Use Images for the visual meaning of a photo and URLs for a public web page.

Ask Metnos with a request like this example:“Find every PDF changed this week in Projects and summarise the ones about Atlas.”

Ask Metnos with a request like this example:“Compute the SHA-256 hashes and lines of code of the Python files in the runtime folder.”

Distributed operations (19)

change_files_formatcompress_filescompute_files_loccreate_files_doccreate_files_spreadsheetdelete_filesfind_filesget_filesmove_filesread_filesread_files_csvread_files_docread_files_ocrread_files_spreadsheetread_files_xlsxshare_fileswrite_fileswrite_files_docwrite_files_spreadsheet

dirs

Folders

4 documented operations

Lists, finds, creates, and deletes directories, including on a remote device when the plan requires it.

Boundary. A folder organises files; it does not represent their content. Unsafe deletion remains subject to the normal gates.

Ask Metnos with a request like this example:“Show the subfolders under Photos ordered by size.”

Ask Metnos with a request like this example:“Create the Clients/2026 folder on the office laptop.”

Distributed operations (4)

create_dirsdelete_dirsfind_dirslist_dirs

packages

Installed programs

1 documented operation

Checks whether an executable command or program is available in the selected system PATH.

Boundary. It detects availability and location; it does not automatically install unrequested packages.

Ask Metnos with a request like this example:“Check whether ffmpeg is installed on this server.”

Ask Metnos with a request like this example:“Where is python3 on the paired Windows PC?”

Distributed operations (1)

find_packages

numbers

Numbers

1 documented operation

Computes descriptive statistics over numeric values: count, minimum, maximum, mean, and other admitted summaries.

Boundary. It receives explicit numbers or values produced by a previous step; it is not a persistent spreadsheet.

Ask Metnos with a request like this example:“Compute the mean, minimum, and maximum of 12, 18, 21, 21, and 34.”

Ask Metnos with a request like this example:“Find this month's invoices and tell me the average spend.”

Distributed operations (1)

describe_numbers

texts

Texts

1 documented operation

Filters and transforms text already available, at granularities such as lines, paragraphs, or segments.

Boundary. It works on in-memory text; extracting it first from a file, message, or page requires the corresponding source domain.

Ask Metnos with a request like this example:“From the log I gave you, keep only lines containing timeout or retry.”

Ask Metnos with a request like this example:“Read the document and show only the paragraphs containing a date.”

Distributed operations (1)

filter_texts_lines

Result composition

Internal steps joining several capabilities in one request.

entries

In-memory results

11 documented operations

Sorts, filters, groups, classifies, compares, extracts, and summarises structured rows produced during the same turn.

Boundary. This is an internal composition domain: people describe the desired result and do not need to know the name entries.

Ask Metnos with a request like this example:“Find July's invoices, group them by supplier, and order them from most expensive.”

Ask Metnos with a request like this example:“Find open issues, classify them by urgency, and show only critical ones.”

Distributed operations (11)

classify_entriescompare_entriescompute_entriesdelete_entriesdescribe_entriesextract_entriesfilter_entriesfind_entriesgroup_entriessort_entrieswrite_entries

lists

List comparison

1 documented operation

Compares two result sets to find common, new, or missing items using explicit keys.

Boundary. Lists must come from the same plan or an identifiable source; comparison does not invent matches.

Ask Metnos with a request like this example:“Compare the files in these two folders and show those present only in the second.”

Ask Metnos with a request like this example:“Which issues are new compared with yesterday's saved list?”

Distributed operations (1)

filter_lists

Communication and time

Messages, address books, calendars, and future activities.

messages

Messages and mail

4 documented operations

Finds, reads, sends, replies to, labels, moves, or deletes messages through configured accounts, including IMAP/SMTP, Gmail, and admitted channels.

Boundary. The account can be selected when several exist. Sending, replying, and deleting retain consent and traceability.

Ask Metnos with a request like this example:“Using my work account, find Marta's messages from the last seven days with PDF attachments.”

Ask Metnos with a request like this example:“Reply in the same thread that the meeting is confirmed, but show me the text first.”

Distributed operations (4)

move_messagesread_messagessend_messagesset_messages

events

Events

4 documented operations

Reads, creates, and deletes appointments and finds free intervals in accessible calendars.

Boundary. An event is an appointment. Calendars manages containers; Scheduled tasks executes requests in the future.

Ask Metnos with a request like this example:“Find a free hour on Tuesday afternoon across my calendar and Anna's.”

Ask Metnos with a request like this example:“Create a 45-minute meeting with Luca on Friday at 10.”

Distributed operations (4)

create_eventsdelete_eventsfind_events_emptyread_events

contacts

Contacts

2 documented operations

Finds and reads address-book records containing names, email addresses, and phone numbers, locally or from a connected account.

Boundary. A contact is an address-book record. Persons instead represents local identities and recognition in photos.

Ask Metnos with a request like this example:“Find Laura Bianchi's email address in my contacts.”

Ask Metnos with a request like this example:“Show the phone number for the Acme Support contact.”

Distributed operations (2)

find_contactsread_contacts

tasks

Scheduled tasks

6 documented operations

Creates, reads, changes, and deletes reminders or recurring requests and retains execution history. Skills may add remote tasks such as GitHub workflows.

Boundary. A task executes a request at a time or trigger; it is not a calendar appointment.

Ask Metnos with a request like this example:“Every Monday at 8, read unread mail from my work account and send me a summary on Telegram.”

Ask Metnos with a request like this example:“Show the latest outcomes of the Photo backup task and any errors.”

Distributed operations (6)

create_tasksdelete_taskslist_tasksread_tasksread_tasks_historyset_tasks

calendars

Calendars

2 documented operations

Creates and removes calendar containers, distinct from the appointments they contain.

Boundary. Deleting a calendar may also delete its events and is therefore a destructive gated operation.

Ask Metnos with a request like this example:“Create a new Google calendar named Support shifts.”

Ask Metnos with a request like this example:“Delete the Test 2025 trial calendar and all its contents.”

Distributed operations (2)

create_calendarsdelete_calendars

Web, places, and media

Public information, web sessions, and visual archives.

places

Places

2 documented operations

Finds real-world places from text or coordinates and converts GPS coordinates into geographic names.

Boundary. The user's current location is a separate system utility; Places interprets or searches destinations.

Ask Metnos with a request like this example:“Find a pharmacy near Piazza Maggiore in Bologna.”

Ask Metnos with a request like this example:“Which place corresponds to coordinates 45.4642, 9.1900?”

Distributed operations (2)

find_placesget_places

urls

Web and URLs

5 documented operations

Searches the web, fetches known URLs, and reads public HTML pages or PDFs, extracting text and metadata.

Boundary. A public page without session state belongs to URLs. Use Sites for an authenticated, interactive website.

Ask Metnos with a request like this example:“Search the web for the latest European guidance on digital product passports and cite the sources.”

Ask Metnos with a request like this example:“Read this online PDF and summarise requirements, deadlines, and intended audiences.”

Distributed operations (5)

find_urlsget_urlslogin_urlsread_urls_htmlread_urls_pdf

images

Images and photographs

9 documented operations

Describes images, builds and queries local indexes, searches by content, person, or similarity, searches web images, and accesses Google photos created through Metnos.

Boundary. Generic path operations remain in Files. Google Photos exposes only items allowed by its API and mandate.

Ask Metnos with a request like this example:“In the photo archive, find images of Carlo by the sea at sunset.”

Ask Metnos with a request like this example:“Search the web for a reusable aerial photograph of Milan Cathedral.”

Distributed operations (9)

create_images_indicesdelete_images_indicesdescribe_imagesfind_images_google_photosfind_images_indicesfind_images_webget_images_google_photosget_images_indiceswrite_images_google_photos

persons

People and local identities

5 documented operations

Manages a local named-person registry and links recognised faces to people in photographs; it can also read the current actor's profile.

Boundary. It is not an address book: email addresses and phone numbers belong to Contacts. Biometric data and deletion have dedicated controls.

Ask Metnos with a request like this example:“Register this photo as Francesca Riva's face.”

Ask Metnos with a request like this example:“Find every archive photo containing Francesca.”

Distributed operations (5)

delete_personsfind_persons_indicesget_personsread_personsset_persons

sites

Stateful sites

5 documented operations

Opens a persistent browser session, reaches login using protected credentials, reads page state, and performs narrow-mandate web actions.

Boundary. Credentials are injected by the broker and never shown to the model. Sensitive actions require confirmation.

Ask Metnos with a request like this example:“Sign in to the courier portal and tell me where shipment 12345 is.”

Ask Metnos with a request like this example:“Open the bank website, download June's statement, and stop before making any transaction.”

Distributed operations (5)

act_sitesdelete_siteslogin_sitesopen_sitesread_sites

Collaboration and providers

Extensions and shared work objects.

issues

Issues

0 documented operations

Through a provider skill, finds, reads, creates, updates, or closes project issues with state, labels, and assignees.

Boundary. The currently documented provider is GitHub and requires configured credentials; effective capabilities depend on the skills admitted by the instance.

Ask Metnos with a request like this example:“In the metnos repository, find open issues labelled bug created in the last week.”

Ask Metnos with a request like this example:“Create an issue in acme/app with this title and assign it to Laura.”

Distributed operations (0)

This domain becomes available when an admitted skill or provider installs its operations.

pulls

Pull requests

0 documented operations

Finds and reads pull requests, diffs, and review state; updates or merges a request when the provider and mandate allow it.

Boundary. It is distinct from issues because it includes code changes, reviews, and merge. Mutating operations are gated.

Ask Metnos with a request like this example:“Show open pull requests in acme/app that modify the security folder.”

Ask Metnos with a request like this example:“Read PR 42's diff, summarise the risks, and stop before merge.”

Distributed operations (0)

This domain becomes available when an admitted skill or provider installs its operations.

skills

Skills

2 documented operations

Lists and manages installed extensions that can add executors, providers, and specialised knowledge to the local catalog.

Boundary. A skill is admitted through verification and policy; installing one does not bypass vocabulary, sandboxing, or consent.

Ask Metnos with a request like this example:“Which skills are installed and which are enabled?”

Ask Metnos with a request like this example:“Enable the already installed GitHub skill and show which capabilities it adds.”

Distributed operations (2)

list_skillsset_skills

Control and administration

Observability, consent, security, and configuration.

processes

Processes and system health

1 documented operation

Obtains a snapshot of processes and system-health signals on the local system or an eligible device.

Boundary. This is observation, not arbitrary shell administration: available actions remain those of admitted executors.

Ask Metnos with a request like this example:“Which processes are using the most memory on this server?”

Ask Metnos with a request like this example:“Check the office PC's health and show any anomalous processes.”

Distributed operations (1)

get_processes

signatures

Security signatures

3 documented operations

Computes, reads, and curates canonical signatures used to classify system commands and actions into allowed, uncertain, or forbidden policy sets.

Boundary. This is an administrative security domain, not cryptographic signing of user documents.

Ask Metnos with a request like this example:“Show the signatures currently on the greylist and their classification.”

Ask Metnos with a request like this example:“Compute the canonical signature of the proposed command without executing it.”

Distributed operations (3)

compute_signaturesget_signaturesset_signatures

proposals

Evolution proposals

1 documented operation

Exposes local proposals awaiting review, such as capability deduplication, generalisation, or specialisation.

Boundary. Reading a proposal does not approve it. Acceptance, rejection, and rollback occur through the designated administrative surfaces.

Ask Metnos with a request like this example:“Show the deduplication proposals still awaiting review.”

Ask Metnos with a request like this example:“Explain this proposal, its risks, and how to reach the page where I can approve it.”

Distributed operations (1)

get_proposals

inputs

Structured input

1 documented operation

Collects missing information in typed dialogs and forms, including choices, dates, files, and sensitive fields.

Boundary. It is an interaction capability used inside an operation; people normally do not invoke it by name.

Ask Metnos with a request like this example:“Prepare a new mailbox and ask me for the missing server, port, and username in a form.”

Ask Metnos with a request like this example:“Create the event; if you do not know which calendar to use, let me choose from those available.”

Distributed operations (1)

get_inputs

approval

Human approval

1 documented operation

Presents an Approve/Reject choice and continues along the allowed branch while preserving preview, actor, and traceability.

Boundary. It is a gate, not a shortcut: approval does not expand executor authority or make a forbidden action permissible.

Ask Metnos with a request like this example:“Prepare deletion of duplicate files, show me the list, and ask for approval before proceeding.”

Ask Metnos with a request like this example:“If the quote exceeds 500 euros, stop and ask for my confirmation.”

Distributed operations (1)

get_approval

credentials

Credentials

3 documented operations

Configures, lists by metadata, and deletes encrypted bindings for mailboxes, APIs, cloud services, and authenticated sites.

Boundary. Clear-text secrets never return to the planner or Tutor. Multiple accounts of the same type remain selectable through distinct bindings.

Ask Metnos with a request like this example:“Configure a second IMAP mailbox named personal and ask me for credentials securely.”

Ask Metnos with a request like this example:“Which email accounts and cloud providers are configured, without showing any secret?”

Distributed operations (3)

delete_credentialsfind_credentialsset_credentials

Cross-domain utilities

Primitives assisting several domains.

_system

Cross-domain utilities

4 documented operations

Provides reliable date and time, the last observed location, undo for the latest reversible turn, and expert consultation when admitted.

Boundary. These are cross-domain primitives, not new data domains. Undo operates only on effects with a recorded compensation.

Ask Metnos with a request like this example:“What time is it in Tokyo right now?”

Ask Metnos with a request like this example:“Undo the reversible operations from my last turn.”

Distributed operations (4)

consult_frontierget_locationget_nowundo_last_turn

Providers and actual availability

Domains are stable; providers are a separate axis. An instance may use local filesystems and devices, IMAP/SMTP mailboxes, the public web, GitHub, Google Workspace, or Google Photos according to admitted credentials, skills, and policy. The Tutor reads the instance's live catalog and answers about current availability.