Vexal Architecture

Stable

Applies to: Full Vexal platform

Updated: July 2026 — Hub Workspace + Experience Framework

Vexal is a modular digital business platform. Architecture separates Platform Services, Modules, and Applications. WordPress plugin packages are a Deployment choice today—not the definition of the Platform.

Summary

Canonical vocabulary (must stay aligned with public docs):

Platform
  ├── Platform Services
  ├── Modules
  ├── Applications
  └── Deployment targets (WordPress plugin packages today; others later)

Share Contracts across products; do not share credential systems or copy product classes. See also Platform Services, Applications, Modules, and Deployment.

Platform map

Category	Examples	Role
Applications	Hub, Workspace, Index	Orchestration UX
Modules	Intake, SmartBlocks, Media, Portfolio, Comm Dock, Scheduler	Business capabilities
Platform Services	Auth, Tenancy, Machine Credentials, SearchAsist Core, Health, Updates	Shared infrastructure

Product references

Name	Category	Role
Vexal Hub	Application (+ hosts services)	Operator Console, Workspace, membership, machine auth
SmartBlocks	Module	Site AI visibility intelligence
Vexal Intake	Module	Leads + Hub Manifest/Workspace provider
Vexal Media	Module	Media optimization
Vexal Portfolio	Module	Projects and galleries
SearchAsist Core	Platform Service	Authenticated AI routing APIs

Experience Framework

Cross-product UX/security contracts are documented in the Vexal Experience Framework. Governing rule: Vexal owns experience UI; WordPress owns authentication security; each product owns authorization and context.

Authentication → Authorization → Context

User
  ↓
WordPress Authentication
  ↓
Authorization (product rules)
  ↓
Workspace Context (account + site)
  ↓
Workspace Shell
  ↓
Cards

Detail: Authentication layers.

Hub authorization chain

User → Tenant/Account → Site → Permission → Workspace

See Membership and Hub Workspace.

SmartBlocks intelligence layers

On each WordPress site, SmartBlocks still follows:

Content + meta → Page Readiness / Telemetry signals
  → Recommendation registry (keys + evidence)
  → Governed apply (confirm, merge, schema-only fallbacks)
  → Visibility Ledger + Recovery snapshots
  → Dashboards & compare reports

This site-intelligence stack is complementary to Hub’s tenancy stack—not a replacement for it.

Ecosystem bridges

Portfolio ↔ Media ↔ SmartBlocks (ledger / readiness)
Hub ↔ Intake (machine auth + module/workspace contracts)
SmartBlocks / Media ↔ SearchAsist Engine (AI routing)

See Ecosystem Bridges.

Security notes

Admin mutations: capabilities + nonces
No parallel password stores or custom session cookies for product login
Fail closed on ambiguous Hub context (selection_required)
Public docs must not contain secrets or customer PII