ADMATIC STACK CONTEXT - DO NOT IGNORE

STAGING CONTRACT: admatic-staging-3

- Compile an admatic.site-plan.v2 provisional envelope, analyse all references, then let Core lock the final resolved plan before Elementor materialization.
- Select one scope profile: simple, standard or extensive.
- Select one expression profile: clean, brand-led or creative.
- Resolve every page through admatic.page-recipes.v1.
- Resolve templateStructureContract from elementor-template-structure-families-v1.json. The supported families are cavanio-service, fitness-performance, wellness-editorial, hospitality-conversion and corpus-balanced.
- Treat each family as a structure-only completion contract. Visible client reference evidence overrides it; source branding, text, imagery, licences and third-party addon dependencies are forbidden.
- Extract reference geometry before locking. Resolve a slot to an approved componentId plus variantId only when measured structural similarity meets the reference threshold; otherwise use the budgeted admatic.native-composition.v2 contract.
- Treat the plan fingerprint, page recipes, section order and component variants as locked during content, package and repair stages.
- Before Core resolution, display and preserve the planningDigest/provisionalFingerprint and approved candidate coverage. Never report zero candidate coverage when every planned slot has an approved-library candidate.
- Separate planning, content, package and repair instructions. A later stage may fill declared variables but may not silently redesign an earlier stage.

This prompt must be generated for the current Admatic Website Builder Stack:

- Admatic Theme: v1.14.0+
- Central Admatic Core: v2.8.0+ on dev-admatic.dk only; never local on staging
- Admatic Site Installer: v5.8.0+
- Admatic Kit Factory: v2.8.0+ on staging
- Admatic Remote Worker: v1.5.0+ on staging and paired to central Core
- Elementor Core: active and compatible
- Elementor Pro: active, mandatory and not older than Elementor Core major/minor
- Project standard: admatic-elementor-pro-production, revision 2026-07-16-modern-v5-1
- Screenshot QA Service: automatic desktop/tablet/mobile capture and reference-comparison evidence when the endpoint supports comparison
- Admatic Intelligence Service: Python Phase 4 advisory repair recommendations
- Screenshot QA endpoint: use Admatic central defaults supplied by Site Installer / Kit Factory
- Main output format: Admatic Kit Factory project package ZIP
- Native Elementor Website Kit export is not the default workflow

Core and the ChatGPT/OAuth connection exist only on dev-admatic.dk. Staging contains Site Installer, Remote Worker, Kit Factory, Admatic Theme and Elementor/Pro. Do not install or require Core on staging.

Every newly generated package must implement Modern Golden Standard V5.1. It must include measured referenceGeometry, Header/Footer V2, Native Composition V2, canonical responsive QA metadata and a region-weighted visualCorrectionContract. Kit Factory captures all three viewports, uses its structural benchmark when external comparison is unavailable, maps failed regions to Elementor controls and rerenders the same project up to three times.

Legacy packages without the project_standard marker remain import-compatible, but new output must never omit the marker or downgrade to legacy/fallback navigation. Do not require manual Screenshot QA endpoint/secret setup in generated project packages. Build once initially, poll the public Core workflow, and use no more than three evidenced visual correction builds on the same project. Release the existing ZIP when data.releaseGate.releaseReady is true; never call staging REST directly or create a duplicate project.

CANONICAL ARCHITECTURE CONTRACT
- Start from admatic-licensed-inspiration-corpus-v2, revision 2026-07-16-modern-v5-1. Use its page hierarchy, section sequencing, container geometry and responsive topology only; never copy its branding, text, images or addon-widget dependency.
- The licensed multi-industry template corpus is a range guardrail, not an averaging engine. A direct client reference may refine the canonical geometry after measured analysis.
- Every new package carries adapter-manifest V3 with 14 baseline and 3 feature-triggered capability adapters.

MODERN V5 COMPOSITION POLICY
- The visible client reference is the primary authority. The licensed template corpus is inspiration metadata and a geometry/widget grammar, never a source of branding, copy, photography or redistributable templates.
- Curated components are accelerators for headers, footers, menus, forms, navigation and other structurally sensitive regions. Most reference-specific page regions should use bounded native Elementor composition.
- Do not enforce a universal padding table or fixed section-count target. Derive rhythm from the measured reference, content density and adjacent-region relationships, then verify rendered whitespace and mobile overflow.
- All installed first-party Elementor and Elementor Pro widgets may be used through runtime control-schema validation except HTML. Custom CSS, custom JavaScript, direct positioning and flex wrapping remain forbidden.

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.
