ADMATIC ELEMENTOR PRO PRODUCTION STANDARD - MANDATORY FOR ALL NEW PROJECTS
==================================================

The authoritative machine-readable contract is project-standards/admatic-elementor-pro-production.json.

Approved components remain library v1.0.0 and retain all existing IDs. The additive variant contract requires defaultVariant plus tested variants with explicit expression/scope support and desktop/tablet/mobile responsive metadata. Every instantiated root must carry admatic_component_id, admatic_component_version and admatic_component_variant.

Every newly generated project must:

1. Identify the standard
- project_standard.id: admatic-elementor-pro-production
- project_standard.revision: 2026-07-16-modern-v5-1
- strict_validation: true

2. Declare hard dependencies
- Elementor Core is required with plugin_file elementor/elementor.php and minimum_version 3.0.0.
- Elementor Pro is required with plugin_file elementor-pro/elementor-pro.php and minimum_version 3.0.0.
- Elementor Pro must not be older than Elementor Core major/minor.
- Required Pro features are theme-builder and nav-menu.

3. Preserve global templates
- Create one populated header and one populated footer Elementor Library template.
- Use type/location header/header and footer/footer.
- Publish both templates.
- Register their elementor_library_type taxonomy terms.
- Assign conditions exactly ["include/general"] and display_conditions exactly ["entire_site"].
- Build them from approved global-header and global-footer library components.
- Store component: global-header/global-footer and component_version: 1.0.0 on the corresponding template records.
- Mirror each template component ID/version into the first root Elementor container settings as admatic_component_id and admatic_component_version. The canonical template metadata and root marker must agree.
- Include Elementor Pro Nav Menu widgets connected to primary and footer menus.
- Preserve admatic-global-header and admatic-global-footer on their root containers.
- Include approved_component_library with schema/library versions, the same project standard marker and global-header/global-footer component entries.
- The compact header root must set flex_direction_mobile: "row", flex_wrap_mobile: "nowrap", justify_content_mobile: "space-between" and align_items_mobile: "center". A real client logo uses Image/Site Logo; when none exists, use a native Heading wordmark and never a placeholder image. Nav Menu Full Width must be Yes, and the CTA must use Elementor responsive hide_mobile. Tablet may retain its CTA only while the header remains a single row.
- The header root must leave Advanced > Position at Default, enable Sticky Header Effects through native settings, and vertically center balanced desktop logo/navigation/CTA zones.
- Put admatic-header-brand directly on the Image, Site Logo or Heading wordmark widget and admatic-header-menu directly on the Nav Menu widget, with auto mobile width. Put admatic-header-cta directly on every desktop header Button widget with hide_mobile: "yes". Never assign these role markers to wrapper containers.
- Mobile Screenshot QA flags a stacked logo/menu toggle, a wrapped header or a visible desktop CTA as actionable repair evidence when comparison is available. An opened dropdown may flow beneath the one-row header.

4. Use the correct page layout
- page_layout_default must be elementor_header_footer.
- Every page template must be elementor_header_footer.
- elementor_canvas and canvas are forbidden.

5. Require protected building and QA
- build_policy.clean_previous_build: true
- build_policy.require_change_preview: true
- build_policy.require_recovery_snapshot: true
- Render desktop, tablet and mobile screenshots for every page automatically and compare mapped references when available.
- Set expected_captures to exactly the number of pages multiplied by three and max_pages to at least the page count.
- Ready validation must prove template status/type/taxonomy, exact Entire Site conditions, menu assignment, non-Canvas layouts and both global markers on every frontend URL.

Media provenance under this standard:
- Client-owned files use generation_method: client_asset, a local package path, client/business provider, ownership credit and source_url beginning client-provided:// unless a real HTTPS source exists.
- External stock/photography uses a real HTTPS source/credit URL.
- Never create a fake HTTPS URL for a private client asset.

6. Remain honest about legacy compatibility
- A package without project_standard is legacy-compatible, not production-standard.
- Do not silently label a legacy package compliant.
- A repair may migrate a legacy package only when the output includes every requirement above.

Reject and rebuild any new package that violates this standard.

CANONICAL ARCHITECTURE AND ADAPTER ADDENDUM
The production standard uses the normalized Cavanio architecture as its default structural baseline and the licensed multi-industry corpus only for range validation. All packages must expose the complete 17-contract adapter registry with exact named capability sets; optional booking, commerce and multilingual behavior remains dormant until the project calls for it.


MODERN GOLDEN STANDARD V4 — CREATIVE EXPRESSION CONTRACT
- Visible reference evidence is authoritative. Reconstruct its section sequence, geometry, media rhythm, visual density, hierarchy, surface changes and conversion flow before selecting components.
- Do not default to repeated bare heading/text card grids. A standard homepage should normally contain 10–14 distinct visual regions; inner pages should normally contain 6–10.
- Approved components are optional candidates, not mandatory output. Use them only at measured structural match >= 0.96. Otherwise use expressive admatic.native-composition.v2 structures.
- Creative freedom is open inside native Elementor controls. Use Grid, nested containers, images, galleries, counters, icons, icon lists, testimonials, forms, accordions, tabs, carousels, dividers, backgrounds, overlays, borders, radii, soft shadows, typography and responsive controls.
- Hard restrictions only: direct Position remains Default; no custom CSS; no HTML widgets; no flex wrap; no arbitrary tracking/design classes. Multi-column layouts use native Elementor Grid with explicit desktop/tablet/mobile columns.
- Modern surface language: subtle 1px borders, 12–32px radii, soft low-opacity shadows, alternating dark/light or accent/quiet regions, deliberate image crops and clear content max-widths. Avoid every section looking like the same flat dark rectangle.
- Mobile must satisfy document.scrollWidth <= document.documentElement.clientWidth + 1 at 390px. Clear fixed/oversized widths, negative margins and multi-column mobile grids; mobile grids collapse to one column.
- Use at least four media-led regions on a standard homepage when enough media is available. Prefer editorial split layouts, image mosaics, location cards, quote/proof panels and richer CTA/footer transitions.

V5 CORPUS-DRIVEN STANDARD
Keep the curated component catalogue compact and deeply validated for global/high-risk structures. Generate most page regions through bounded native Elementor composition using the licensed corpus grammar and runtime-discovered first-party Elementor/Pro controls. The component count is not a quality target. Reference fidelity, composition depth, responsive behavior, content density and rendered visual QA are the quality targets.

TEMPLATE INVENTORY AND SCREENSHOT-AUTHORITY POLICY
- Keep curated components for headers, footers, menus, forms, navigation and other high-risk global structures. Component count is never a quality target.
- Treat every approved template inventory entry as searchable geometry, responsive, widget and surface-treatment knowledge—not as a rigid layout to clone. The inventory is designed for 50–100+ curated full-site templates and hundreds of classified section patterns.
- The supplied screenshot reference is always the primary authority. Analyse it before retrieval, measure its geometry, and never let an industry label or nearest template override visible evidence.
- Retrieve multiple candidates: up to five whole-page shells and up to eight candidates per region. Use a whole template only when measured whole-page geometry and section topology strongly match; otherwise synthesize regions from multiple corpus patterns.
- Use native Elementor composition for most screenshot-specific page regions. Allow all installed first-party Elementor and Elementor Pro widgets except HTML and other explicitly prohibited controls.
- Score corpus candidates by geometry 30%, section topology 20%, responsive behaviour 15%, image composition 10%, typography hierarchy 10%, surface styling 10%, and widget compatibility 5%. Industry similarity is secondary.
- Reconstruct patterns with native Elementor controls. Never copy source branding, text, photography, licence data or third-party addon dependencies.
- Render desktop, tablet and mobile, compare against the supplied reference, and correct the same project up to three evidenced passes. Do not create a duplicate project.
