briefing-critique

name	briefing-critique
description	Compare generated draft pages against the source briefing to catch copy errors, missing content, wrong block types, and structural mismatches. Use when "critique drafts", "check briefing compliance", "verify content fidelity", "QA against briefing", or "validate draft pages".

Briefing Critique

Quick Reference

Category	Trigger	Complexity	Source
audit	"critique drafts", "check briefing compliance", "verify content fidelity", "QA against briefing"	High	az-sitebuilder

Systematically compare generated draft .plain.html pages against a source briefing document to detect copy errors, missing content, wrong block types, image mismatches, and structural problems. Also verifies published AEM content against the briefing to catch post-upload drift. Produces a severity-rated findings report with fix suggestions. Auto-detects fidelity level from the briefing's own instructions to avoid false positives.

When to Use

• After generating site pages from a briefing and before uploading to DA
• User wants to verify all briefing content made it into the drafts accurately
• User asks to "QA", "check", "review", or "validate" drafts against a briefing
• Before running upload-to-da.sh as a final quality gate
• After making bulk edits to drafts and needing to re-verify compliance
• User suspects copy or image drift between briefing and generated pages
• After uploading to DA, to verify the published AEM content still matches the briefing (catches post-upload edits in DA)

Instructions

Step 1: Identify Sources and Determine Fidelity Level

Locate the briefing and draft files for the target site:

• Briefing: sites/{sitename}/briefing.md or sites/{sitename}/briefing.docx
  • For .docx files, extract text content (use a tool or read what's available)
  • For .md files, read directly
• Drafts: All drafts/{sitename}/*.plain.html files

Read the briefing thoroughly and detect three independent fidelity dimensions by examining the briefing's own instructions and structure:

Dimension	Strict	Flexible
Copy	Briefing says "must be used exactly as written", "verbatim", "MLR-approved", or provides precise copy per section	No such instruction; briefing provides descriptions, outlines, or topic summaries
Block types	Briefing specifies block types explicitly (e.g., **Block:** hero-teaser) per section	Briefing describes content intent ("three cards", "image left text right") without naming blocks
Image mapping	Briefing specifies exact image filenames per section (e.g., Image: hero-home.jpeg)	Briefing gives general image descriptions without specific filenames

The detected fidelity level determines what subsequent steps check and how strictly they check it:

• Strict copy: Paragraph-by-paragraph verbatim comparison after normalization
• Flexible copy: Check intent coverage — are all key topics, messages, and data points present?
• Strict blocks: Exact block type match per section
• Flexible blocks: Verify the chosen block is reasonable for the content intent
• Strict images: Verify the correct image filename appears in the draft for each section
• Flexible images: Verify an appropriate image exists in each section that expects one

State the detected fidelity level at the top of the report with evidence (quote the briefing text that determined each dimension).

---

Step 2: Page Inventory

Compare the set of expected pages (from the briefing's page/sitemap list) against the actual files found in drafts/{sitename}/.

Check	Severity
Page listed in briefing but no corresponding .plain.html file	CRITICAL
.plain.html file exists with no corresponding briefing entry	LOW
nav.plain.html missing	CRITICAL
footer.plain.html missing	CRITICAL

List all expected pages and their found/missing status. Include nav.plain.html and footer.plain.html in the inventory.

---

Step 3: Nav and Footer Verification

Nav checks:

• Nav links match the briefing's navigation section (correct pages, correct order, correct count). The briefing's nav section is authoritative — if it lists 4 pages, nav should have exactly 4 page links. Do NOT use the full page inventory as the reference; some pages may be intentionally excluded from top-level navigation.
• All links use /{sitename}/ prefix
• Logo <img src> uses CDN URL (https://{sitename}-images.pages.dev/)
• Search icon uses CDN URL
• Top bar links present (Contact Us, AZ Employee Login)

Footer checks:

• Footer site links match the briefing's footer section (not the full page inventory). If the briefing's footer section lists specific pages, use that list.
• Approval code matches briefing (if specified)
• Brand trademark text present with correct drug/brand name
• AstraZeneca logo uses CDN URL
• Regulatory links present (Report Adverse Event, Medical Information, Privacy, Terms, Accessibility)
• Date of preparation present

Placeholder detection:

• Any href in nav/footer that equals /{sitename}/ and is NOT the logo home link or Login CTA is a likely unfilled placeholder
• Cross-reference against the briefing's nav/footer sections — if the briefing specifies a real URL, flag this as HIGH
• If the briefing doesn't specify a URL for that link, flag as MEDIUM (potential oversight)

Flag any mismatch with severity HIGH.

---

Step 4: Structural Comparison

For each page, compare the structural layout between briefing and draft:

1. Section count: Does the number of content sections match?
2. Block types per section:
   • Strict mode: Does each section use the exact block type specified in the briefing?
   • Flexible mode: Is the chosen block type reasonable for the described content?
3. Section-metadata styles: Do highlight, light, or other style variants match what the briefing specifies?
4. Section ordering: Are sections in the same order as the briefing?
5. Metadata block: Does the page have a metadata block with Title and Description?

Block type inference from descriptions

Some briefing sections describe the content intent rather than naming a block explicitly (e.g., "Hero (full-width image with text overlay)" instead of "Block: hero-teaser"). In strict mode, infer the block type from the description using this mapping before flagging a mismatch:

Briefing description pattern	Inferred block type
"Hero", "full-width image with text overlay"	hero-teaser
"Page header (text only, no image)"	title
"centred text", "centered text"	introduction
"two-column: image left, text right" or "image right, text left"	columns-teaser
"equal columns", "card grid", "three cards"	cards-teaser
"data table", "comparison table"	table-data
"tabs", "tabbed content"	tabs-large
"expandable sections", "accordion"	accordion

Only flag a block type mismatch if neither the explicit name nor the inferred name matches the draft.

Finding	Severity
Missing content section	HIGH
Wrong block type (strict mode)	MEDIUM
Block type could be better (flexible mode)	LOW
Wrong section-metadata style	MEDIUM
Sections in wrong order	MEDIUM
Missing metadata block	MEDIUM

---

Step 5: Copy Fidelity

This is the critical step. The approach depends on the detected fidelity level.

Strict Mode (verbatim copy specified)

NEVER compare copy by reading — always run the diff script below. Visual comparison misses single-word deletions that change clinical meaning (e.g., "adults and adolescents" → "adults" narrows the approved indication by one deleted word). The script catches every difference mechanically.

Run this script for each content page (excluding nav/footer). Replace {sitename} with the actual site name:

python3 << 'PYEOF'
import html, re, glob, difflib, json

SITENAME = "{sitename}"

def normalize(text):
    """Strip HTML tags, decode entities, collapse whitespace."""
    text = re.sub(r'<[^>]+>', ' ', text)
    text = html.unescape(text)
    text = re.sub(r'\s+', ' ', text).strip()
    return text

# --- Extract briefing paragraphs keyed by page ---
with open(f'sites/{SITENAME}/briefing.md') as f:
    briefing = f.read()

# Split into page sections
page_sections = re.split(r'## PAGE \d+:\s*', briefing)[1:]
page_labels = re.findall(r'## PAGE \d+:\s*(.+)', briefing)

findings = []
for label, section in zip(page_labels, page_sections):
    # Extract text fields from briefing section
    fields = re.findall(
        r'\*\*(?:Heading|Body text|Body text \(continued\)|Card heading|Card body|Card link):\*\*\s*(.+?)(?=\n\n|\n\*\*[A-Z]|\Z)',
        section, re.DOTALL
    )
    briefing_texts = []
    for f in fields:
        t = f.strip().split(' → ')[0]  # strip CTA arrow targets
        t = t.replace('\\\n', ' ').replace('\\', '')
        t = normalize(t)
        if len(t) > 15:
            briefing_texts.append(t)

    # Determine draft filename from page label
    slug_map = {}
    url_match = re.search(r'\*\*URL path:\*\*\s*/\w+/(\S*)', section)
    slug = url_match.group(1) if url_match and url_match.group(1) else 'index'
    draft_path = f'drafts/{SITENAME}/{slug}.plain.html' if slug else f'drafts/{SITENAME}/index.plain.html'

    try:
        with open(draft_path) as df:
            draft_html = df.read()
    except FileNotFoundError:
        findings.append({"page": slug, "severity": "CRITICAL", "msg": f"Draft file not found: {draft_path}"})
        continue

    # Extract text from draft paragraphs and headings
    draft_paras = re.findall(r'<(?:p|h[1-6])(?:\s[^>]*)?>(.+?)</(?:p|h[1-6])>', draft_html, re.DOTALL)
    # Also extract table cell text
    draft_cells = re.findall(r'<div>([^<]+)</div>', draft_html)
    all_draft = [normalize(p) for p in draft_paras + draft_cells if len(normalize(p)) > 10]

    # For each briefing paragraph, find the best match in the draft
    for bt in briefing_texts:
        best_ratio = 0
        best_draft = ""
        for dt in all_draft:
            r = difflib.SequenceMatcher(None, bt, dt).ratio()
            if r > best_ratio:
                best_ratio = r
                best_draft = dt
        if best_ratio >= 0.85 and best_ratio < 1.0:
            # Near-match: show what changed
            findings.append({
                "page": slug or "index", "severity": "CRITICAL",
                "briefing": bt[:300], "draft": best_draft[:300],
                "ratio": f"{best_ratio:.3f}"
            })
        elif best_ratio < 0.85:
            # No close match found — paragraph may be missing
            findings.append({
                "page": slug or "index", "severity": "CRITICAL",
                "msg": f"Briefing text not found in draft (best match ratio: {best_ratio:.2f})",
                "briefing": bt[:300], "draft": best_draft[:300] if best_draft else "(none)"
            })

if findings:
    print(f"COPY DIFF FINDINGS ({len(findings)}):\n")
    for f in findings:
        print(f"[{f['severity']}] {f['page']}")
        if 'msg' in f:
            print(f"  {f['msg']}")
        if 'briefing' in f:
            print(f"  BRIEFING: {f['briefing']}")
        if 'draft' in f:
            print(f"  DRAFT:    {f['draft']}")
        print()
else:
    print("ALL COPY MATCHES — no differences found between briefing and drafts.")
PYEOF

Review the script output. Each finding shows the exact briefing text and draft text side by side. Classify findings using these rules:

Important exclusions — do NOT flag these as copy differences:

• <strong> wrapping on CTAs (this is structural markup per block conventions)
• <em> wrapping for emphasis in block markup
• Link <a href> wrapping around text
• <br> tags within paragraphs
• Bullet list formatting differences (<ul><li> vs paragraph text)
• Typographic quote substitution (' vs ') — these are rendering-equivalent

Finding	Severity
Clinical data differs (numbers, percentages, p-values)	CRITICAL
Drug name or dosing information differs	CRITICAL
Body copy text differs from briefing	CRITICAL
Heading text differs from briefing	HIGH
CTA text differs from briefing	HIGH
Table cell content differs	CRITICAL

Briefing internal inconsistencies

The briefing may contain contradictions between its own brand rules and the actual section copy. For example, a brand rule may say "use ™ on first mention per page" but the briefing's section copy for a specific page omits the ™ from the heading and places it in the body text instead.

In strict mode, the explicit section copy always takes precedence over general brand rules. The draft is correct to reproduce the section copy verbatim, even if that copy violates a brand rule stated elsewhere in the briefing.

When such contradictions are detected:

• Do NOT flag the draft as having a copy error
• Instead, flag as LOW severity with category "Briefing inconsistency" — the briefing's own copy contradicts its own brand rules
• Include both the brand rule text and the contradicting section copy in the finding, so the user can decide whether to update the briefing

Finding	Severity
Draft copy matches briefing section but contradicts briefing brand rule	LOW (briefing inconsistency)

Flexible Mode (intent-based copy)

Check that all key messages, topics, and data points from the briefing appear somewhere in the draft:

1. Extract the key topics and messages from the briefing for each page
2. For each topic, verify it appears in the corresponding draft page
3. Verify all clinical data points (numbers, percentages) are present and accurate

Finding	Severity
Clinical data missing or differs	CRITICAL
Key topic completely absent from draft	HIGH
Data point present but rephrased — acceptable	Not flagged

---

Step 6: Image Verification

Compare images by filename (the last path segment of the URL), NOT by full URL. DA reprocesses images and assigns new URLs on the published site, so full URL comparison produces false positives.

For each section where the briefing specifies an image:

1. Extract the expected image filename from the briefing (e.g., hero-home.jpeg)
2. Find <img src> and <source srcset> attributes in the corresponding draft section
3. Check that the expected filename appears in the draft's image URL path

CDN reachability check (CRITICAL):

After filename matching, verify that the CDN actually serves the images. Sample 3–5 unique image URLs from the drafts and curl -sI each one. If any return non-200, the CDN deployment is missing or incomplete — flag as CRITICAL.

# Sample image URLs and verify CDN returns HTTP 200
for url in $(grep -oh 'https://[^"]*\.jpeg' drafts/{sitename}/*.plain.html | sort -u | head -5); do
  code=$(curl -sI -o /dev/null -w '%{http_code}' "$url")
  [ "$code" != "200" ] && echo "CRITICAL: $url returns $code"
done

This catches the case where image filenames are correct in the HTML but the CDN was never deployed — the most common cause of broken images in DA.

Additional image checks across all pages:

Check	Severity
CDN image URL returns non-200 (CDN not deployed)	CRITICAL
Briefing image filename not found in draft section	HIGH
No image in a section that expects one	HIGH
Local image path (src="/..." not using CDN)	CRITICAL
about:error in any image src	CRITICAL
Alt text significantly differs from briefing	LOW
Image present but for wrong section	HIGH

---

Step 7: Metadata Comparison

Check each page's metadata block (the last section containing Title and Description):

• Strict mode: Title and Description must match the briefing exactly (after normalization)
• Flexible mode: Title and Description must contain the key terms from the briefing

Finding	Severity
Missing metadata block	MEDIUM
Title doesn't match briefing	LOW
Description doesn't match briefing	LOW

---

Step 8: Cross-Page Checks

These checks span all pages in the site:

1. Accordion consistency: The prescribing information / important safety information accordion should be identical (or near-identical) across all pages that include it. Diff the accordion content between pages and flag differences.

2. Nav link list matches briefing nav section: Compare the links in nav.plain.html against the briefing's navigation section (not the full page inventory). If the briefing explicitly lists which pages appear in main navigation, that is authoritative. Extra pages in the nav that aren't in the briefing's nav spec should be flagged as MEDIUM. Missing pages that the briefing's nav spec lists should be flagged as HIGH.

3. No local image paths: Run grep -rn 'src="/' drafts/{sitename}/ --include='*.html' — should return nothing. Any matches are CRITICAL.

4. No about:error: Run grep -rn 'about:error' drafts/{sitename}/ --include='*.html' — should return nothing. Any matches are CRITICAL.

5. Consistent CDN base URL: All image URLs should use https://{sitename}-images.pages.dev/ as the base. Flag any image using a different CDN or domain.

6. CDN reachability: Sample 3–5 unique image URLs from the drafts and curl -sI each one. If any return non-200, the CDN deployment is missing or incomplete. Flag as CRITICAL — this means every image on the site will be broken in DA/production.

7. Internal link validity: All <a href="/{sitename}/..."> links should point to pages that exist in the drafts folder.

---

Step 9: Published Content Verification (AEM drift detection)

After validating local drafts, check whether the published AEM content still matches the briefing. Content can drift after upload if someone edits directly in DA. This step is not optional — it catches changes that are invisible in the local drafts.

9a: Determine the AEM preview base URL

remote_url=$(git remote get-url origin 2>/dev/null)
owner=$(echo "$remote_url" | sed -E 's#.*/([^/]+)/[^/]+(\.git)?$#\1#')
repo=$(echo "$remote_url" | sed -E 's#.*/([^/]+)(\.git)?$#\1#')
branch=$(git branch --show-current)
echo "AEM preview: https://${branch}--${repo}--${owner}.aem.page"

9b: Fetch and check each page individually

IMPORTANT — URL pattern: The home page endpoint is /{sitename}/index.plain.html, NOT /{sitename}/.plain.html. The latter returns 404 even when the page exists.

Check each page independently. Do NOT skip all pages because one returns 404.

# Check each page individually — use index.plain.html for the home page
AEM_BASE="https://{branch}--{repo}--{owner}.aem.page/{sitename}"
for page in index luminos-data safety dosing how-treluxia-works resources nav footer; do
  code=$(curl -sI -o /dev/null -w '%{http_code}' "${AEM_BASE}/${page}.plain.html")
  echo "$code $page"
done

If a page returns 200, include it in the drift check. If it returns non-200, note it as LOW but continue checking the others. Only skip this entire step if every single page returns non-200.

9c + 9d: Run the AEM drift diff script

Run this script to compare published AEM content against both the briefing AND the local drafts. It reuses the same normalization and matching logic as Step 5 but fetches from AEM instead of reading local files. Replace {sitename} and the AEM base URL:

python3 << 'PYEOF'
import html, re, difflib, subprocess

SITENAME = "{sitename}"
AEM_BASE = "https://{branch}--{repo}--{owner}.aem.page/{sitename}"

# Pages to check: (slug, draft_filename)
PAGES = [
    ("index", "index"),
    ("luminos-data", "luminos-data"),
    ("safety", "safety"),
    ("dosing", "dosing"),
    ("how-treluxia-works", "how-treluxia-works"),
    ("resources", "resources"),
]

def normalize(text):
    text = re.sub(r'<[^>]+>', ' ', text)
    text = html.unescape(text)
    text = re.sub(r'\s+', ' ', text).strip()
    return text

def fetch_aem(slug):
    """Fetch AEM page, return None if not available."""
    r = subprocess.run(
        ['curl', '-sL', '-w', '\\n%{http_code}', f'{AEM_BASE}/{slug}.plain.html'],
        capture_output=True, text=True, timeout=15
    )
    lines = r.stdout.rsplit('\\n', 1)
    body = lines[0] if len(lines) > 1 else r.stdout
    code = lines[-1].strip() if len(lines) > 1 else '000'
    if not code.startswith('2') or 'Page not found' in body[:200]:
        return None
    return body

def extract_text_paragraphs(html_content):
    """Extract text from <p>, <h1-6>, and <div> cells, normalized."""
    paras = re.findall(r'<(?:p|h[1-6])(?:\s[^>]*)?>(.+?)</(?:p|h[1-6])>', html_content, re.DOTALL)
    cells = re.findall(r'<div>([^<]+)</div>', html_content)
    return [normalize(p) for p in paras + cells if len(normalize(p)) > 10]

# --- Read briefing ---
with open(f'sites/{SITENAME}/briefing.md') as f:
    briefing = f.read()

page_sections = re.split(r'## PAGE \d+:\s*', briefing)[1:]
page_labels = re.findall(r'## PAGE \d+:\s*(.+)', briefing)

# Build briefing text per page slug
briefing_by_slug = {}
for label, section in zip(page_labels, page_sections):
    url_match = re.search(r'\*\*URL path:\*\*\s*/\w+/(\S*)', section)
    slug = url_match.group(1) if url_match and url_match.group(1) else 'index'
    fields = re.findall(
        r'\*\*(?:Heading|Body text|Body text \(continued\)|Card heading|Card body):\*\*\s*(.+?)(?=\n\n|\n\*\*[A-Z]|\Z)',
        section, re.DOTALL
    )
    texts = []
    for f in fields:
        t = f.strip().replace('\\\n', ' ').replace('\\', '')
        t = normalize(t)
        if len(t) > 15:
            texts.append(t)
    briefing_by_slug[slug] = texts

findings = []
unreachable = 0

for slug, _ in PAGES:
    aem_html = fetch_aem(slug)
    if aem_html is None:
        unreachable += 1
        findings.append({"page": slug, "severity": "LOW", "type": "unreachable",
                         "msg": f"AEM page not reachable (not yet uploaded/previewed)"})
        continue

    aem_texts = extract_text_paragraphs(aem_html)

    # --- 9c: Compare AEM vs briefing ---
    for bt in briefing_by_slug.get(slug, []):
        best_ratio = 0
        best_aem = ""
        for at in aem_texts:
            r = difflib.SequenceMatcher(None, bt, at).ratio()
            if r > best_ratio:
                best_ratio = r
                best_aem = at
        if best_ratio >= 0.85 and best_ratio < 1.0:
            findings.append({
                "page": slug, "severity": "CRITICAL", "type": "aem-vs-briefing",
                "briefing": bt[:300], "aem": best_aem[:300], "ratio": f"{best_ratio:.3f}"
            })

    # --- 9d: Compare AEM vs local draft ---
    try:
        with open(f'drafts/{SITENAME}/{slug}.plain.html') as df:
            local_html = df.read()
        local_texts = extract_text_paragraphs(local_html)
        # Compare each local paragraph against AEM
        for lt in local_texts:
            best_ratio = 0
            best_aem = ""
            for at in aem_texts:
                r = difflib.SequenceMatcher(None, lt, at).ratio()
                if r > best_ratio:
                    best_ratio = r
                    best_aem = at
            if best_ratio >= 0.85 and best_ratio < 1.0:
                findings.append({
                    "page": slug, "severity": "HIGH", "type": "aem-vs-draft",
                    "local": lt[:300], "aem": best_aem[:300], "ratio": f"{best_ratio:.3f}"
                })
    except FileNotFoundError:
        pass

# --- Report ---
if unreachable == len(PAGES):
    print("AEM DRIFT CHECK SKIPPED — no pages reachable on AEM preview.")
else:
    real_findings = [f for f in findings if f["type"] != "unreachable"]
    if real_findings:
        print(f"AEM DRIFT FINDINGS ({len(real_findings)}):\n")
        for f in real_findings:
            print(f"[{f['severity']}] [AEM] {f['page']} ({f['type']})")
            if 'briefing' in f:
                print(f"  BRIEFING: {f['briefing']}")
            if 'local' in f:
                print(f"  LOCAL:    {f['local']}")
            if 'aem' in f:
                print(f"  AEM:      {f['aem']}")
            if 'msg' in f:
                print(f"  {f['msg']}")
            print()
    else:
        reachable = len(PAGES) - unreachable
        print(f"NO AEM DRIFT — all {reachable} reachable pages match the briefing and local drafts.")
    if unreachable > 0 and unreachable < len(PAGES):
        unreachable_pages = [f['page'] for f in findings if f['type'] == 'unreachable']
        print(f"\nNote: {unreachable} page(s) not reachable on AEM: {', '.join(unreachable_pages)}")
PYEOF

Review the script output. Each finding is pre-classified:

Finding	Severity
Published text differs from briefing (strict mode)	CRITICAL
Published clinical data differs from briefing	CRITICAL
Published content differs from local draft (text drift detected)	HIGH
Published page not reachable (not yet uploaded)	LOW

Report labelling: Prefix all findings from this step with "[AEM]" in the location field to distinguish them from local draft findings. For example: [AEM] index → Section 1 (hero-teaser) → Heading.

---

Step 10: Install Critique Overlay (one-time setup)

The interactive report requires a small overlay script in the project's scripts/delayed.js. Check if it already exists — if not, append the contents of references/critique-overlay.js to scripts/delayed.js.

The overlay activates only when ?critique-section or ?critique-target query params are present in the URL. It has zero impact on production pages.

It supports three targeting modes:

• ?critique-section=N — highlights the Nth <main> .section (1-indexed)
• ?critique-target=header — highlights the <header> element
• ?critique-target=footer — highlights the <footer> element
• ?critique-label=TEXT — optional label shown as a tag on the highlighted element

---

Step 11: Generate Interactive HTML Report

Write the report to sites/{sitename}/critique.html. Read the template from references/report-template.html and populate all {{PLACEHOLDER}} values with the actual findings data.

Template placeholders

Placeholder	Value
{{SITENAME}}	Site folder name (e.g., zenturis)
{{DRUG_BRAND}}	Brand name from briefing (e.g., Zenturis)
{{DRUG_GENERIC}}	Generic name from briefing (e.g., zenturigliptin)
{{BRIEFING_PATH}}	Relative path to briefing (e.g., sites/zenturis/briefing.docx)
{{DATE}}	Current date
{{COPY_FIDELITY}}, {{BLOCKS_FIDELITY}}, {{IMAGES_FIDELITY}}	Strict or Flexible
{{COPY_EVIDENCE}}, {{BLOCKS_EVIDENCE}}, {{IMAGES_EVIDENCE}}	Quote from briefing that determined the fidelity level
{{CRITICAL_COUNT}}, {{HIGH_COUNT}}, {{MEDIUM_COUNT}}, {{LOW_COUNT}}	Integer counts
{{VERDICT_CLASS}}	pass, needs-fixes, or blocked
{{VERDICT_TEXT}}	Verdict text with summary
{{AEM_PREVIEW_URL}}	AEM preview base URL (e.g., https://main--az-sitebuilder--paolomoz.aem.page) or "N/A" if not available

Fidelity badge classes

Set the .value div class based on the detected fidelity level:

• badge-strict (red) for strict dimensions
• badge-flexible (green) for flexible dimensions

Findings markup

Each finding is a clickable <div class="finding"> with data attributes for preview targeting:

<div class="finding" data-page="PAGE" data-section="N" data-label="SHORT LABEL">
  <div class="location">PAGE &rarr; Section N (BLOCK)</div>
  <div class="description">DESCRIPTION</div>
  <div class="diff">
    <div>
      <div class="diff-label">Expected</div>
      <div class="diff-expected">BRIEFING TEXT</div>
    </div>
    <div>
      <div class="diff-label">Actual</div>
      <div class="diff-actual">DRAFT TEXT</div>
    </div>
  </div>
  <div class="fix">FIX SUGGESTION</div>
  <div class="view-hint">Click to view in preview &rarr;</div>
</div>

Preview targeting rules:

• For content section findings: data-page="pageslug" + data-section="N" (1-indexed)
• For nav findings: data-page="index" + data-target="header" (shows nav in context of home page)
• For footer findings: data-page="index" + data-target="footer" (shows footer in context of home page)
• The diff block is optional — include it when there's a concrete expected vs actual comparison

Page status table

Each <tr> has data-page="pageslug" to make the row clickable. Use these classes:

• class="match" (green) for passing counts
• class="mismatch" (orange) for failing counts
• Status cell: class="status-pass" / class="status-warn" / class="status-fail"

Cross-page checklist

Each <li> uses one of: class="check-pass", class="check-warn", class="check-fail"

Report layout behaviour

The report starts full-width (centered, comfortable reading). When the user clicks any finding card or page table row, the report panel animates to 440px on the left and the preview iframe slides in from the right, loading the relevant page from http://localhost:3000 with the critique overlay highlighting the affected section. A close button collapses the preview back to full-width.

Verdict criteria

Verdict	Class	Condition
PASS	pass	Zero CRITICAL and zero HIGH
NEEDS FIXES	needs-fixes	Zero CRITICAL, but HIGH or MEDIUM exist
BLOCKED	blocked	One or more CRITICAL

Severity criteria summary

Severity	Criteria
CRITICAL	Copy text differs from briefing (strict mode); clinical data wrong; missing page; local image path; about:error; published AEM content differs from briefing (strict mode)
HIGH	Missing image; wrong image filename; missing content section; wrong link target; key topic missing (flexible mode); published content drifted from local drafts
MEDIUM	Wrong block type (strict mode); wrong section-metadata style; wrong link text; missing metadata
LOW	Extra file not in briefing; metadata mismatch; alt text differs; block type could be better (flexible mode); published page not reachable

After writing the file, open it in the browser and tell the user the path. Remind them the preview iframe requires the dev server running at localhost:3000.

---

Troubleshooting

Problem	Cause	Fix
Too many CRITICAL copy findings	Briefing has HTML entities, drafts have decoded characters	Ensure normalization in Step 5 decodes all HTML entities before comparison
False positives on <strong> text	CTA text wrapped in <strong> per block conventions	Step 5 explicitly excludes structural markup wrapping from copy diffs
Image comparison flags every image	Comparing full URLs instead of filenames	Step 6 specifies filename-only comparison (last path segment)
Briefing is .docx and unreadable	Binary Word document	Extract text using available tools, or ask user to provide a text/markdown version
Accordion diffs across pages	Pages were generated independently	Flag in Step 8 cross-page checks; provide the specific diff
Entity encoding differences (&ge; vs ≥)	Briefing uses HTML entities, draft uses Unicode	Normalization handles this — decode entities in both sources before comparing
Table cell ordering differs	Table rows or columns reordered in draft	Compare cell content regardless of position within the same table; flag if data is missing entirely
Published content check flags every image URL	DA rewrites image URLs to ./media_xxx paths during upload	Step 9c excludes image src/srcset from text comparison — only compare text content
Published content returns 404 for home page only	Used /.plain.html instead of /index.plain.html	The home page endpoint is /{sitename}/index.plain.html — see Step 9b URL pattern note
Published content returns 404 for all pages	Site not yet uploaded/previewed on AEM	Step 9 skips the published check and notes it in the report
Published content differs from local draft but matches briefing	Someone fixed an error directly in DA	Flag as HIGH (draft-to-published drift) so local drafts can be re-synced
False positives from DA whitespace changes	DA normalizes whitespace differently	Apply aggressive whitespace normalization (collapse all runs, trim) before comparing

Cross-References

• eds-website-builder: The skill that generates the drafts this skill audits
• generative-page-pipeline: Alternative page generation pipeline whose output can also be critiqued
• site-auditor: Broader site-level audit (content gaps, metadata) — complementary to briefing-level fidelity checking
• accessibility-auditor: Can be run after briefing critique to verify generated pages meet WCAG standards