Skip to main content
A short glossary. Every page in these docs uses these terms the same way.
The human using Mesh Pilot. A marketer, head of growth, or agency lead. You’re an operator.
A D2C account under management — typically one Shopify store, one HubSpot pipeline, or one outbound ICP. A single operator can run multiple brands inside one workspace.
One of six specialist marketing executors: Ads, Sales, Social, Creative, Voice, and SEO. Agents draft moves; they never execute money moves without your approval. Agents are attribution metadata — they show up as “From: <agent>” badges on proposals, never as nav destinations.
An agent-drafted action awaiting your decision. Examples: pause an underperforming ad set, send a follow-up email, publish a scheduled post. Every proposal lives in the Inbox until you act.
Your accept, edit, or reject decision on a proposal. Approvals are the cockpit’s load-bearing primitive. When you approve, the orchestration engine writes the change back to the source-of-truth tool (Meta, Shopify, HubSpot, etc.).
A cross-agent flow. Example: an Ads anomaly triggers a Creative refresh proposal, which when approved drafts a Social variant. Loops are how multiple agents collaborate on one operator intent.
A per-action-type rule that lets an agent auto-fire after N consecutive operator approvals under a daily cap. You set thresholds in Settings. Anything risky stays gated behind explicit approval.
The learning layer. Each agent emits observations as it works. When a pattern is corroborated across multiple brands, the brain promotes it into anonymized cross-brand wisdom that every agent can recall. Patterns never contain brand-identifying data.
Brand-scoped or operator-scoped facts. “Our ROAS target is 3x.” “Discontinue the GoodGut SKU.” Once saved, every agent on that brand reads memory before asking you a question that’s already been answered.
The billing container. One workspace per customer; many brands inside; many operator seats. Brands are the main expansion lever as you grow.
Access is scoped two ways. Per-brand: each member is a viewer (read-only) or operator (read + write) on each brand. Workspace: owner / admin manage the whole workspace (team, org-wide audit); operator / viewer are scoped to their brands. See Roles & permissions.
A capability-scoped API key that lets an AI client (Claude, Cursor, etc.) drive Mesh Pilot over the Model Context Protocol. Each key is bounded to specific brands, platforms, and read/write access — never more than its minter can do. See Developers & MCP.
The bridge between upper-funnel Meta spend and Amazon sales. Ref-tags tie tagged Meta→Amazon clicks to campaigns; the sessions-delta halo models the indirect lift Meta drives on Amazon. See Attribution.
A deterministic check result from the Amazon Health audit (buy-box, images, conversion, keywords, …). Findings surface in the Inbox with evidence and, where possible, a proposed fix. See Amazon Health.
Mesh Pilot does not replace your tools. HubSpot stays the source of truth for deals, Shopify for orders, Meta for ad state. We orchestrate flows across them and mirror enough state inside the cockpit that you never have to leave to verify what just happened.