Glossary

AaaS (Agent as a Service) is the subscription model: merchants and organizations pay periodically to own a hosted, maintained and distributed agent. It runs alongside CPL and SC — subscription covers ownership and operation, leads and success fees cover acquisition and outcomes.

The Agent Distribution Network (ADN) is the layer that distributes agents across surfaces — deciding which agent appears on which page, in which city and for which industry. Every routing decision carries an explainable trace with reason, confidence and priority source.

Agent Engine Optimization (AEO) is the practice of improving how visible and recommendable a business is inside AI conversations and agent distribution. Unlike SEO, which targets search rankings, AEO targets whether the AI knows you, understands you and is willing to recommend you — its core assets are facts, knowledge and real experience.

An Agent is the platform's fundamental intelligent unit — a conversational entity with identity, knowledge, capability and boundaries, representing a merchant, industry, organization or lifestyle scenario. Four parts define what it may say, must not say and can do. The platform recognizes four kinds: Industry Agent (Type A), Local Service Agent (Type B), Organization Agent (Type C) and Enterprise Solution Agent (Type D).

An AI Space is an ownable, brandable conversational space — the dedicated AI venue of a merchant, organization, enterprise or website. Each space binds one knowledge set, one persona and one attribution relationship, and can be visited directly or embedded elsewhere.

AionWeb is the technology and infrastructure brand behind the agent runtime, distribution core and white-label capability. In white-label deployments AionWeb and Haiwai appear only as a lightweight footer attribution; the partner remains the foreground brand.

An Appointment is a meeting or service accepted by the merchant and scheduled at a specific time — the state that follows a confirmed booking. It is the base object for merchant scheduling and show-up conversion metrics.

Ask Expert is the professional question entry inside content: while reading, a user can put a question directly to the relevant domain agent. It turns static content into a dialogue that can be probed, forming the natural bridge from content to service.

Attribution determines and records who brought a lead or conversion and who shares in the revenue. The platform separates two layers: lead attribution may credit multiple contributing sources, while ownership attribution is single-owner and immutable once written by onboarding. Every event must carry its surface and partner identifiers; events without attribution never enter settlement.

A Booking is a service appointment request initiated and confirmed by the user in conversation or on page — a high-value rung on the lead ladder. It is written only after explicit confirmation; a cancellation writes nothing.

The Brain is an agent's reasoning core: it interprets the question, selects knowledge, forms the judgment and decides the answer structure. The platform follows a single-brain principle — within one product domain all intelligence lives in one place, never scattered across UI components.

A Canonical Route is the single public address of a runtime surface — one surface, exactly one canonical route. All new documentation, marketing and handbooks must use it; every other historical address exists only as an alias. Examples: Website Partner `/website/*`, MNP `/mnp/*`, DNP `/dnp/*`.

Case Analysis is the structured judgment an agent makes about a user's specific situation rather than a generic explainer. It typically contains a conclusion, its basis, the risks and the next actions — the dividing line between professional dialogue and encyclopedic answers.

Commerce Attribution covers click and conversion tracking in commerce and affiliate contexts: tracked links, source identifiers and conversion postbacks. It is strictly isolated from service-lead attribution — the two never share records or settlement channels.

A Compatibility Alias is retained so existing integrations, internal identifiers and external links keep working. It may persist indefinitely in internal fields and technical identifiers, while user interfaces and public documentation always present the canonical name.

Consumer is the end-user identity that uses the platform's AI services — the origin of every conversation, lead and conversion. Consumers always experience the service under a partner brand or the Haiwai brand, never the underlying infrastructure.

Context is everything one answer depends on: the current question, conversation history, user memory, page context, city, locale, site identity and merchant identity. It is passed as one typed envelope into routing and runtime so every entry point behaves consistently.

Conversation Commerce is the completion of decision and transaction inside the dialogue itself — contact capture, booking, ordering or a tracked handoff to purchase. It collapses "getting information" and "completing the transaction" into one conversation and forms the commercial loop of DCCA.

Conversational Ads is the general term for ad units whose interaction model is dialogue; DCCA is its canonical implementation on this platform. The first screen is a question and an answer, not a slogan and an image.

A Conversion Code is the credential submitted by merchant or user at the point of sale to confirm that a lead actually converted, serving as the billing basis for the success fee. It turns a verbal close into a verifiable, reconcilable event.

CPL (Cost Per Lead) charges merchants for each confirmed, qualified lead. On this platform CPL fires only after explicit user confirmation and always writes through the single canonical lead path; any billing that bypasses it is not recognized.

A Creator is an individual identity contributing content, experience and knowledge material. Accepted contributions carry attribution and revenue share. Creator is a business identity, not a separate account system — one user may simultaneously be a consumer, a creator and a merchant owner.

DCCA is the platform's core advertising format: instead of serving static creative, it dynamically selects and presents a conversational agent based on page context, user intent and city. The unit of delivery is a qualified conversation, not an impression, and value is measured in leads and conversions. Every placement is explainable and traceable to context match, geography, fair rotation and quality.

A Distribution Network Partner (DNP) develops and manages a portfolio of distribution surfaces (website partners). DNP earnings are computed as source share × network override rate, with a 10% default override. DNP is one of the four canonical partner types; `PNP` is a legacy compatibility alias.

DSIA is dynamic placement driven by the service intent a user reveals in conversation: a service exit appears only when a genuine need is expressed. DSIA complements DCCA — DCCA is context-driven, DSIA is intent-driven.

An Embedded AI Space is an AI space embedded as a full page or a full content block rather than a small floating widget. It suits partners who want to offer a complete AI experience, such as a dedicated channel page or a members' area.

Enterprise Brain is the reasoning core of an Enterprise Solution Agent, treating the enterprise's own facts and knowledge as the highest-priority basis. It is deliberately bounded: questions outside the enterprise's knowledge are answered with an explicit boundary statement rather than filled in with generic model knowledge.

Enterprise Knowledge is the official, continuously maintained knowledge asset supplied by the enterprise: policies, procedures, products, services, fees, contacts and FAQs. It is owned and curated by the enterprise in its workspace — reviewable, revisable, versioned — and is the sole authoritative source for the Enterprise Brain.

An Enterprise Solution Agent is a dedicated AI agent deployed for one enterprise, institution, organization, solution provider or corporate website. It is a deployment and runtime model, not an industry category — any sector may adopt it. It is single-tenant with dedicated knowledge, persona and domain, and can be fully white-labeled.

Enterprise Workspace is where enterprise and institutional customers manage their dedicated agent: knowledge curation, capability configuration, conversation review and performance analytics. It targets single-tenant deployments and emphasizes knowledge governance and brand consistency over lead marketplaces.

Experience is first-hand content from real people: real cases, lived accounts, community discussion and practitioner testimony. It sits in a different layer from public knowledge — public knowledge is learnable by any model, while lived experience can only be accumulated by a community and is the platform's irreplaceable asset.

A Fact Pack holds deterministic facts — limits, rates, deadlines, thresholds, form numbers — where ambiguity is unacceptable. Fact questions take a deterministic path: the same question must always yield the same answer, and when jurisdiction or source data is missing the agent refuses explicitly instead of guessing.

Haiwai is the consumer-facing AI platform brand serving overseas Chinese communities. It unifies everyday questions, local services, merchant consultation and lifestyle guides in one conversational experience. For consumers it is an entry point that answers, judges and routes to real local services; for merchants and website partners it is the commercial layer that carries agents, leads and revenue share.

Haiwai Agent OS is the unified agent operating system that defines agent identity, knowledge, runtime, distribution, attribution and settlement contracts. It is the shared core across Haiwai, Sinomedia and AionWeb. New surfaces and industries register into the OS rather than forking parallel systems.

Haiwai Life Guide is the productized guide system for overseas living scenarios — relocation, parenting, healthcare, taxes, housing. It organizes structured knowledge into searchable, conversational content and can be embedded on partner sites.

The Haiwai Life Guide Widget embeds structured living guides into partner sites in searchable, conversational form. It delivers content value first and service routing second: users get practical information, then reach a service entry only when a need appears.

A Handbook is the systematic reference for a given role: what the role is, what it can do, how to start and how success is measured. Handbooks answer what and why, pair with playbooks that answer how, and must stay synchronized with their governing SSOT.

Identity is the platform's unified identity model: one user has exactly one account and one profile, and may hold multiple business identities on top of it (consumer, creator, merchant owner, partner admin). The binding rule is one profile and one wallet per user — adding a business identity never forks the account or the wallet.

Knowledge is the factual and procedural material an agent relies on: definitions, rules, procedures, thresholds and timelines. The platform separates public knowledge from real lived experience — the latter is its distinctive asset. Knowledge enters an approved skill pack only through human review; automatic promotion is not permitted.

A Knowledge Item is the standard storage unit of the knowledge layer: one curated fact, definition or procedure carrying its source, creator and timestamps. It is an intermediate product of the content pipeline — derived from raw material, and only eligible for an approved skill pack after review.

A Knowledge Pack bundles knowledge around one subject — a merchant pack, an industry pack, an organization pack. Packs are deliverable, versioned assets submitted at onboarding and maintained in the workspace.

A Lead is a deliverable record of genuine service intent, containing the need, city, industry and contact details. Leads must originate from an explicit user confirmation — never auto-filled or auto-submitted — and every lead is written to the unified lead record with its source and trigger stamped.

The Lead Ladder is the tiering of leads by quality and commitment — from light interest, to shared contact details, to a confirmed appointment and finally a completed transaction. The ladder drives pricing and settlement: higher rungs are closer to revenue and worth more.

The Lead Ledger is the unified ledger of leads, recording generation, ownership, billing state and settlement outcome for reconciliation between merchant, partner and platform. It is the authoritative record — any lead delivery that bypasses it is invalid.

A Lead Magnet exchanges a high-value asset — an assessment, checklist, calculation or guide — for the user's contact details. On this platform it typically runs as assessment → draft report → email gate for the full report, producing a lead directly.

A Legacy Alias is a historical name or address that still works but is no longer the official term and must not appear in new public-facing content. Typical examples: `Publisher` (within Haiwai), `CNP`, `PNP` and the routes `/publisher/*`, `/cnp/*`, `/pnp/*`.

A Life Guide Card is the smallest presentation unit of the Living Guide: one card carries actionable information on one clear topic. Cards are built to be skimmed and acted on — key points, steps, cautions, next action.

Life OS is the lifestyle runtime layer behind MyGPT, responsible for domain routing, domain-advisor answers, companion persona and local context. It never carries merchant lead flows — booking, contact capture and attribution writes belong to the service runtime.

Living Guide is the platform's structured lifestyle content system, organizing practical overseas-living information into continuously maintained entries. Simplified Chinese is the editorial master; Traditional Chinese is generated automatically; English is produced on request. Search is script-agnostic. The guide serves both human readers and agents as a knowledge source.

Master Workspace is the upper-level workspace used by network partners (MNP, DNP) to manage their members: member overview, sub-account administration, aggregated performance and network-level revenue views. It does not replace each member's own workspace.

Memory is user-related information retained across turns or sessions — city, household situation, prior concerns, confirmed preferences. It reduces repeated questioning and improves continuity; anything the user states explicitly outranks anything the system infers.

Merchant is one of the two canonical business entities: a business that provides services or products. It is the single name used across architecture, domain model, runtime, database, APIs, analytics and event contracts. Presentation terms (Merchant Partner in Haiwai, Advertiser in Sinomedia) all normalize to Merchant.

The Merchant Chat Widget is bound to a single merchant and can be placed on the merchant's own site, a landing page or a partner page. Powered by the merchant runtime, it supports professional Q&A, booking and contact capture — the merchant's most direct acquisition entry.

A Merchant Network is the set of merchants organized by an MNP together with its governance: admission, activation, quality, lead distribution and settlement. It is the supply-side organizational unit that determines whether a city or industry can reliably deliver service.

Merchant Partner is the canonical Haiwai presentation term for a Merchant: a contracted business that owns an agent and receives leads. Merchant Partners hold a workspace, knowledge assets and a settlement relationship, and are one of the four canonical partner types.

Merchant Runtime powers merchant and industry agent conversations, handling professional answers, boundary control and lead conversion. It is the only runtime permitted to create leads and booking writes; lifestyle and content runtimes never do.

Merchant Workspace is the merchant partner's back office: agent status, leads and customers, content and knowledge, analytics, settlement and settings. Its home page answers only four questions — are you live, how do you share, how many customers, what is next.

A Merchant Network Partner (MNP) develops and serves a portfolio of merchants, organizing them into one manageable, settleable network. MNPs operate through a master workspace with network-level analytics and revenue relationships, earning from leads and conversions generated by their merchants. MNP is one of the four canonical partner types; `CNP` is a legacy compatibility alias only.

MyGPT is the consumer-facing general life AI entry point. It interprets the question, delivers a verdict first, and hands off to the right industry or local-service agent when needed. It reasons from human-prior defaults when context is incomplete, and resolves every local reference to the header's current city.

The MyGPT Widget embeds the general-purpose life AI into partner sites, covering cross-industry everyday questions. It inherits the site's default city and locale, and hands off to the appropriate professional agent once the user expresses a concrete service need.

MyLife is the product surface for personal life records and accumulated experience — itineraries, checklists, notes and life moments. Its content can feed the platform's Experience Layer as real lived experience rather than public knowledge.

MyLife Experience is the lived-experience content a user accumulates in MyLife and chooses to share publicly. Shared entries can enter the content pipeline as retrievable, citable experience material, always retaining the original author's attribution.

Open Network is the option for enterprises and organizations that already run a dedicated agent to also join the platform's public consumer network for additional reach and leads. Participation is optional: an enterprise may stay purely single-tenant, or join public distribution while keeping its brand independent.

Partner Settlement is the settlement flow and reconciliation view for partners (merchants, websites, MNPs, DNPs), presented partner-first: period revenue, itemized sources, deductions and withdrawable balance.

Partner Wallet is the unified financial view under a partner identity — earnings, charges, balance and payouts. It is a presentation of the single wallet, not a separate account system.

A Playbook is a task-level execution document: step-by-step instructions for getting one thing done, with prerequisites, sequence, acceptance criteria and common pitfalls. Playbooks answer how, and must never contradict their governing SSOT.

RAG (Retrieval-Augmented Generation) retrieves relevant knowledge before generating an answer and grounds the answer in what was retrieved. Platform retrieval is script-agnostic across Simplified and Traditional Chinese. RAG only solves finding the basis — whether an answer may be given still depends on fact and skill-pack rules.

Reasoning is the judgment process an agent completes before answering: classifying the question, drawing on facts and experience, weighing risk and reaching a conclusion. The platform's rule is verdict-first — even with incomplete context, give a usable judgment from sensible defaults, then ask at most one key follow-up.

Revenue Attribution allocates a payment across beneficiaries under a fixed precedence: contract override → partner policy → platform default. Network partners are paid as source share × override rate, which never alters the source party's own share base.

Revenue Share is the agreed split of income between the platform and its partners. Rates follow one precedence — contract override, then partner policy, then platform default — and every allocation is traceable to the specific rule that produced it.

Runtime is the execution environment where an agent actually runs: receiving the request, assembling context, invoking the brain and tools, producing the reply and recording events. Runtimes are isolated per product domain, and each domain permits exactly one canonical runtime.

SC (Success Fee) is charged when a lead ultimately converts, forming a two-stage revenue model together with CPL. Conversion requires a verifiable confirmation signal such as merchant confirmation or a conversion postback; unconfirmed conversions are not billed.

Settlement turns confirmed revenue and shares into ledger entries: a reconciliation period, generated statements, wallet credits and payout eligibility. It accepts only attributed, ledgered events and is idempotent — duplicates never double-charge.

Sinomedia is the advertising and media distribution brand serving Chinese-language publications and advertisers. It upgrades display advertising into conversational advertising and agent distribution. In Sinomedia, `Publisher` (supply) and `Advertiser` (demand) are approved presentation terms that normalize to the canonical `Website` and `Merchant` entities.

A Skill is a professional action or answering capability an agent can perform — eligibility assessment, document checklists, timeline planning, risk flagging. Skills are composable and reusable: industries share generic skills while keeping their own specialized ones.

A Skill Pack is the approved, agent-callable combination of skills and knowledge — the formal output layer of the knowledge system. Only human-reviewed candidates become skill packs, and high-risk industries (legal, immigration, tax, insurance, medical, financial) always require review.

SSOT (Single Source of Truth) is the one authoritative definition for a given topic. Where descriptions conflict, the SSOT prevails. The platform maintains one SSOT each for identity, attribution, routing, terminology, workspaces and the knowledge hierarchy; new capability extends an existing SSOT rather than forking a parallel document. This glossary is the SSOT for platform terminology.

A Sub Merchant is a merchant that belongs to an MNP's network. It remains a full merchant partner with its own agent and workspace — the relationship describes ownership and settlement, not reduced capability.

Synthetic Q&A are question-answer pairs generated from already-verified facts to broaden coverage of how users may phrase the same question. They may only derive from verified facts and must not introduce new ones — they expand phrasing, never the knowledge boundary.

A Tool is an external function an agent can call during a conversation — retrieval, calculation, form submission, booking writes, report generation. Tool calls must be explicit, traceable and compliant with their write contracts (for example, leads may only be written through the single canonical path).

Wallet is the unified financial view for a user or partner, aggregating earnings, charges, balance and payouts across every identity. The platform follows a one-wallet-per-user rule regardless of how many business identities are held.

Website is one of the two canonical business entities: a distribution surface owned by a partner — a site, publication, channel or embed host. It is the canonical name of the "publisher business object"; attribution, configuration, white-label domains and revenue share all attach to it.

Website Facts are structured facts extracted and verified from an official site: address, phone, email, services, fees, office hours, application procedures. They are the first-hand basis for merchant and organization agents and outrank generic model knowledge.

A Website Network is the set of distribution surfaces organized by a DNP together with its governance: onboarding, widget configuration, content fit, traffic quality and revenue share. It is the demand-side traffic unit that determines reach and geographic coverage.

Website Partner is the canonical Haiwai presentation term for a Website: a partner that provides a distribution surface and earns revenue share from it. Website Partners can enable conversational ad slots, embedded assistants, life-guide widgets and white-label subdomains; every event carries `site_id` and `publisher_id` attribution. `Publisher` and `Publisher Partner` are legacy compatibility aliases in Haiwai; `Publisher` remains approved in Sinomedia.

Website Runtime is the execution environment on the distribution side: it resolves site identity, loads site configuration and branding, determines default locale and city, and stamps attribution identifiers on every event. Unknown hosts fall back to a neutral shell with no partner branding and no partner attribution.

Website Workspace is the website partner's back office: widget and ad-slot configuration, distribution strategy, city and industry scope, traffic and lead performance, revenue share and settlement. It also carries white-label settings such as subdomain, brand name, primary color and default locale.

White Label lets a partner deliver platform capability under its own brand and domain, so end users only ever see the partner. It covers the partner subdomain, brand name, primary color, logo, default city and default locale — all driven by site configuration, never hardcoded. The platform appears only as a single-line footer attribution and never competes with the partner brand.

A Widget is an embeddable conversational entry that brings platform agent capability onto a partner's own pages. It renders either inline (within page content) or floating (anchored in a page corner), and is always labeled "助手 / Assistant" in the UI. Every widget must be registered before it can run; unregistered widgets never render.

Widget Runtime mounts, unmounts and instruments embedded assistants on external pages, turning routing decisions into rendered experiences. It only renders and reports events — it never writes attribution or settlement data directly.

A Workspace is the operating back office for a given role: data, assets, agent configuration, leads and settlement. Each role has exactly one canonical workspace and one canonical route; no role may hold two parallel back offices. Every workspace must be registered in the platform URL inventory before release.

XiaoZhi is the original embeddable conversational assistant used on media sites and partner pages for instant Q&A and service routing. In user-facing UI it is always presented as "助手 / Assistant"; `xiaozhi` persists only as an internal runtime identifier.

The XiaoZhi Widget is the original and most widely deployed assistant widget for media sites, used on article and channel pages for instant Q&A and service routing. It matches an agent to page context and city, and is the main vehicle for conversational advertising in media environments.