Glossary

Quick reference for every term that appears across the TrainAR docs.

Core concepts

Tenant — your team's account on TrainAR. The boundary around your data. See Your tenant.

Seat — a paid licence for one engineer to wear the glasses and run training sessions. Billed monthly.

User — a Dashboard login. Users (admins, ops) don't wear glasses; they manage the tenant. There's no per-user charge — only per-seat.

Session — a single training run on the glasses, from "Start training session" to "Stop training session." Recorded, summarised, optionally extracted into a procedure.

Procedure — a structured, re-usable training procedure built from a trainer-mode session. Other engineers can load it in trainee mode and be coached through the same job.

Task — a unit of work assigned to an engineer (a job, a service call). Can be created manually or synced from a connected field-service system. Provides context to the AI for a session.

Skill — a tool the AI assistant can call during a session. Some are built-in (search_knowledge, capture_camera), some come from Marketplace bundles (pa_* for Parts & Spares), some you author yourself.

Knowledge — documents (manuals, procedures, specs) uploaded to your tenant that the AI can search in trainee sessions.

Bundle — a Marketplace package combining skills + knowledge + procedures, subscribable per seat per month. Either platform-built (TrainAR) or curator-built (third party).

Curator — a third party publishing a Marketplace bundle. Could be a manufacturer, trade trainer, or domain expert.

Modes and roles

Trainer mode — engineer is recording a procedure. The AI listens but stays mostly silent. Used to capture senior engineers' know-how.

Trainee mode — engineer is doing a job, with the AI actively coaching, looking at things on request, fetching information. Used for juniors learning, or experienced engineers hitting unfamiliar work.

Admin — full Dashboard access. Admin-only surfaces: Users, Seats, Billing, Integrations, API & Webhooks. (Dashboard roles today: Admin and Member only.)

Member — non-admin Dashboard user. Sees Dashboard, Tasks, Sessions, Skills & Knowledge, Marketplace, Reports, and their own My Seat. Doesn't see Users/Seats/Billing/Integrations/API admin tabs.

Trainer / Trainee (seat roles, NOT Dashboard roles) — each seat has one or both of these roles. Trainer-mode sessions capture procedures; trainee-mode sessions are AI-coached. A seat can hold both roles simultaneously.

On-glasses concepts

Core App — the application running on the AR glasses. Authenticates against your tenant, handles voice commands, streams video, hosts the AI participant.

Voice channel — the WebRTC stream between the glasses and the AI in TrainAR's cloud. Carries the engineer's voice and the AI's voice replies.

Server-side VAD — voice activity detection that runs in TrainAR's cloud (not on the glasses). Detects when the engineer's finished speaking so the AI can reply naturally — no hotword needed.

Start / Stop training session — the two voice phrases that open and close a session.

Skills, knowledge, and integrations

System skill — built-in AI capabilities present in every tenant (search_knowledge, capture_camera, end_session).

Platform skill — skills delivered via a Marketplace bundle (e.g. the five pa_* skills from Parts & Spares).

Tenant skill — skills you've authored yourself in Dashboard → Skills & Knowledge → Skills.

Knowledge collection — a grouping of related knowledge documents within a tenant.

Integration — a connection between TrainAR and an external system (FSM, CRM, automation tool). Connected from Dashboard → Integrations (top-level nav, not under Settings).

Writeback — when a completed TrainAR session pushes its outcome back to the source FSM (status update, summary, time, parts).

Marketplace

Marketplace — the in-Dashboard catalogue of bundles available to subscribe to.

Subscription — your tenant's paid access to a Marketplace bundle. Per seat per month.

Allocation — the seats within your tenant that have access to a specific bundle. You can subscribe a bundle to fewer seats than your total.

Developer surface

Tenant REST API — HTTP API for your tenant data, authenticated with a tak_* API key. See Tenant REST API.

Tenant MCP server — Model Context Protocol server exposing the same operations as the REST API, for AI agents. See Tenant MCP server.

Webhook — an HTTP POST TrainAR sends to a URL you control when an event fires (session ended, procedure extracted, task created, etc.). See Webhooks.

API key — credential for the Tenant REST API or Tenant MCP server. Starts tak_. Scoped to specific permissions.

Sessions and processing

Pre-flight — the ~2-second silent check at session start (voice channel up, video stream up, AI joined).

POV recording — the engineer's first-person video captured by the glasses during a session.

Session summary — the AI-generated narrative of what happened in a session ("the engineer serviced a Worcester Greenstar 30CDi, replaced the expansion vessel, tested gas tightness, signed off").

Procedure extraction — the 4-pass video analysis pipeline (Gemini 2.5 Pro) that converts a trainer-mode session into a structured procedure.

Minute pool — your tenant's allowance of session minutes. Consumed by active session time. Top up from Settings → Billing.

Hardware

INMO Air 3 — supported AR glasses model. Open-ear audio, binocular display, swappable battery.

Vuzix Blade 2 — supported AR glasses model. Monocular display.

Pairing code — 6-digit code generated in the Dashboard to associate a pair of glasses with an engineer.

Where to next

• Welcome to TrainAR — the 90-second pitch.
• Your first session — end-to-end walkthrough.
• Browse the topic categories from the home page.