Create an editable HTML/CSS composition with selectable text and a print stylesheet; treat any raster illustration as a separate local asset for [PROJECT] and [AUDIENCE]. The task is: Event Ticket Design.

## Required content and structure

Prioritize event, date, seat or entry type and a clearly labeled validation area.

Use [APPROVED_CONTENT] as the source of names, dates, figures, claims and destinations. List missing inputs before substituting anything. If a demonstration is needed, label its content as fictional. Do not invent customer quotes, rankings, partner logos or product capabilities.

## Design direction

Use [BRAND_RULES] and the design system already selected in the project. If no system is supplied, start with this direction: muted lavender, ink typography and apricot accents; thoughtful negative space and a distinctive visual motif. Keep type, spacing and color roles consistent. Prioritize the task over decorative elements and avoid a generic collection of unrelated cards.

## Content preparation

Prepare event details, date, venue, seat or entry type, holder information and validation requirements. Clarify the area reserved for a real issuing system's code.

## Layout and behavior

Make entry details scannable for both the attendee and door staff. Keep the validation area distinct from decorative graphics and preserve safe margins.

## Task-specific acceptance check

- Do not generate a fake functional barcode or QR code.
- Check long seat labels and small print.
- Do not fabricate a functional barcode or QR code; a concept should label the reserved validation area clearly.

## Implementation and review

Keep text editable. Use semantic structure, descriptive controls, visible keyboard focus and appropriate empty/error states. Check narrow and wide layouts. Respect reduced-motion preferences. Preserve any existing project framework and dependencies; do not silently replace the stack. Return the editable files and explain any incomplete behavior or unsupported inputs. Review this specific task before proposing extra features.

Keep exact text and required credits as live text. Ask for the intended dimensions when they are missing. Do not invent a functional QR code, barcode, signature or official seal.

## Reference attachment and reconstruction goal

Attach reference.webp from this prompt’s download bundle alongside this prompt in OpenDesign. Build an editable result with a similar composition and hierarchy; do not embed the whole reference image as the finished interface. Preserve approved project content and brand rules if they conflict with fictional sample labels. If the image is missing or unreadable, ask for it instead of claiming visual fidelity.

## Reference composition and content

Use the attached reference.webp as the visual reference for Event Ticket Design. Before building, identify the major regions from top to bottom, their relative widths and heights, alignment, spacing, typography hierarchy, surface colors, borders, imagery and repeated components. Preserve those relationships rather than substituting a generic template. Required task content: Prioritize event, date, seat or entry type and a clearly labeled validation area. Use the following task-specific layout guidance when translating the image into editable elements: Make entry details scannable for both the attendee and door staff. Keep the validation area distinct from decorative graphics and preserve safe margins.

## Visual direction from the example brief

muted lavender, ink typography and apricot accents; thoughtful negative space and a distinctive visual motif.

## Output and editability

Recreate the finished graphic as editable text, shapes and image layers. The reference is a composition, not an editor interface; do not add navigation, forms or dashboard widgets that are absent from it. Make entry details scannable for both the attendee and door staff. Keep the validation area distinct from decorative graphics and preserve safe margins. Confirm intended dimensions and preserve text hierarchy when adapting the artwork. Do not generate a fake functional barcode or QR code.

## Visual comparison and delivery

1. Compare the result with the attached image at matching proportions. Review major region placement, relative image sizes, line breaks, spacing, typography hierarchy, contrast, active states and content density before polishing decorative details.
2. Then test the narrow layout without squeezing desktop text into tiny labels.
3. Keep logos, photos and icons as separate assets and all meaningful labels editable. List any unavailable fonts/assets and any intentional departures. Return the working files plus a concise account of implemented behavior and remaining integrations; do not promise a pixel-identical result from the prompt alone.