Komplex · coherent journey rebuild

Capture

Existing September master, with a visible ad or landing card and the OUTER comment selection marker/composer.

Set up / action

Enable review mode on the master; select a specific asset card. Expand its embedded screen while keeping the outer asset identity visible.

Viewport

Internal review canvas/document: 1280×900 CSS px, DPR 1. Open customer screens separately at mobile widths. A canvas thumbnail does not replace a readable mobile screenshot.

Required coverage

Capture outer selection and expanded asset. Inspect every embedded document for duplicate toolbars; include one readable landing example.

What independent Luna must be able to see/read:

• The selected asset has a stable identity and a precise outer selection/marker.
• Only the master exposes the review toolbar/composer. The embedded customer interface remains unobstructed.
• The marker refers to the intended asset or section, not an unrelated iframe boundary.

Evidence fields to fill: screenshot URL(s) · asset/day ID · state · viewport · capture time · deployed screen URL · actual Luna observations · reviewer report.

Capture

Old master asset cards and section-level landing critique.

Set up / action

Expand the existing asset and its saved critique at readable scale.

Viewport

Internal review canvas/document: 1280×900 CSS px, DPR 1. Open customer screens separately at mobile widths. A canvas thumbnail does not replace a readable mobile screenshot.

Required coverage

For every inventory asset attach asset-ID-linked screenshots. Landings require each section-level critique and the section it refers to.

What independent Luna must be able to see/read:

• The actual creative, email or landing passage being criticized is readable.
• Critique identifies why overview is difficult, the likely reader interpretation, a specific weakness and a concrete replacement/change.
• The suggested change concerns this asset and its next action; it is not a generic CRO checklist.

Evidence fields to fill: screenshot URL(s) · asset/day ID · state · viewport · capture time · deployed screen URL · actual Luna observations · reviewer report.

Capture

Canvas introduction: audience commonalities plus proposed Meta targeting card.

Set up / action

Show the complete persona and targeting assumptions; expand any hidden text.

Viewport

Internal review canvas/document: 1280×900 CSS px, DPR 1. Open customer screens separately at mobile widths. A canvas thumbnail does not replace a readable mobile screenshot.

Required coverage

One complete persona capture set, including common problem, self-framing, situations, emotions, desired progress and targeting proposal.

What independent Luna must be able to see/read:

• Concrete everyday situations explain who the broad adult audience is and what they want to improve.
• Problem, self-narrative, feelings and desired progress are distinct and understandable, with hypotheses labelled.
• Targeting card clearly states proposed geography, broad/Advantage+ approach, placements and test assumptions; no claim of campaign activation.

Evidence fields to fill: screenshot URL(s) · asset/day ID · state · viewport · capture time · deployed screen URL · actual Luna observations · reviewer report.

Capture

Canvas analysis card next to the actual ad, landing, email, checkout, lesson, feedback or consultation screen.

Set up / action

Open final asset and its reasoning card. Show hook/caption/body/CTA in actual reading order.

Viewport

Internal review canvas/document: 1280×900 CSS px, DPR 1. Open customer screens separately at mobile widths. A canvas thumbnail does not replace a readable mobile screenshot.

Required coverage

Every major step on both entry routes and the daily/consultation journey has a linked reasoning capture, not just the persona section.

What independent Luna must be able to see/read:

• Card distinguishes before-view attitude, attention hook, interpretation order, internal narrative and objection.
• It states the desired next thought and explains why the next action offers relevant value with credible delivery and manageable effort.
• A concrete criticism and resulting copy/UX improvement match what is visible in the final asset.

Evidence fields to fill: screenshot URL(s) · asset/day ID · state · viewport · capture time · deployed screen URL · actual Luna observations · reviewer report.

Capture

Fitted canvas overview plus readable acquisition and daily-row crops.

Set up / action

Use Fit, then focus the acquisition branch and the 14-day participant/Rita rows.

Viewport

Internal review canvas/document: 1280×900 CSS px, DPR 1. Open customer screens separately at mobile widths. A canvas thumbnail does not replace a readable mobile screenshot.

Required coverage

Capture full overview, both entry branches and row alignment covering every day-01–day-14.

What independent Luna must be able to see/read:

• Free-video and direct-challenge routes join the correct paid/access journey.
• Upload/feedback, consent, emails, checkout, confirmation/access, all daily screens, final video and consultation appear in logical order.
• Exactly 14 expert cards sit below matching participant day IDs, with recognizable labels.

Evidence fields to fill: screenshot URL(s) · asset/day ID · state · viewport · capture time · deployed screen URL · actual Luna observations · reviewer report.

Capture

Canvas at normal reading zoom and an expanded asset view.

Set up / action

Jump to an asset, open its readable full view, then return to the same canvas position.

Viewport

Internal review canvas/document: 1280×900 CSS px, DPR 1. Open customer screens separately at mobile widths. A canvas thumbnail does not replace a readable mobile screenshot.

Required coverage

Capture controls, focused stage, expanded view and restored position.

What independent Luna must be able to see/read:

• Pan/zoom/Fit/jump/open controls have understandable labels and the recommended route is obvious.
• Full copy is readable in an expanded view without tiny thumbnails being treated as the review surface.
• Outer comments and alternative-selection controls do not hide navigation.

Evidence fields to fill: screenshot URL(s) · asset/day ID · state · viewport · capture time · deployed screen URL · actual Luna observations · reviewer report.

Capture

Source CC Klíma canvas and the new customer journey canvas.

Set up / action

Capture matching control areas and the new focused journey view; use the actual source HTML, not a recreated drawing.

Viewport

Internal review canvas/document: 1280×900 CSS px, DPR 1. Open customer screens separately at mobile widths. A canvas thumbnail does not replace a readable mobile screenshot.

Required coverage

One source/output comparison plus open-and-return state of the new canvas.

What independent Luna must be able to see/read:

• New page retains useful spatial navigation, pan/zoom/jump and screen-opening behavior.
• The primary structure is a left-to-right journey with expert feedback below participant days.
• Branding and content are Komplex, while the reusable canvas navigation remains recognizable.

Evidence fields to fill: screenshot URL(s) · asset/day ID · state · viewport · capture time · deployed screen URL · actual Luna observations · reviewer report.

Capture

Canvas introduction/review index and a readable side-by-side variant panel.

Set up / action

Follow the stated review order; open an ad, both offer alternatives, one email and paired participant/Rita day.

Viewport

Internal review canvas/document: 1280×900 CSS px, DPR 1. Open customer screens separately at mobile widths. A canvas thumbnail does not replace a readable mobile screenshot.

Required coverage

Capture introduction, complete index groups, comparison state and matched day rows.

What independent Luna must be able to see/read:

• Recommended selections are labelled as recommendations, with alternatives easy to locate.
• Every deliverable group, important AI decision, critique and unsent client email has a visible route/link.
• Side-by-side alternatives remain readable and the user can return to the journey.

Evidence fields to fill: screenshot URL(s) · asset/day ID · state · viewport · capture time · deployed screen URL · actual Luna observations · reviewer report.

Capture

Full Facebook preview for each ad-01–ad-20, including actual image and matching copy.

Set up / action

Open each ad at readable mobile scale; expand long primary text if needed.

Viewport

Customer screen at 390×844 CSS px, DPR 1 for readable content. Add 360×800 and 430×932 for the stated mobile QA coverage. Never capture a desktop customer UI.

Required coverage

20 individual image/copy captures. Inspect all final image originals for square dimensions and caption spelling.

What independent Luna must be able to see/read:

• Each image is a genuine rendered 1:1 creative, not a placeholder or stretched crop.
• Caption is natural Hungarian, legible and relevant to its image and offer.
• Rita’s name is absent from every ad. The primary text makes clear what the click will open.

Evidence fields to fill: screenshot URL(s) · asset/day ID · state · viewport · capture time · deployed screen URL · actual Luna observations · reviewer report.

Capture

Each final Facebook preview plus its destination landing’s first screen.

Set up / action

Read the image/caption first, then primary text/headline/CTA; open its declared destination.

Viewport

Customer screen at 390×844 CSS px, DPR 1 for readable content. Add 360×800 and 430×932 for the stated mobile QA coverage. Never capture a desktop customer UI.

Required coverage

All 20 ad packs and both offer destinations; attach critique record IDs outside the customer preview.

What independent Luna must be able to see/read:

• Hook locates the reader in a recognizable situation or clear curiosity.
• Image caption and primary text form one understandable thought, then explain the offer and next step.
• The destination’s first screen answers the expectation created by the ad.

Evidence fields to fill: screenshot URL(s) · asset/day ID · state · viewport · capture time · deployed screen URL · actual Luna observations · reviewer report.

Capture

Canvas ad test guide with the corresponding creative/copy pairs.

Set up / action

Show representative variants for each angle, alongside what the comparison is intended to teach.

Viewport

Internal review canvas/document: 1280×900 CSS px, DPR 1. Open customer screens separately at mobile widths. A canvas thumbnail does not replace a readable mobile screenshot.

Required coverage

Every ad ID maps to a test angle and destination. Capture the guide and readable comparisons for the distinct angles.

What independent Luna must be able to see/read:

• Variants differ in a clear situation, hook, benefit emphasis or visual concept, not only a swapped adjective.
• Each proposed comparison identifies the audience/offer and a downstream action to observe.
• Recommended starting set is distinct from measured results.

Evidence fields to fill: screenshot URL(s) · asset/day ID · state · viewport · capture time · deployed screen URL · actual Luna observations · reviewer report.

Capture

free-video-A/B and challenge-A/B: ordered, readable section screenshot sets.

Set up / action

Use real deployed pages. Scroll so complete headings, copy, media and CTAs of each adapted section are visible.

Viewport

Customer screen at 390×844 CSS px, DPR 1 for readable content. Add 360×800 and 430×932 for the stated mobile QA coverage. Never capture a desktop customer UI.

Required coverage

All four pages, every adapted section, at 390; include 360/430 coverage in landing QA. Mapping must account for all requested S1–S28 layouts.

What independent Luna must be able to see/read:

• Each section preserves an identifiable supplied layout while serving a distinct offer-related purpose.
• Typography, palette, buttons and image treatment align with current Komplex references.
• Every section uses finished relevant content, with honest proof and no fake testimonial or arbitrary filler.

Evidence fields to fill: screenshot URL(s) · asset/day ID · state · viewport · capture time · deployed screen URL · actual Luna observations · reviewer report.

Capture

First mobile viewport of free-video-A, free-video-B, challenge-A and challenge-B.

Set up / action

Open as a first-time visitor, no scrolling. Hide reviewer overlays only, not customer content.

Viewport

Customer screen at 390×844 CSS px, DPR 1 for readable content. Add 360×800 and 430×932 for the stated mobile QA coverage. Never capture a desktop customer UI.

Required coverage

One first-screen capture per page at 390, plus 360/430 mobile QA.

What independent Luna must be able to see/read:

• Offer, intended visitor, practical benefit and immediate action are understandable from the first screen.
• Free-video route offers a clear first step; challenge route explains the two-week paid practice offer.
• Headline, subhead and CTA work together, with no unexplained promise or technical filler.

Evidence fields to fill: screenshot URL(s) · asset/day ID · state · viewport · capture time · deployed screen URL · actual Luna observations · reviewer report.

Capture

Side-by-side comparison of three full CTA-section alternatives for each of two offers.

Set up / action

Show full section headline, supporting copy, inclusion/friction information and button, then the linked demo state.

Viewport

Customer screen at 390×844 CSS px, DPR 1 for readable content. Add 360×800 and 430×932 for the stated mobile QA coverage. Never capture a desktop customer UI.

Required coverage

Six full CTA alternatives, readable mobile renderings and corresponding destination first screen.

What independent Luna must be able to see/read:

• Alternatives make materially different, coherent cases for the same next step.
• Button label and surrounding copy explain what happens after the click.
• Paid CTAs state the proposed offer/amount honestly; free CTAs do not imply payment.

Evidence fields to fill: screenshot URL(s) · asset/day ID · state · viewport · capture time · deployed screen URL · actual Luna observations · reviewer report.

Capture

Each custom illustration/infographic within its actual landing section.

Set up / action

Capture media at readable size with the accompanying explanatory heading/copy.

Viewport

Customer screen at 390×844 CSS px, DPR 1 for readable content. Add 360×800 and 430×932 for the stated mobile QA coverage. Never capture a desktop customer UI.

Required coverage

Seven unique visuals; include every placement and inspect each original at readable resolution.

What independent Luna must be able to see/read:

• Illustration explains the adjacent offer/process instead of adding unrelated decoration.
• Infographic labels are legible Hungarian, accurate and consistent with the written process.
• Visual is uncropped where its meaning depends on labels; essential instructions remain in readable text.

Evidence fields to fill: screenshot URL(s) · asset/day ID · state · viewport · capture time · deployed screen URL · actual Luna observations · reviewer report.

Capture

Current website/commented Figma reference crops beside final hero, programme, feedback, proof and CTA sections.

Set up / action

Capture references without modifying them and corresponding deployed sections at readable scale.

Viewport

Internal review canvas/document: 1280×900 CSS px, DPR 1. Open customer screens separately at mobile widths. A canvas thumbnail does not replace a readable mobile screenshot.

Required coverage

Reference set plus these key section types across all four variants; six CTA alternatives included.

What independent Luna must be able to see/read:

• Type hierarchy, palette, button shapes and imagery form the same recognizable visual system.
• Rita’s meaningful copy insight is reflected without importing superseded low-feedback promises.
• Sections clarify programme, daily feedback, practical concerns and next action with consistent tone.

Evidence fields to fill: screenshot URL(s) · asset/day ID · state · viewport · capture time · deployed screen URL · actual Luna observations · reviewer report.

Capture

Actual deployed sections of all four landing pages at 360/390/430.

Set up / action

Capture readable section runs including sticky CTA, long paragraphs, image labels, forms and validation.

Viewport

Customer screen at 390×844 CSS px, DPR 1 for readable content. Add 360×800 and 430×932 for the stated mobile QA coverage. Never capture a desktop customer UI.

Required coverage

All four variants at all three mobile widths. No section may be omitted; a very tall scaled-down screenshot is not readable evidence.

What independent Luna must be able to see/read:

• Copy, headings and image labels are readable without clipping or a wall of repeated claims.
• Controls do not overlap content or force horizontal scrolling.
• Every section has a relevant job and every media asset is finished.

Evidence fields to fill: screenshot URL(s) · asset/day ID · state · viewport · capture time · deployed screen URL · actual Luna observations · reviewer report.

Capture

Same landing section/state before and after a correction, on actual deployed revision.

Set up / action

Use the same viewport, section and scroll context. Attach final URL/build identifier.

Viewport

Customer screen at 390×844 CSS px, DPR 1 for readable content. Add 360×800 and 430×932 for the stated mobile QA coverage. Never capture a desktop customer UI.

Required coverage

Every significant Luna/content defect gets a comparable before/after pair and fresh independent observation.

What independent Luna must be able to see/read:

• The exact reported problem is visible in the before image and absent in the after image.
• Correction retains coherent offer and design, with surrounding context still readable.

Evidence fields to fill: screenshot URL(s) · asset/day ID · state · viewport · capture time · deployed screen URL · actual Luna observations · reviewer report.

Capture

Source passage and the corresponding expanded daily exercise section.

Set up / action

Show full exercise instructions, examples/poems and reflection wording. Label source range and proposed day split outside the customer text.

Viewport

Internal review canvas/document: 1280×900 CSS px, DPR 1. Open customer screens separately at mobile widths. A canvas thumbnail does not replace a readable mobile screenshot.

Required coverage

All original passages mapped across days 01–14. Capture source/render pairs for each module and every differing daily split.

What independent Luna must be able to see/read:

• Source wording and meaning remain recognizable and complete in the lesson.
• Original exercise copy is distinct from new navigation/summary wording.
• Six source modules are not falsely labelled fourteen originally approved lessons.

Evidence fields to fill: screenshot URL(s) · asset/day ID · state · viewport · capture time · deployed screen URL · actual Luna observations · reviewer report.

Capture

Daily image chooser/gallery with all four alternatives.

Set up / action

Open chooser for each day; expand both infographics to read their actual labels.

Viewport

Customer screen at 390×844 CSS px, DPR 1 for readable content. Add 360×800 and 430×932 for the stated mobile QA coverage. Never capture a desktop customer UI.

Required coverage

14 chooser capture sets, each showing two infographics and two AI images; all 28 infographics inspected at readable full resolution.

What independent Luna must be able to see/read:

• Four actual images are present, distinctly labelled by type/alternative.
• Recommended selection is clear and changing it shows the chosen image in the lesson.
• Visuals relate to the day’s task and infographic wording agrees with the original instruction.

Evidence fields to fill: screenshot URL(s) · asset/day ID · state · viewport · capture time · deployed screen URL · actual Luna observations · reviewer report.

Capture

Participant entry/overview and each day’s practice, reflection and video sections.

Set up / action

Enter demo mode, open a day, complete meaningful reflection and select/play fixture video, then demo-submit.

Viewport

Customer screen at 390×844 CSS px, DPR 1 for readable content. Add 360×800 and 430×932 for the stated mobile QA coverage. Never capture a desktop customer UI.

Required coverage

All 14 day views plus entry/overview; capture practice, filled form and submitted status. Include planned previous-feedback checkpoints.

What independent Luna must be able to see/read:

• The participant can tell what to do, record and submit, and what Rita will do next.
• Source journal prompts are real controls with visible chosen values/text and save status.
• Local demonstration labels make clear that a real server upload has not occurred.

Evidence fields to fill: screenshot URL(s) · asset/day ID · state · viewport · capture time · deployed screen URL · actual Luna observations · reviewer report.

Capture

Course overview and first viewport of each individual day.

Set up / action

Enter demo; open every overview tile and each direct day URL without waiting a real day.

Viewport

Customer screen at 390×844 CSS px, DPR 1 for readable content. Add 360×800 and 430×932 for the stated mobile QA coverage. Never capture a desktop customer UI.

Required coverage

One readable overview set plus 14 day-header captures. Capture enough overview sections to read every tile.

What independent Luna must be able to see/read:

• Days 01–14 have distinct stable IDs/titles and correctly ordered progress/status.
• Each day header identifies the task, source range/context and useful next action.
• Selected/pending/completed/feedback states are distinguishable.

Evidence fields to fill: screenshot URL(s) · asset/day ID · state · viewport · capture time · deployed screen URL · actual Luna observations · reviewer report.

Capture

All sections of each daily lesson with expandable exercise text opened.

Set up / action

Expand core instructions and any source text/download previews. Capture sections sequentially at readable scale.

Viewport

Customer screen at 390×844 CSS px, DPR 1 for readable content. Add 360×800 and 430×932 for the stated mobile QA coverage. Never capture a desktop customer UI.

Required coverage

All 14 daily content sets and all original module passages. Capture the entire relevant poem/example/instruction, not only its heading.

What independent Luna must be able to see/read:

• Reason for practice, ordered full instructions, examples, supplied repetitions/duration and original reflection prompts are present.
• Core exercises and optional extras are clearly separated.
• Recording instruction and next step complete the lesson; unavailable original media is honestly marked.

Evidence fields to fill: screenshot URL(s) · asset/day ID · state · viewport · capture time · deployed screen URL · actual Luna observations · reviewer report.

Capture

Daily first screen followed by contiguous task/feedback/practice/form/submission sections.

Set up / action

Open each day as a returning participant. On checkpoints open yesterday’s feedback before current practice.

Viewport

Customer screen at 390×844 CSS px, DPR 1 for readable content. Add 360×800 and 430×932 for the stated mobile QA coverage. Never capture a desktop customer UI.

Required coverage

All 14 day first screens and ordered section captures; special checkpoint sequence on days 2,5,8,12 unless a logged source-based alternative replaces it.

What independent Luna must be able to see/read:

• Day/progress, plain task summary and first useful action are immediately clear.
• Order is previous review where scheduled, practice reason, ordered exercises, reflection, recording/submission and next expectation.
• Steps are scannable without controls competing with the instructions.

Evidence fields to fill: screenshot URL(s) · asset/day ID · state · viewport · capture time · deployed screen URL · actual Luna observations · reviewer report.

Capture

Each day’s Napló & önértékelés form.

Set up / action

Capture unanswered state, then change labelled sliders and enter a day-specific reflection.

Viewport

Customer screen at 390×844 CSS px, DPR 1 for readable content. Add 360×800 and 430×932 for the stated mobile QA coverage. Never capture a desktop customer UI.

Required coverage

14 day form sets: unanswered, edited/unsaved, saved and reloaded readback. Include a demonstrated failed-save state.

What independent Luna must be able to see/read:

• Original prompts and scale labels/endpoints are readable.
• Unanswered is different from a real zero or middle score; changed values and reflection text are visible.
• Saved/unsaved/error status is clear and the reloaded form belongs to the same day.

Evidence fields to fill: screenshot URL(s) · asset/day ID · state · viewport · capture time · deployed screen URL · actual Luna observations · reviewer report.

Capture

Daily recording/video submission area.

Set up / action

Try submission with no file and an unsupported file; then select playable fixture video, play, replace and remove it.

Viewport

Customer screen at 390×844 CSS px, DPR 1 for readable content. Add 360×800 and 430×932 for the stated mobile QA coverage. Never capture a desktop customer UI.

Required coverage

Every day supports these states; capture readable state sets across all 14 IDs. Include actual error and valid-preview captures.

What independent Luna must be able to see/read:

• Recording guidance, chosen file/day, real video controls, replace/remove and submit actions are visible.
• No-file/unsupported-file error is understandable and does not show successful submission.
• Removal restores a clear empty state. Preview shows the intended video rather than an unrelated thumbnail.

Evidence fields to fill: screenshot URL(s) · asset/day ID · state · viewport · capture time · deployed screen URL · actual Luna observations · reviewer report.

Capture

Daily submitted/waiting feedback screen and reloaded video state.

Set up / action

Select valid video and deliberately demo-submit; reload the same day.

Viewport

Customer screen at 390×844 CSS px, DPR 1 for readable content. Add 360×800 and 430×932 for the stated mobile QA coverage. Never capture a desktop customer UI.

Required coverage

Submitted/waiting and reload readback for day01–14.

What independent Luna must be able to see/read:

• Success explicitly identifies a prototype/local demonstration and explains daily Rita review.
• Correct day/file metadata remains consistent. If bytes were not retained, reselection is requested and no broken player is shown.
• Waiting for feedback is different from feedback already received.

Evidence fields to fill: screenshot URL(s) · asset/day ID · state · viewport · capture time · deployed screen URL · actual Luna observations · reviewer report.

Capture

Same participant/day before submission, waiting, feedback available and read.

Set up / action

Use one demo fixture, deliberately send feedback from the matching Rita view and return to participant.

Viewport

Customer screen at 390×844 CSS px, DPR 1 for readable content. Add 360×800 and 430×932 for the stated mobile QA coverage. Never capture a desktop customer UI.

Required coverage

All 14 day feedback states; clearly appropriate Day1 start. Focus readable checkpoint sequences on days2,5,8,12.

What independent Luna must be able to see/read:

• Not submitted, waiting, feedback available and reviewed are distinct states.
• Yesterday’s video/day ID and specific sample feedback match the previous task.
• Next practice focus links to the current source exercise, with sample content labelled.

Evidence fields to fill: screenshot URL(s) · asset/day ID · state · viewport · capture time · deployed screen URL · actual Luna observations · reviewer report.

Capture

Day-specific chooser plus expanded infographic and selected in-lesson visual.

Set up / action

Show source task heading nearby; expand image when labels would otherwise be too small.

Viewport

Customer screen at 390×844 CSS px, DPR 1 for readable content. Add 360×800 and 430×932 for the stated mobile QA coverage. Never capture a desktop customer UI.

Required coverage

All 14 days × four alternatives. Inspect every infographic at text-readable scale, plus every selected mobile placement.

What independent Luna must be able to see/read:

• Infographic labels support the day’s exact exercise, with correct Hungarian and readable layout.
• AI image has a clear task-related purpose, no fabricated anatomical assertion.
• Essential exercise wording remains textual and does not depend on reading tiny image captions.

Evidence fields to fill: screenshot URL(s) · asset/day ID · state · viewport · capture time · deployed screen URL · actual Luna observations · reviewer report.

Capture

Demo entry, overview and all14 participant days: header, long instruction, form, media and primary actions.

Set up / action

Use actual deployment; capture each section/state at requested mobile widths, including long Hungarian content.

Viewport

Customer screen at 390×844 CSS px, DPR 1 for readable content. Add 360×800 and 430×932 for the stated mobile QA coverage. Never capture a desktop customer UI.

Required coverage

Entry/overview and day01–14 at 360×800, 390×844 and 430×932 CSS px. Cover every section and significant state at readable scale.

What independent Luna must be able to see/read:

• No horizontal scrolling, overlap, clipped text or sticky control hiding the current task.
• Labels and touch controls are usable and readable, including long reflection/video states.
• Day context/navigation remain obvious throughout the screen.

Evidence fields to fill: screenshot URL(s) · asset/day ID · state · viewport · capture time · deployed screen URL · actual Luna observations · reviewer report.

Capture

Day14 final task/reflection/video and consultation preparation/confirmation.

Set up / action

Finish the final demo task, then follow the actual next-action control to preparation and sample booking.

Viewport

Customer screen at 390×844 CSS px, DPR 1 for readable content. Add 360×800 and 430×932 for the stated mobile QA coverage. Never capture a desktop customer UI.

Required coverage

Capture each transition and both participant and Rita consultation contexts.

What independent Luna must be able to see/read:

• Original final practice/reflection remains intact.
• The next step states what to prepare, what the online consultation discusses and what follows.
• Booking is visibly sample/demo; the programme is a practical start, not a guaranteed cure or completed development.

Evidence fields to fill: screenshot URL(s) · asset/day ID · state · viewport · capture time · deployed screen URL · actual Luna observations · reviewer report.

Capture

Aligned canvas row plus readable participant submission, Rita editor/sent and participant received view.

Set up / action

Use the same sample participant/day and send a distinctive feedback message.

Viewport

Customer screen at 390×844 CSS px, DPR 1 for readable content. Add 360×800 and 430×932 for the stated mobile QA coverage. Never capture a desktop customer UI.

Required coverage

All14 matched day IDs; each has full context screenshots and feedback readback.

What independent Luna must be able to see/read:

• Expert screen sits below the matching participant day in the canvas.
• Submission day, participant, video and feedback editor/sent states refer to the same task.
• Participant readback displays the actual demo message entered in that Rita view.

Evidence fields to fill: screenshot URL(s) · asset/day ID · state · viewport · capture time · deployed screen URL · actual Luna observations · reviewer report.

Capture

Rita feedback preview and matching participant feedback panel.

Set up / action

Expand full sample text and show day/task context.

Viewport

Customer screen at 390×844 CSS px, DPR 1 for readable content. Add 360×800 and 430×932 for the stated mobile QA coverage. Never capture a desktop customer UI.

Required coverage

All14 full sample messages, not a cropped preview or one reused paragraph.

What independent Luna must be able to see/read:

• Each message gives a concrete observation and an actionable next practice focus.
• It uses supportive natural Hungarian and is clearly sample content.
• Daily personal feedback is the pilot model without unsupported diagnosis or fabricated personal improvement.

Evidence fields to fill: screenshot URL(s) · asset/day ID · state · viewport · capture time · deployed screen URL · actual Luna observations · reviewer report.

Capture

Rita queue/review header, task context, video and reflection.

Set up / action

Capture before/after switching between distinct days and sample participants.

Viewport

Customer screen at 390×844 CSS px, DPR 1 for readable content. Add 360×800 and 430×932 for the stated mobile QA coverage. Never capture a desktop customer UI.

Required coverage

Every14 day IDs; include one deliberate day/participant switch comparison.

What independent Luna must be able to see/read:

• Sample participant, day, task/source, submission time/status and video identity are clear.
• Video, reflection and feedback context change together with the selected day.
• Demo data is labelled, with no claim of a real client upload.

Evidence fields to fill: screenshot URL(s) · asset/day ID · state · viewport · capture time · deployed screen URL · actual Luna observations · reviewer report.

Capture

Rita video/reflect/editor panel, empty-validation, saved-draft and send-confirmation states.

Set up / action

Read reflection, enter a distinctive message, save/reload/edit, preview, then mark sent. Attempt empty feedback separately.

Viewport

Customer screen at 390×844 CSS px, DPR 1 for readable content. Add 360×800 and 430×932 for the stated mobile QA coverage. Never capture a desktop customer UI.

Required coverage

All14 day workflows. Include visible empty-error, restored-draft, preview, recipient/day confirmation and participant readback.

What independent Luna must be able to see/read:

• Player controls, source task/reflection and editor are readable together or through clear navigation.
• Draft status and full message are visible; empty feedback cannot appear sent.
• Preview/confirmation states identify recipient/day and mark delivery as a prototype action.

Evidence fields to fill: screenshot URL(s) · asset/day ID · state · viewport · capture time · deployed screen URL · actual Luna observations · reviewer report.

Capture

Full daily sample feedback with the matching original exercise context.

Set up / action

Open each sample in the review preview. Do not crop the closing action or its qualifiers.

Viewport

Customer screen at 390×844 CSS px, DPR 1 for readable content. Add 360×800 and 430×932 for the stated mobile QA coverage. Never capture a desktop customer UI.

Required coverage

One readable full-text/context capture per day01–14.

What independent Luna must be able to see/read:

• Observation, supportive explanation and next focus are identifiable and relevant to this day.
• The fourteen messages are meaningfully differentiated, natural Hungarian and explicitly sample text.
• The next action respects the actual exercise instead of adding a new unsupported technique.

Evidence fields to fill: screenshot URL(s) · asset/day ID · state · viewport · capture time · deployed screen URL · actual Luna observations · reviewer report.

Capture

All14 expert day views in waiting/unread/draft/sent states.

Set up / action

Use actual deployed expert prototype and enter a long Hungarian message; inspect task/video/reflection and primary action.

Viewport

Customer screen at 390×844 CSS px, DPR 1 for readable content. Add 360×800 and 430×932 for the stated mobile QA coverage. Never capture a desktop customer UI.

Required coverage

All14 expert views at 360×800,390×844,430×932. Capture long editor, validation and status states, not only the header.

What independent Luna must be able to see/read:

• Komplex UI system is consistent and queue/status labels are clear.
• Long text fields and controls remain readable without overflow or hidden task context.
• Primary action is reachable and does not cover the player/editor or confuse save with send.

Evidence fields to fill: screenshot URL(s) · asset/day ID · state · viewport · capture time · deployed screen URL · actual Luna observations · reviewer report.

Capture

Paid landing CTA, Stripe-like checkout, success/access, cancel, pending/error and sold-out/waitlist.

Set up / action

Choose the review offer; navigate each demo state using explicit prototype controls.

Viewport

Customer screen at 390×844 CSS px, DPR 1 for readable content. Add 360×800 and 430×932 for the stated mobile QA coverage. Never capture a desktop customer UI.

Required coverage

All four landing variant destinations as applicable, and every listed checkout branch.

What independent Luna must be able to see/read:

• Challenge, proposed one-time amount, inclusions and next step agree between landing and checkout.
• Success opens confirmation/access; cancellation returns to the right offer; pending/error explains sensible retry; sold-out offers a demo waitlist.
• Prototype/simulated labels are clear and do not imply actual payment or enrollment.

Evidence fields to fill: screenshot URL(s) · asset/day ID · state · viewport · capture time · deployed screen URL · actual Luna observations · reviewer report.

Capture

Canvas email sequence with readable A/B service/nurture/newsletter/promotion previews and consent/suppression cards.

Set up / action

Open complete email bodies, including footer/CTA; inspect subscribed versus not-subscribed and purchased fixture states.

Viewport

Internal review canvas/document: 1280×900 CSS px, DPR 1. Open customer screens separately at mobile widths. A canvas thumbnail does not replace a readable mobile screenshot.

Required coverage

Every email/variant in full inventory and all sequence rules, including weekly newsletter and fixed-cohort campaign.

What independent Luna must be able to see/read:

• Emails are in the correct recipient/trigger order with complete natural copy and matching links.
• Required service messages are distinct from optional marketing consent.
• Promotion replaces the weekly newsletter during cohort campaign and paid participants are shown excluded from sales reminders.

Evidence fields to fill: screenshot URL(s) · asset/day ID · state · viewport · capture time · deployed screen URL · actual Luna observations · reviewer report.

Capture

Final-day next-action and consultation participant/Rita views.

Set up / action

Open final practice and follow the consultation preparation link.

Viewport

Customer screen at 390×844 CSS px, DPR 1 for readable content. Add 360×800 and 430×932 for the stated mobile QA coverage. Never capture a desktop customer UI.

Required coverage

Capture full preparation and participant/Rita consultation context.

What independent Luna must be able to see/read:

• The visitor can state when the call happens, what to prepare, what is reviewed and what follows.
• Sample booking and confirmation are honest; the call reviews practice and useful next steps.
• No guaranteed cure, completed development or real slot claim is made.

Evidence fields to fill: screenshot URL(s) · asset/day ID · state · viewport · capture time · deployed screen URL · actual Luna observations · reviewer report.

Capture

Each paid landing CTA → correct checkout → confirmation/access/overview; cancel/error/waitlist branches.

Set up / action

Click real controls; retain selected offer/version. After cancellation return to the same offer.

Viewport

Customer screen at 390×844 CSS px, DPR 1 for readable content. Add 360×800 and 430×932 for the stated mobile QA coverage. Never capture a desktop customer UI.

Required coverage

Both challenge variants and all critical CTA alternatives; every branch and subsequent access screen.

What independent Luna must be able to see/read:

• Selected challenge/amount/inclusions stay consistent and the next screen follows from the button label.
• Success offers clear access/overview, retry retains context, cancellation restores offer, sold-out leads to demo waitlist.
• Customer is not stranded on a static screenshot with no useful next action.

Evidence fields to fill: screenshot URL(s) · asset/day ID · state · viewport · capture time · deployed screen URL · actual Luna observations · reviewer report.

Capture

Mobile email preview showing subject/preheader/body/CTA; A/B comparison and destination.

Set up / action

Expand full body; open the linked frontend state. Place analysis labels outside the customer email.

Viewport

Customer screen at 390×844 CSS px, DPR 1 for readable content. Add 360×800 and 430×932 for the stated mobile QA coverage. Never capture a desktop customer UI.

Required coverage

All emails and substantive A/B alternatives, including newsletter and cohort sales.

What independent Luna must be able to see/read:

• Trigger and recipient stage are clear in review metadata. Full body, subject, preheader and CTA are readable.
• Hook builds a natural relevant thought before the offer, not an arbitrary feature list.
• Feedback follow-up does not pretend an unsubmitted video was reviewed; CTA opens the promised step.

Evidence fields to fill: screenshot URL(s) · asset/day ID · state · viewport · capture time · deployed screen URL · actual Luna observations · reviewer report.

Capture

Consultation UI: preparation, slot choice, confirmation, link state, rescheduling/cancel and next-step.

Set up / action

Choose a sample slot; confirm, reschedule and cancel in demo. Open post-consultation view separately.

Viewport

Customer screen at 390×844 CSS px, DPR 1 for readable content. Add 360×800 and 430×932 for the stated mobile QA coverage. Never capture a desktop customer UI.

Required coverage

Every consultation state, plus source-consistent explanation of early reservation versus post-challenge call.

What independent Luna must be able to see/read:

• Purpose, required preparation, sample date/time and confirmation next step are understandable.
• Meeting-link state honestly says demo/unconfirmed and does not invent a real Meet destination.
• Reschedule/cancel has a clear result; after-call screen describes next options rather than claiming a fabricated outcome.

Evidence fields to fill: screenshot URL(s) · asset/day ID · state · viewport · capture time · deployed screen URL · actual Luna observations · reviewer report.

Capture

Readable relevant excerpts from ad, landing, checkout, email, daily lesson, expert feedback and consultation beside promise matrix.

Set up / action

Show inclusions and expectation-setting passages in the actual deployed assets, not a newly written summary only.

Viewport

Internal review canvas/document: 1280×900 CSS px, DPR 1. Open customer screens separately at mobile widths. A canvas thumbnail does not replace a readable mobile screenshot.

Required coverage

Every asset variant mapped; include daily tasks/video/daily feedback/final consultation and date/price/limit claims.

What independent Luna must be able to see/read:

• All stages offer the same fourteen-day practice with daily submissions/personal feedback and sourced final consultation.
• Proposed price/capacity and unconfirmed dates remain consistently labelled, with no fabricated countdown or urgency.
• Two-week practical progress is distinct from longer-term development.

Evidence fields to fill: screenshot URL(s) · asset/day ID · state · viewport · capture time · deployed screen URL · actual Luna observations · reviewer report.

Capture

Canvas introduction, recommended path, full categorized index and variant comparison links.

Set up / action

Expand every index group and recommendation/decision panel.

Viewport

Internal review canvas/document: 1280×900 CSS px, DPR 1. Open customer screens separately at mobile widths. A canvas thumbnail does not replace a readable mobile screenshot.

Required coverage

Cover all nine deliverable groups and every manifest asset/alternative with readable index entries.

What independent Luna must be able to see/read:

• Recommended path is easy to find with substantive alternatives one click away.
• Day01–14 and matching expert views, all20 ads, all4 landings, email variants, critique, decisions and client email are represented.
• Recommendations are not labelled measured winners or Rita-approved assets.

Evidence fields to fill: screenshot URL(s) · asset/day ID · state · viewport · capture time · deployed screen URL · actual Luna observations · reviewer report.

Capture

Final Hungarian email draft on the review surface.

Set up / action

Show subject and complete body, including all URL descriptions and review questions.

Viewport

Internal review canvas/document: 1280×900 CSS px, DPR 1. Open customer screens separately at mobile widths. A canvas thumbnail does not replace a readable mobile screenshot.

Required coverage

Capture the entire email at readable scale; follow and independently verify every included URL.

What independent Luna must be able to see/read:

• Email tells Rita what each URL contains, what to review and the guiding principles.
• It describes the actual delivered frontend review/proposals honestly and explains consequential decisions needing approval.
• Draft/unsent status is explicit in review metadata, with no claim of sending or client approval.

Evidence fields to fill: screenshot URL(s) · asset/day ID · state · viewport · capture time · deployed screen URL · actual Luna observations · reviewer report.

Capture

QA evidence index linking actual mobile screenshots and blind Luna reports.

Set up / action

Show asset/section/state/viewport, deployed build and review/fix/recheck references. Open readable samples.

Viewport

Internal review canvas/document: 1280×900 CSS px, DPR 1. Open customer screens separately at mobile widths. A canvas thumbnail does not replace a readable mobile screenshot.

Required coverage

Every changed customer page/section and significant state at 360/390/430, split into at least two independent QA partitions.

What independent Luna must be able to see/read:

• Each evidence item identifies the exact deployed asset, state and viewport, with actual screenshot and independent observations.
• Original defect, corrective action and fresh recheck are linked without hiding outstanding issues.
• Only mobile customer captures are counted. Review canvas screenshots remain a separate document category.

Evidence fields to fill: screenshot URL(s) · asset/day ID · state · viewport · capture time · deployed screen URL · actual Luna observations · reviewer report.

Capture

Readable before/after mobile section screenshots for every material defect.

Set up / action

Capture corrected section/state at same viewport on the final deployed build; get fresh independent observations.

Viewport

Customer screen at 390×844 CSS px, DPR 1 for readable content. Add 360×800 and 430×932 for the stated mobile QA coverage. Never capture a desktop customer UI.

Required coverage

All significant visual/content/UX defects from both partitions, with matching before/after contexts.

What independent Luna must be able to see/read:

• The specific defect is visible before and resolved after, at the same readable scale.
• Nearby content remains usable and the final capture genuinely belongs to the deployed revision.

Evidence fields to fill: screenshot URL(s) · asset/day ID · state · viewport · capture time · deployed screen URL · actual Luna observations · reviewer report.