> ## Documentation Index > Fetch the complete documentation index at: https://docs.puntego.com/llms.txt > Use this file to discover all available pages before exploring further. # Glossary > Plain-language definitions for the Puntego terms you meet across these docs, from the guide and targets to lanes, Verified Actions, and the visitor JWT. Short definitions for the terms that recur across the docs. Each entry links to the page where the concept is used in full. ## The guide and what loads it | Term | Definition | | ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | The guide | The on-page assistant Puntego renders for visitors. It reads the live DOM of the surface in front of the visitor and can point, highlight, scroll, narrate, run tours, and execute confirmed actions. See [Guide Tools SDK](/guide-tools-sdk). | | Boot script | The install snippet you add to your site — a single script tag that loads Puntego, calls `/boot`, and mounts the guide. It needs both `data-app-id` (your app ID, the `gp_` token) and `data-gp-api`. See [Install Puntego](/install). | | Runtime | The in-page engine the boot script loads. It inventories the live DOM, evaluates the route rules, mounts the launcher, and runs point, highlight, tour, and action requests. See [Configuration](/configuration). | | Visitor JWT | The short-lived bearer token minted at `/boot` (roughly a 15-minute TTL) that authorizes `/chat` as `Authorization: Bearer `. See [Authentication](/authentication). | ## Launcher and surface modes | Term | Definition | | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Bubble mode | The cursor launcher's fallback on touch-primary or narrow (under 768px) screens, where the cursor mode switches to a bubble experience. The default floating launcher does not switch — it keeps its floating button on those screens. See [Configuration](/configuration). | | Canvas mode | The mode the runtime enters when a canvas or WebGL surface covers more than \~60% of the viewport. The underlying controls are not exposed as DOM targets, so the guide works as a typed assistant rather than pointing at controls. See [Troubleshooting](/troubleshooting). | ## Targeting and configuration | Term | Definition | | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Target | A control or element on the page the guide can point at, highlight, or act on. The guide resolves targets from the live DOM the visitor has loaded. See [Guide Tools SDK](/guide-tools-sdk). | | Declared target | An owner-registered target — the highest-priority grounding tier. The guide resolves a declared target before falling back to live-DOM heuristics, and click actions must bind to one. Register declared targets through the SDK (`registerTarget`) or your workspace settings. See [Guide Tools SDK](/guide-tools-sdk). | | Manifest | The workspace configuration returned by `/boot`: branding, consent directive, enabled guide tools, declared targets, and allowed actions. The runtime can only use page actions that are enabled for the workspace and declared by the manifest. See [Configuration](/configuration). | | Runtime-map | A dashboard view of your account's live runtime state — active knowledge sources, playbooks, declared targets and actions, privacy mode, and open Needs Attention items — that the owner assistant reads to reason about the account. | | Agent-home | The owner-facing dashboard home that packs the runtime-map together with guardrails, guide tools, declared targets, model lanes, memory policy, and recommended next actions into one view. | | Lane | An isolated runtime path with its own model, capabilities, token budget, and privacy rules. The model lanes are Visitor guide (the on-page assistant), Owner operator (dashboard drafting), Voice IO (speech transport), and Workflow eval (offline checks). Owners enable specific lanes and action instances rather than flipping one global switch. | | Needs Attention | The owner review queue. The workspace flags items here for review — unanswered questions, failed actions, missing or stale sources, contradictions, escalations, and policy blocks — and Verified Action problems land here too. See [Verified Actions](/verified-actions). | ## Verified Actions | Term | Definition | | ----------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Verified Action | A customer-approved tool that lets the guide read or change a narrow business object after policy checks. It is not a generic API agent: every action targets one fixed operation, runs server-side, and starts disabled until an owner enables it. See [Verified Actions](/verified-actions). | | Curated template | One of the seven pre-built Verified Action templates, each with a fixed schema, risk class, identity requirement, and confirmation requirement. Six of the seven ship a managed adapter you connect from the dashboard. See [Verified Actions](/verified-actions). | | Custom read-only action | A manually scoped read-only Verified Action for when no curated template fits. It calls one fixed method against one fixed base URL and path, with an input schema, output schema, per-minute rate limit, and a test input; the redaction map is optional. See [Verified Actions](/verified-actions). | ## Next steps Add the boot script and its required data attributes. Register targets and shadow roots so the guide can reach more of your page. Curated templates, custom read-only actions, and the policy gate. Diagnose boot, chat, voice, and visible-page issues.