Admatic Stack
Documentation for release 5.14.2
Search, install, operate and repair the coordinated Elementor website-production stack.
Browse
Version note
This site documents stack 5.14.2. The stack is expected to evolve, so update the version badge and changed procedures when publishing a new coordinated bundle.
Stack Architecture
Understand what each package does, where it belongs and how project data travels from the central development site to a protected Elementor build on staging.
How the system is divided
Core is the source of truth. Staging executes only signed high-level operations. The same explicit project ID is used by planning, compilation, materialization, QA, recovery and automation.
Central development site
Runs Admatic Core and the ChatGPT/OAuth connection. Stores canonical project state, contracts, approved component metadata and the central template corpus.
Staging website
Runs Admatic Theme first, followed by Site Installer, Elementor, Elementor Pro, Remote Worker and Kit Factory. Receives and builds a verified project ZIP.
Component responsibilities
Admatic Core 2.14.3
- Native MCP and OAuth server.
- Controlled tools, policies and global approval.
- Canonical project state and contract schemas.
- Central Template Corpus and design intelligence.
- Package compilation, diagnostics and staging delivery.
- Project, media, page-plan, QA, repair and recovery coordination.
Admatic Site Installer 5.13.1
- Installs and repairs the coordinated staging stack.
- Runs preflight and readiness workflows.
- Checks Elementor/Pro versions, Worker pairing, ZIP support, OpenSSL, temporary files, uploads, memory and background jobs.
- Provides modern and legacy administration modes.
Admatic Remote Worker 1.6.2
- Pairs a staging site to central Core.
- Negotiates HTTPS compatibility transport with HMAC fallback.
- Verifies package SHA-256 and the exact stack contract.
- Imports once and starts the protected Kit Factory build.
Admatic Kit Factory 2.13.1
- Creates the project prompt from a stored brief.
- Validates and imports deterministic project ZIPs.
- Materializes pages, Theme Builder templates, menus, local media and Elementor settings.
- Runs screenshot QA, package validation, change previews and recovery snapshots.
Admatic Theme 1.14.2
- Hello Elementor child theme.
- Owns the unified Admatic WordPress admin shell.
- Provides compatibility adapters without taking over third-party application layouts.
- Hosts Theme Control Center, diagnostics and visual settings.
Elementor and Elementor Pro
- Provide native containers, Grid, widgets, responsive controls and Theme Builder.
- Elementor Pro is mandatory for global header/footer templates and Nav Menu.
- HTML widgets, arbitrary raw JSON and direct-positioning shortcuts are excluded from the production standard.
Build contracts
Build Job V1
Defines project identity, brief, required pages, reference authority and expected deliverable.
Site Plan V2
Locks the reference-resolved page plan, section ownership and global parts.
Native Composition V2
Allows bounded native Elementor composition when no approved component structurally matches.
Reference Geometry V2
Stores measured header, hero, section, card, footer and responsive typography geometry.
Visual Correction V2
Defines region-weighted desktop, tablet and mobile comparison with exactly three same-project correction passes.
Project State V3
Keeps summary, plan lock, compiler, materializer and recovery on one normalized project state.
Approved components versus native composition
Approved components are used when structural evidence proves a match, especially for global header, footer, menus, forms and other high-risk structures. When a page section does not match an approved family, the builder uses bounded native Elementor composition instead of forcing a generic block.
Coverage is not a component-count score
A low approved-library count is not automatically bad. The important requirement is proof of ownership: every section must be either an approved component with evidence or a valid bounded-native composition.