00 — START HERE: SLO Page Production Cascade

This is the setup and orientation document for the SLO Page Production Cascade kit. Read this to understand what it is, what it does, what files it needs, and how to use it.

What This Is

The SLO Page Production Cascade takes a page brief and runs every production step as an enforced sequence. Brief goes in, every gate runs, page doesn't ship until everything passes. This kit exists because pages keep shipping without pixels, without compliance links, without proper tracking values — and catching those failures after deployment costs more than preventing them during production.

Foundation: the SFB Low-Ticket Funnel System. This kit is built on the 8-component funnel architecture from the Digital Low-Ticket Funnel (Funnel 07, Pipeline Volume Engine). The SFB system defines what a complete funnel looks like — 8 components, 6 audit layers, 10 documented failure modes, specific benchmarks per component. This kit enforces that architecture at the page level.

The cascade runs in three phases: AUDIT, STRATEGY, BUILD. Before building anything, the cascade audits the existing funnel state against the SFB 6-layer framework. Which components exist? Which are missing? Which have gaps (missing pixel, missing compliance links, missing OTO videos)? The audit catches problems BEFORE the build, not after. The strategy phase maps each gap to a specific component and build mode. The build phase builds/fixes each component with all QC gates enforced.

Audience: Internal team (Kathryn, Cole, Claude) Format: Markdown (this kit is a production process, not an HTML deliverable — the HTML comes from the page-type kits it coordinates) Lifecycle: Runs once per page. Every page, every time.

The Three-Phase Cascade (SFB Foundation)

PHASE 1 — AUDIT
   Audit existing funnel state against SFB 6-layer framework
   Which of the 8 components exist? Which are missing? Which have gaps?
   Layer 2 checkpoint: "Compliance footer present (5 links)?" = BLOCKING
   Output: component-by-component status (green/yellow/red per layer)

       |
       v

PHASE 2 — STRATEGY
   Map each gap to a specific SFB component + build mode
   Determine build order (compliance footer + pixel first — they block everything)
   Set acceptance criteria per component from SFB benchmarks
   Output: prioritized build plan with specific modes

       |
       v

PHASE 3 — BUILD
   Build/fix each component with all QC gates enforced
   Every page gets: pixel, compliance footer, terminology sweep,
   copy QC, responsive check, link verification
   Page ships only after all gates pass
   Output: ship-ready page + QC report

The key insight: The SFB system is the ARCHITECTURE (what a complete funnel looks like, what's required at each layer). The campaign launch playbook is the EXECUTION (how to build each page correctly). This kit combines both: audit against the architecture, then build against the execution playbook, with QC gates at every step.

How It Relates to Other Page Kits

This kit does not build pages. The page-type kits build pages:

• kit-offer-page — purchase and booking pages
• kit-opt-in-page — lead capture pages
• kit-thank-you-page — post-action confirmation pages
• kit-delivery-page — asset delivery pages
• kit-homepage — homepage
• kit-skill-delivery-page — skill download pages

This kit wraps around those kits. It enforces the production cascade that every page must pass through regardless of type. The page-type kit produces the HTML. This kit ensures the HTML has the right pixel, the right events, the right compliance footer, the right terminology, clean copy, working links, and verified responsive behavior before it ships.

Page Brief
    |
    v
PHASE 1 — AUDIT (SFB 6-layer framework)
    |  What exists? What's missing? What has gaps?
    |  Compliance footer present? Pixel present? OTO videos present?
    v
PHASE 2 — STRATEGY (SFB component mapping)
    |  Which components need building? Which need fixing?
    |  What build mode for each? What order?
    v
PHASE 3 — BUILD (Page-type kits + QC gates)
    |--> Calls the appropriate page-type kit to build HTML
    |--> Runs every gate in sequence
    |--> Page ships only after all gates pass

Operating Modes

Mode 1 — Run Cascade

The primary mode. You provide a page brief (see file 01 for required inputs). The cascade:

1. AUDIT — Audits the existing funnel state against the SFB 6-layer framework. Identifies which components exist, which are missing, which have gaps. Flags blocking issues (missing compliance footer, missing pixel, missing OTO videos) before any build work begins. This is where the problems Cole flagged — missing pixels, missing compliance links, hardcoded tracking values — get caught.
2. STRATEGY — Maps each audit finding to a specific SFB component and build mode. Determines build order. Sets acceptance criteria from SFB benchmarks (bump take rate 30%+, OTO1 take rate 10%+, compliance footer = 5 links, etc.).
3. BUILD — Identifies the page type and required pixel events, calls the appropriate page-type kit to build the HTML, runs every gate in sequence (pixel, compliance, terminology, copy QC, sentence editor, responsive, links, visual check), produces a QC report with specific accounting per gate. Ships only after all gates pass.

Before starting: Confirm understanding of the brief. "Here's what I'm going to build, here's what page type this is, here's what pixel events this page needs, and here's what the audit found. Does this match your intent, or am I missing something?"

Mode 2 — Improve This Kit

The self-improvement loop. After running this kit:

1. Did I change anything in the output by hand? --> Update golden example + output skill
2. Did QC miss something I caught? --> Update quality checklist + add to common failure modes
3. Should the kit do something it doesn't? --> Update output skill

The rule: Every manual fix should become a kit fix. If you fixed it by hand, tell the kit builder to fix the kit so you never fix it by hand again.

Mode 3 — QC-Only

For pages built outside this cascade (legacy pages, pages built before this kit existed, pages from team members who built without the cascade). Runs the full SFB audit first (what's the funnel state?), then runs every build gate against the existing HTML and produces a pass/fail report. Does not rebuild — only validates.

What This Does NOT Do

1. Does not build the HTML itself. The page-type kits build pages. This kit enforces production quality around those builds.
2. Does not handle email sequences, ad creative, or non-page assets. Those have their own production paths. This kit is pages only.
3. Does not manage campaign-level coordination. The campaign launch playbook handles phase sequencing across asset types. This kit handles the production cascade for a single page.
4. Does not replace page-type kit QC checklists. If kit-offer-page has a 42-item quality checklist, that still runs as part of the page build. This kit adds the cross-cutting gates (pixel, compliance, terminology, copy QC) that apply to every page regardless of type.
5. Does not approve pages for launch. Kathryn is the final approval. This kit ensures every gate passes before the page reaches her — she is the approval gate, not the QC pass.

The Self-Improvement Loop

Run cascade --> AUDIT --> STRATEGY --> BUILD --> QC the page
    |
    v
QC passes --> Ship it. Done.
    |
    v
QC fails OR manual change needed --> Mode 2
    |
    v
Update quality checklist (if QC missed something)
Update output skill (if process needs to change)
Update terminology (if new forbidden terms discovered)
    |
    v
Next run catches it automatically.

After every cascade run, ask:

1. Did I change anything in the output by hand? --> If yes, Mode 2.
2. Did QC miss something I caught? --> If yes, Mode 2.
3. Is there something the kit should do that it doesn't? --> If yes, Mode 2.

If the answer to all three is no, the kit is working. Move on.

File Inventory

Total: 6 files.

Relationship to Other Kits and Systems

The SFB Failure Modes This Kit Prevents

The SFB master reference documents 10 failure modes. Several are directly relevant to page production:

The compliance footer is the most critical page-level gate. SFB Component 7 documents the 5-link pattern. SFB Failure Mode #8 documents the consequence of skipping it (Meta CPMs spike 2-3x). This kit makes that failure impossible to repeat.

Notion Product Delivery (Cross-Reference)

This kit covers HTML page QC. If the product is delivered via Notion (skills, SOPs, templates), there's a separate set of delivery QC steps:

• Page architecture: container → database → homepage → individual pages
• Sharing/permissions: buyers see browse pages, not raw databases
• Duplication settings: "Allow duplicating as template" on buyer-facing pages only
• Incognito testing: confirm Duplicate button works and sub-pages are included

Reference: Product Pages — Duplication Checklist (Notion) — includes the full checklist, architecture pattern, and reusable template for future products.

Infrastructure Roadmap

Future improvements — not blocking the kit from being used now, but tracked for when they matter.

File Location

advisory-os-vault/content/frameworks/kit-slo-page-production/
    00-slo-page-production-start-here.md          (this file)
    01-slo-page-production-context.md
    02-slo-page-production-terminology.md
    03-slo-page-production-golden-example.md
    04-slo-page-production-quality.md
    05-slo-page-production-output-skill.md