← Vault Index
Source: frameworks/kit-slo-page-production/04-slo-page-production-quality.md

04 — QUALITY: SLO Page Production Cascade

Pass threshold: 92 / 102 When to run: After every cascade run (Mode 1) or QC-only run (Mode 3). Run against the page, the cascade process, AND the SFB audit findings.

Blocking failures: Any item marked BLOCKING below fails the entire cascade regardless of total score. A page with 100/102 but one blocking failure does not ship.


SFB Audit (15 points) — HARD GATE

The SFB audit runs BEFORE the build. These checks come from the SFB 6-layer framework and catch architectural issues — missing components, missing videos, incomplete compliance — at the funnel level before you waste time building a page that sits inside a broken funnel.

#CheckPointsBlocking
1SFB component mapping is explicit — the page maps to one of the 8 SFB components2YES
2Compliance footer present on ALL existing funnel pages (5 links each) — SFB Layer 2 checkpoint. Count the links. Not 4. Not 3. All 5: Privacy, Terms, Disclaimer, Returns/Refunds, Contact. If ANY existing page in the funnel is missing a compliance link, fix it BEFORE building the new page.3YES
3For OTO pages: OTO video present (60-90s, Hook/Reframe/Offer/Risk/CTA formula) — SFB Layer 4 checkpoint. Without video, take rate collapses to 0-2%. Ben's OTO3 at 0% until video filmed.3YES
4For OTO pages: OTOs ascend in price + commitment (OTO1 < OTO2 <= OTO3)2YES
5For sales pages: VSL/PASPA is 3-7 minutes (NOT 15 min — decision fatigue on low-ticket)2YES (sales pages)
6For sales pages: Risk reversal visible above the fold (even $7 needs refund policy — Stripe + Meta)2YES
7Audit findings documented — every red/yellow layer has a fix assigned to a specific SFB component + build mode1NO

SFB Failure Mode #8 (compliance footer) and Failure Mode #1 (OTO videos) are the two most critical page-level checks. Both are BLOCKING. Both have documented real-world consequences: CPMs spike 2-3x without compliance footer; take rate drops to 0% without OTO video.


Meta Pixel (15 points) — HARD GATE

Every item in this section is a blocking failure. A page without correct pixel tracking ships broken attribution and wastes ad spend.

#CheckPointsBlocking
8Meta Pixel base code is present in (not , not footer, not missing)3YES
9Pixel ID in the code matches the confirmed Pixel ID from the brief (numeric, 15-16 digits)3YES
10fbq('init', '[PIXEL_ID]') is present with the correct ID2YES
11fbq('track', 'PageView') is present2YES
12Correct conversion event for page type: Lead on thank-you-optin, Purchase (with value + currency) on thank-you-purchase, no conversion event on other types3YES
13For Purchase events: value parameter matches actual product price, currency is 'USD'1YES (when applicable)
141NO

What "correct conversion event for page type" means:

Page TypeRequired Events
opt-inPageView only
thank-you-optinPageView + Lead
thank-you-purchasePageView + Purchase (value + currency)
offer-purchasePageView only
offer-bookingPageView only
deliveryPageView only
homepagePageView only
skill-deliveryPageView only
oto-pagePageView only (OTO conversion tracked via SamCart, not page pixel)

A Lead event on an opt-in page (instead of the thank-you-optin page) fires on page load, not on form submit — inflating lead counts. A Purchase event without a value parameter breaks ROAS reporting. Both have happened.


Compliance (15 points) — HARD GATE

Missing compliance links expose the business to policy violations, legal risk, and Meta CPM spikes. Every item marked BLOCKING stops the page. This section enforces SFB Component 7.

#CheckPointsBlocking
15Footer contains Privacy Policy link2YES
16Footer contains Terms of Service link2YES
17Footer contains Disclaimer link2YES
18Footer contains Returns & Refunds link2YES
19Footer contains Contact link2YES
20All 5 compliance links present (not 4, not 3 — all 5) — COUNT THEM1YES
21Meta disclaimer present on pages in paid funnels2YES (when in paid funnel)
22Anthropic disclaimer present when AI tools are referenced1YES (when applicable)
23Earnings disclaimer present when financial outcomes are implied1YES (when applicable)
24Copyright line includes correct entity name0NO

The compliance footer is 5 links. Always. On every page: sales page, checkout, all OTO pages, post-purchase confirmation, email footer. SFB Component 7. SFB Failure Mode #8: "Skipping compliance footer — Meta CPMs spike 2-3x." This is not a suggestion. This is a blocking gate.


Terminology (10 points) — HARD GATE

Terminology violations in paid context create Meta policy risk. Items marked BLOCKING stop the page when the page is in a paid funnel.

#CheckPointsBlocking
25Zero instances of "AI assistant" on any customer-facing page2YES
26Zero instances of LLM brand names (Claude, ChatGPT, Gemini) on pages in paid funnels3YES (paid context)
27"AI tool of choice" or equivalent neutral phrasing used where AI is referenced2NO
28Zero instances of old pricing (prices that have changed since the brief)1YES
29Zero instances of old or broken URLs2YES

Copy QC (10 points)

The 11-pattern AI detection check from business-aos/reference/brand/copy-qc.md. This is a quality gate, not a style guide — every pattern here has been caught in actual Advisory OS drafts.

#CheckPointsBlocking
30Zero P1 violations: no twinning, no mirror reversals, no question-revelation arcs4YES
31Zero P2 violations without documented exception: no three-beat parallels (unless data pattern), no "Not because X. Because Y.", no formulaic setups (max 1 with evidence), no trying-to-be-quotable lines3NO
32Maximum one P3 violation: dramatic beats (max 1), no rhetorical hand-holding, no 3+ identical openers1NO
33Compound check passes: no correction-revelation family compounds (2+ from Patterns 1/3/4/7), sentence length varies, not every insight structured as correction1NO
34Read-aloud test: every line reads at conversation speed, no presentation-voice lines1NO

Sentence Editor (5 points)

The 8-rule sentence quality pass. Applied to new copy written for this page (not to copy pulled verbatim from approved sources).

#CheckPointsBlocking
35Sentence length varies (no metronomic rhythm)1NO
36No filler words in CTA or headline context (just, really, very, actually)1NO
37Active voice preferred (passive voice flagged and justified or rewritten)1NO
38Specific over vague, concrete nouns over abstract1NO
39Every sentence earns its place (no padding, no filler paragraphs)1NO

Mobile / Responsive (12 points) — PARTIAL HARD GATE

#CheckPointsBlocking
40Three breakpoints present minimum: 1024px, 768px, 480px2YES
41Class selectors used for responsive rules (no attribute selectors like div[style*="..."])2YES
42No var() CSS — all colors hardcoded as hex values (Convertri requirement)2YES
43Header stacks centered on mobile (968px breakpoint)2NO
44On pages with forms: form visible within one scroll on mobile (CSS order: -1 if needed)2YES (when form present)
45No horizontal overflow on any breakpoint2NO

Link Verification (10 points)

#CheckPointsBlocking
46Every CTA button links to the correct destination URL2YES
47All compliance footer links are present and not 4042YES
48Logo links to correct homepage URL1NO
49All internal page references match Convertri slugs1YES
50No placeholder URLs remain (no #, no about:blank, no example.com)2YES
51For thank-you pages: every dollar amount visible on the page matches a confirmed price from the brief or is dynamically populated from URL parameters. No hardcoded prices from previous funnels.2YES

Visual Verification (10 points) — MANUAL GATE

These checks require human verification. The cascade cannot automate them. They must be confirmed by a team member before the page ships.

#CheckPointsBlocking
52Page renders completely on desktop (no missing sections, no broken layouts)2YES
53Page renders completely on mobile (no missing sections, no broken layouts)2YES
54Colors match the specified brand system (AOS or CYP)2NO
55Typography renders correctly (correct fonts loaded, no fallback fonts visible)2NO
56Tested in Facebook in-app browser on mobile (this is where ad traffic lands)2YES (paid funnel pages)

Manual gate protocol: When the cascade reaches visual verification, it stops and presents the findings from all automated gates. The page is opened for visual inspection. The human confirms each check. Only after confirmation does the cascade produce the final QC report.


Scoring Summary

CategoryPointsBlocking Items
SFB Audit156
Meta Pixel156
Compliance158
Terminology104
Copy QC101
Sentence Editor50
Mobile / Responsive124
Link Verification105
Visual Verification103
Total10237

Pass criteria:

A page that scores 97 but has one blocking failure does not ship.


Common Failure Modes

FailureSFB ReferenceWhat HappensHow to FixHow Often
Compliance footer missing or incompleteSFB Failure Mode #8, Component 74 of 5 links present. Returns & Refunds or Contact dropped. Meta CPMs spike 2-3x.COUNT the links. There must be exactly 5: Privacy, Terms, Disclaimer, Returns & Refunds, Contact. Do not eyeball — count. Apply to EVERY page: sales page, checkout, all OTO pages, confirmation, email footer.Common — happens when footer is copied from a page that was already missing one
OTO page without videoSFB Failure Mode #1, Component 6Take rate collapses to 0-2%. Ben's own OTO3 sat at 0% for 10 days. Single biggest revenue leak.Film 60-90s video per OTO. Webcam-over-slides (Loom). One take. 30-60 min total for all OTOs. The 90 seconds of recording is the highest-leverage minute in the funnel build.Has happened — Ben's own funnel
Pixel on wrong page typeCampaign playbookLead event fires on opt-in page instead of thank-you-optin. Every page load counts as a "lead," inflating metrics.Check the page type table. Lead goes on thank-you-optin. Purchase goes on thank-you-purchase. The page where the action happens is NOT where the event fires — the NEXT page is.Common — Cole flagged this on 3 pages in one funnel
Missing pixel entirelyCampaign playbookNo tracking data. Attribution broken. Ad spend wasted.SFB audit Layer 2 catches this before the build. The pre-build gate catches it during the build. Two chances to catch it. Zero excuses for shipping without it.Has happened
Pixel ID from wrong accountCampaign playbookPage has A pixel, but it's the wrong pixel. Events fire to a pixel nobody is watching.Verify the numeric ID against Meta Business Manager. Do not assume the ID is correct because "we always use the same one."Has happened
Purchase event without valueCampaign playbookfbq('track', 'Purchase') fires but without {value: X, currency: 'USD'}. ROAS reporting shows conversions but no revenue.The Purchase event MUST include value and currency: fbq('track', 'Purchase', {value: 297.00, currency: 'USD'})Has happened
OTOs not ascending in priceSFB Failure Mode #9OTO1 priced higher than OTO2. Broken stack. Buyer psychology breaks.OTO1 < OTO2 <= OTO3. Each ascends in price + commitment. Strategy phase catches this before build.SFB documented
Sales page VSL too longSFB Failure Mode #615-min VSL on a $7 product. Decision fatigue kills CVR.3-7 min for low-ticket. Match VSL length to price point.SFB documented
No risk reversalSFB Failure Mode #5Even $7 needs a refund policy. Stripe compliance issue + CVR drop.Risk reversal visible above the fold. "30-day money-back guarantee."SFB documented
Attribute selectors in responsive CSSCampaign playbookPage looks fine in Chrome DevTools. Breaks in Facebook in-app browser.Use class selectors only. No div[style*="..."]. Test in actual Facebook in-app browser.Happened on The Build launch
LLM brand name in paid pageTerminology rules"Built with Claude" on a paid funnel page. Meta policy violation risk.Run terminology sweep. Grep for Claude, ChatGPT, Gemini, AI assistant. Replace with "AI tool of choice."Recurring
Placeholder URLs in productionLink verificationCTA button links to # or about:blank. Dead button in production.Link verification gate catches this — but only if the gate runs.Has happened
var() CSS in ConvertriResponsive rulesColors render locally. Disappear in Convertri (doesn't process CSS custom properties).Hardcode every color as hex. Search for var( before shipping.Recurring

Change Log

2026-05-24 — Consensus review fixes (Arden, Cole, Reid, Cade). Check #5 (VSL/PASPA 3-7 min) changed from non-blocking to BLOCKING for sales pages — SFB says "3-7 minutes ONLY"; a 15-min VSL on a $7 product is an architectural violation. Check #47 (compliance footer links not 404) changed from non-blocking to BLOCKING — a compliance link that 404s is worse than a missing one. Added check #51: displayed dollar amounts on thank-you pages must match confirmed prices from the brief or use dynamic URL parameters (BLOCKING). Visual Verification renumbered to #52-#56. Scoring summary updated: 102 points, 37 blocking items, pass threshold 92/102.

Rebuilt with SFB Low-Ticket Funnel System as foundation. Source: f07-lowticket-00-master.md (8 components, 10 failure modes), f07-lowticket-01-audit-skill.md (6 audit layers), f07-lowticket-03-build-skill.md (6 build modes, compliance footer Mode 6). Added SFB Audit section (15 points, 5 blocking items). Compliance footer verification now enforced as BLOCKING gate per SFB Component 7 and Failure Mode #8. OTO video check added as BLOCKING gate per SFB Component 6 and Failure Mode #1. Previous source: campaign launch playbook, campaign-production-workflow.md.