Vexal Architecture

Stable

Applies to: Vexal platform, SmartBlocks, Hub integrations

Introduced: Documented in SmartBlocks AI-VISIBILITY-CONTRACT (1.0.700+)

Updated: Documentation v1

Vexal is a portable intelligence layer—not a theme framework. Architecture separates measurement, discovery, governed execution, and audit.

Summary

Four cooperating layers: signals (content, meta, crawlers), intelligence (scoring, recommendations, agents), governance (registry, apply guards, campaigns), and audit (ledger, snapshots, recovery).

Use cases

Design new features that plug into existing recommendation and ledger pipelines
Understand why SmartBlocks avoids theme template takeover
Plan Hub or SearchAsist integrations without duplicating intelligence engines

How it works

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

SmartBlocks implements most v1 surfaces in WordPress. Vexal Hub and SearchAsist extend AI routing and engine calls where configured.

Inputs

Post content (including builder/Elementor extraction where supported)
Post meta: FAQ, schema flags, GEO mentions, suggestions
Telemetry payloads and external API responses

Outputs

Updated meta, schema JSON-LD, FAQ rows (when grounded)
REST/AJAX responses for admin UI
Ledger rows and change snapshots

Admin UI location

Vexal → Vexal AI Visibility section hubs; sub-pages include Visibility Campaigns, Telemetry, Visibility Ledger, Recovery & Rollback.

Agent families, crawl health, GSC bridges—Telemetry Engine.

Campaign milestones, recommendation apply, snapshot creation—Visibility Ledger.

Security notes

All admin mutations require manage_options or post-level edit caps plus nonces. AI-generated JSON-LD is assembled in PHP from templates—never emitted raw from models.