==================================================
REFERENCE-TO-SITE MAPPING - MANDATORY
==================================================

PROFILE AND RECIPE BOUNDARY

The design reference controls measured structure, global tokens, photography treatment and responsive behavior. Extract header, hero, section, card and footer geometry before locking the plan and store it as admatic.reference-geometry.v2. It does not invent pages or authorize raw Elementor JSON. When no approved candidate reaches the structural threshold, it authorizes only a budgeted admatic.native-composition.v2 composition.

- Simple controls information volume and navigation depth; it is not shorthand for visually plain.
- Standard is the default complete small-business architecture.
- Extensive adds content depth, archives and detail templates; it is not permission to repeat sections.
- Clean, brand-led and creative select among tested responsive variants. Creative remains bounded by the same mobile, accessibility and overflow gates.
- When a reference feature cannot be represented by an approved variant, record the measured mismatch and compile it with the bounded native Elementor composition contract.

Before building, create a clear reference-to-site mapping.

Map the uploaded design reference to the new project structure:
- Reference hero -> project hero
- Reference header -> project header
- Reference stat/trust cards -> project trust/stat section
- Reference image/card section -> project intro/benefit section
- Reference services grid -> project services section
- Reference reviews/testimonials -> project reviews/testimonials section
- Reference pricing/package section -> project prices/packages section
- Reference CTA section -> project booking/contact CTA
- Reference footer -> project footer

The final layout must preserve the same overall section rhythm unless the client content
requires a clear adjustment.

Do not skip sections from the reference unless they are irrelevant to the client.
Do not rearrange the page into a generic website layout if the reference has a strong visual
structure.
Do not flatten complex reference layouts into simple vertical blocks.

The built website must feel intentionally adapted from the visual reference, not simply
inspired by it.




TEMPLATE STRUCTURE FAMILY CONTRACT - MANDATORY

- Read templateStructureContract.selectedFamily before laying out pages.
- Use the selected family's homepageSlotOrder, regionTargets, header pattern, footer pattern, nested depth and responsive topology only for information not visible in the supplied reference.
- Cavanio/service is the primary local-service baseline; Gymplus + Vigron supply fitness/performance structure; Nivaya supplies wellness/editorial structure; Ristera supplies hospitality/conversion structure; corpus-balanced uses the median five-kit range.
- Visible reference geometry and explicit Site Design Blueprint rules override the family.
- Never copy source branding, source copy, source photography, licences, product data or third-party addon dependencies. Normalize any observed addon widget to approved native Elementor/Elementor Pro structures.
- Do not collapse a family into hero + three cards + CTA. Meet its region targets unless reference evidence justifies a documented deviation.
- Record selected family, selection mode and evidence in design_blueprint.templateStructureContract and project.json.templateStructureContract.

==================================================
SITE DESIGN BLUEPRINT / LIMITED-REFERENCE PROTOCOL - MANDATORY
==================================================

A screenshot is evidence of a design system, not complete proof of every page and breakpoint.
When only one image, one viewport or a partial page is supplied, do not guess freely and do not
pretend that unseen areas are a 1:1 match.

Use this evidence hierarchy:
1. Explicit Site Design Blueprint rules from the Project Brief
2. Elements directly visible in the uploaded reference
3. Repeated patterns that can be safely extrapolated from the same reference
4. Conservative Admatic fallback rules for anything not shown

Reference-control meanings:
- Strict match: preserve visible composition, proportions, section rhythm and component treatment as closely as the client content allows
- Balanced adaptation: preserve the design fingerprint while adapting content length, conversion flow and business requirements
- Brand-first adaptation: use the reference as structural inspiration, while the client brand rules control color, typography and content emphasis
- Conservative inference: complete unseen areas with simple, consistent patterns already evidenced in the reference
- Balanced inference: allow normal conversion sections while retaining the same visual language
- Creative completion: allow broader completion only where the blueprint explicitly permits it

For every major page section, assign one traceability status:
- OBSERVED: directly visible in the reference
- ADAPTED: based on a visible reference pattern but changed for the project content or goal
- INFERRED: not visible and completed from the blueprint/fallback system

Store the project-specific rules in project.json under design_blueprint.
Store section-level decisions in project.json under design_traceability and repeat a readable summary in README-HANDOFF.txt.
Each design_traceability item should contain section, status, source and notes.

Safe extrapolation rules when the reference is incomplete:
- derive one container-width system from visible outer margins; do not use random widths section by section
- derive one spacing scale from visible gaps and repeat it consistently
- derive one radius, border and shadow family from visible cards/buttons/images
- continue the same heading hierarchy and text-measure direction
- continue alternating background logic only when it is visible or explicitly requested
- use explicit desktop/tablet/mobile grids instead of relying on flex-wrap
- 6 repeated items should normally use a 3-column x 2-row desktop grid, 2 columns on tablet and 1 column on mobile
- avoid inventing sliders, marquees, overlapping elements, floating cards or decorative shapes unless evidenced or requested
- unseen internal pages should reuse the same header, footer, tokens and component family, but may use simpler content layouts
- mobile layouts should preserve hierarchy and CTA priority rather than attempting a literal desktop shrink

The final reference-match score must distinguish visible-reference accuracy from inferred completeness.
A high score may not be claimed merely because colors are similar.


==================================================
ACCESSIBLE RULESET GENERATION - MANDATORY
==================================================

Most users will not know how to specify grids, radii, typography scales or responsive rules.
Do not require them to fill the advanced fields.

When design_setup_mode is automatic:
- inspect the screenshot before planning the page
- extract a reference fingerprint for header, hero, section order, spacing, cards, typography, colors, imagery, CTA treatment and mobile hierarchy
- convert that fingerprint into a complete design_blueprint
- use conservative defaults only where the screenshot provides no evidence
- make all inferred decisions explicit in design_traceability

When design_setup_mode is guided:
- follow the screenshot first
- use design_preset, visual_personality, spacing_density and corner_style only to complete unseen areas

When design_setup_mode is advanced:
- treat populated advanced rules as explicit overrides
- still analyse the screenshot for any rule that was not manually supplied

The quick design profile must be stored in design_blueprint using:
- design_setup_mode
- design_preset
- visual_personality
- spacing_density
- corner_style
- media_source_policy

A complete project must never depend on the user understanding professional web-design terminology.

==================================================
DESIGN CONTRACT / QUALITY GATE - MANDATORY
==================================================

Before creating the final ZIP, create and internally follow a Design Contract for the project.

The Design Contract must include:

1. Reference fingerprint
- Header structure
- Hero layout
- Section order
- Card style
- Spacing rhythm
- Typography direction
- Image treatment
- Button style
- Footer structure
- Mobile behavior

2. Project adaptation map
Map every major reference section to the new website:
- reference section name
- new section name
- purpose
- Elementor structure
- desktop layout
- tablet layout
- mobile layout

3. Design token map
Define:
- primary, secondary, accent, text, muted, background, card, border, button and hover colors
- heading/body/button fonts
- H1/H2/H3/body/button sizes
- section padding desktop/tablet/mobile
- container width
- grid gaps
- card radius
- image radius
- button radius
- shadows

4. Contrast matrix
For every major section, confirm:
- background color/image
- heading color
- body text color
- button color
- contrast status
Do not proceed if normal text is below WCAG AA contrast.

5. Component rules
Build reusable visual patterns consistently:
- header
- hero
- service card
- benefit card
- testimonial card
- CTA block
- contact form
- footer

Cards, stats, benefits, reviews, prices and repeated info boxes must be real Elementor containers/widgets where possible. Do not use HTML widgets for core structural cards unless there is a clear fallback reason.

6. Grid enforcement
Repeated cards must use explicit grid behavior:
- 3 cards = 3 columns desktop
- 4 cards = 2x2 or 4 columns desktop
- 6 cards = 3 columns x 2 rows desktop
- tablet usually 2 columns
- mobile 1 column
No repeated card section may appear as a 1-column desktop stack unless the reference clearly shows a vertical list.

7. Sticky header enforcement
If Sticky Header Effects for Elementor is expected:
- apply the confirmed real Sticky Header Effects Elementor setting keys
- leave Advanced > Position at Default; direct Fixed or Absolute positioning is forbidden
- vertically center the logo, navigation and CTA and use balanced desktop zones
- do not rely only on CSS classes
- do not rely only on Elementor Pro sticky settings
- README must state whether the actual plugin controls are expected to be ON after build

8. Site identity
project.json must include:
"site_identity": {
  "title": "[business name]",
  "tagline": "[short local/service tagline]",
  "language": "da_DK"
}

9. Package rejection rules
Reject and rebuild the package before delivery if:
- header/footer are unstyled
- frontend depends mainly on external CSS
- repeated card sections stack 1x1 on desktop
- images are missing or reused from reference screenshots
- text contrast is poor
- header or footer navigation uses static HTML instead of the mandatory Elementor Pro Nav Menu widget
- forms are empty
- CSS requires opening Elementor and clicking Update
- site identity is missing
- project.json is not in ZIP root
- any template/page has empty content
- Theme Builder conditions are malformed

10. Advisory design score
Use these targets to guide quality when visual evidence is available:
- Reference match: 85/100 or higher
- Editability: 80/100 or higher
- Conversion readiness: 90/100 or higher
- Technical build readiness: 95/100 or higher

Record lower scores as actionable repair recommendations. Apply at most three corrections to the same Core project; preserve the current package and snapshot evidence throughout the loop.

==================================================

CANONICAL BASELINE ORDER
When the client has not supplied a stronger measured reference, preserve the canonical Cavanio-derived sequence: hero, offer, story, trust metrics, featured offer, gallery, team, proof, insights, FAQ, location/contact and conversion. Simple scope may omit optional regions; standard and extensive retain the richer journey. Convert every source addon pattern to an approved native Elementor/Pro component.

ADMATIC REFERENCE-FIRST RELEASE GATE V4 — MANDATORY
- A reference-led project cannot pass from schema validation, capture success, baseline creation or structural heuristics alone.
- comparison.available=false, comparisons=0, baselineCreated-only, structural-advisory or missing viewport mapping must set releaseReady=false.
- Structural analysis is advisory and may identify corrective controls, but it may never contribute synthetic perfect region scores or satisfy rendered reference comparison.
- Header, hero, sections, typography, imagery and footer each have independent minimum thresholds. A failed critical region triggers same-project correction even when the weighted average passes.
- Approved components require measured structuralMatch.score >= 0.96 plus evidence. Otherwise use admatic.native-composition.v2. Never silently substitute utility-message, global-header/classic or global-footer/columns in a reference-led plan.
- The header brand Image control may bind only to an assetRole=brand-logo manifest entry. With no valid brand logo, render a native text wordmark. Any content-photo in the brand control is a blocking validation failure.
- Prefer explicit Elementor Grid containers for repeated structures. Flexbox wrap is forbidden for card, feature, service, testimonial, price and gallery collections.
- Supported global-part families include overlay navigation, centered-logo split, utility-bar + primary, editorial asymmetric, contact-heavy footer, editorial wide footer, compact legal footer and CTA-led footer. Select by measured geometry, not industry defaults.



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.

REFERENCE-RELATIVE RHYTHM
Do not apply fixed global section-padding maxima or a universal spacing table. Measure section boundaries, content density, negative space, heading-to-body intervals, image crop proportions and viewport-specific whitespace from the reference. Flag excessive blank runs or compressed rhythm using rendered evidence rather than one fixed pixel number.

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.
