Vexal Documentation by WileyLabs

Glossary

Stable

Applies to: Vexal platform and SmartBlocks documentation

Introduced: Docs site v1

Updated: July 2026 — Hub + Experience Framework

This glossary defines the core terms used across Vexal technical documentation and SmartBlocks operational workflows.

Summary

Terms are concise and implementation-oriented to reduce ambiguity in development, QA, and operations.

Use cases

  • Align vocabulary across teams
  • Speed up onboarding and review
  • Interpret campaign and telemetry docs consistently

How it works

Each term provides a v1 definition aligned with current SmartBlocks and WileyLabs release behavior.

Inputs

  • Platform architecture docs
  • Plugin implementation patterns
  • Operational release and governance standards

Outputs

  • Vexal: Modular digital business platform and AI Visibility Platform built on machine-understanding infrastructure. Site: vexalai.com.
  • Module: Self-contained business capability (Intake, Media, Portfolio, Comm Dock, Scheduler, SmartBlocks, …). May be installed as a WordPress plugin package.
  • Application: Orchestration UX that coordinates modules and services (Hub, Workspace, Index).
  • Platform Service: Shared infrastructure (authentication, tenancy, machine credentials, SearchAsist Core, health, updates)—not customer-installable as a module.
  • WordPress plugin package: Deployment packaging for modules/apps on WordPress (Plugins screen, ZIP, activation)—not the product name.
  • Vexal Experience Framework: Cross-product experience contracts (Auth, Workspace, Cards, …)—architecture shared, implementations product-owned.
  • Authentication Experience: Vexal owns login UI; WordPress owns credentials; product owns authorization.
  • Vexal Hub: Application control plane for Operator Console, customer Workspace, membership, and machine auth (also hosts some Platform Services).
  • Hub Workspace: Customer Application shell at /vexal-workspace/ (not Portfolio Project Workspace).
  • selection_required: Fail-closed Hub status when multiple accounts/sites exist; chooser UI planned.
  • Vexal Intake: Lead Module — forms + client account portal; Hub Manifest/Workspace provider.
  • SmartBlocks: AI Visibility Module for site intelligence features (delivered as a WordPress plugin package).
  • WileyLabs: Product/release organization and repository identity owner. Site: wileylabs.ai.
  • Governed Apply: Capability-checked, evidence-backed mutation flow through approved handlers.
  • Visibility Ledger: Event/snapshot audit history for optimization actions.
  • Safe Fix: Low-risk apply action constrained by policy and validation.
  • FAQ Guided Action: Assisted FAQ optimization step reviewed before publish.
  • Page Readiness: Section-based scoring model (SEO/AI/GEO/schema) for machine clarity.
  • Schema-only mode: Applies allowed schema updates without broader content rewrite operations.
  • Customer Context: Server-resolved account/site context after authentication and authorization.
  • Machine Authentication: Per-site tokens for Hub↔remote module pulls (not human login).

Admin UI location

Reference page only; terms map to SmartBlocks admin modules and telemetry/operations screens.

Glossary terms appear in telemetry and campaign reporting contexts.

Terms such as governed apply and safe fix are reflected in ledger event keys and notes.

Security

Definitions do not expose private implementation secrets, credentials, or customer-specific data.

See also