01 — CONTEXT: SLO Page Production Cascade

Input definitions, validation rules, SFB component inventory, 6-layer audit framework, and what each mode requires.

SFB Foundation — The 8 Components

Every funnel is made of these 8 components (from the SFB Digital Low-Ticket Funnel master reference, Funnel 07). The audit phase checks each one before any build work begins.

SFB Foundation — The 6 Audit Layers

Before building, audit the existing funnel state against these 6 layers. First red layer = the bottleneck. Fix that before anything else.

Layer 2 checkpoint "Compliance footer present (5 links)?" is a BLOCKING gate. If this fails in the audit, it becomes the first fix in the strategy phase — no other build work proceeds until the compliance footer is confirmed for every page in the funnel.

Mode 1 Inputs — Run Cascade

Conditional Inputs (Based on Page Type and SFB Component)

Validation Rules — Mode 1

1. Every input marked Required must be present before building. No building with gaps. A page built without a confirmed Pixel ID ships without tracking. A page built without a confirmed slug ships with broken links. Both have happened.
2. Pixel ID must be numeric, 15-16 digits. If someone pastes a pixel name or a Business Manager ID, stop — that's the wrong value.
3. Page type must be one of the defined types. If the brief describes a page that doesn't match a type, clarify before building. The page type determines which pixel events fire, and wrong events break attribution.
4. CTA destination URL must be a live, working URL. Do not build with placeholder URLs. If the checkout page or Calendly link doesn't exist yet, that blocks the build.
5. Convertri slug must match what's configured in Convertri. The page references its own slug in links and meta tags. A mismatch means broken links post-deploy.
6. Compliance entity name must match the legal entity. Not a brand name, not an abbreviation. This appears in the copyright line and disclaimer text.
7. SFB component mapping must be explicit. Every page maps to one of the 8 SFB components. If the mapping is unclear, clarify before building. The component determines which audit-layer checks apply.

Mode 2 Inputs — Improve This Kit

Validation Rules — Mode 2

1. Always read the current kit files before making changes. Understand what's there first.
2. Changes propagate. If you add a new gate to the quality checklist, add the corresponding step to the output skill cascade.
3. Never remove a quality check without a reason. Quality checks accumulate — they represent pages that shipped broken.
4. Document what changed and why. Add to the Change Log section at the bottom of the updated file.

Mode 3 Inputs — QC-Only

Validation Rules — Mode 3

1. All inputs from Mode 1 that affect QC gates must be provided. You can't check pixel events without knowing the page type. You can't check links without knowing the slug.
2. QC-Only still runs the SFB audit. The audit layers apply even to existing pages. A page might pass all build gates but fail the SFB architecture check (e.g., OTO page without a video, sales page with 15-min VSL).
3. QC-Only does not fix — it reports. The output is a gate-by-gate pass/fail report with SFB audit findings. Fixes are a separate step.

Pre-Build Validation Gate

Before calling the page-type kit to build, every input must pass this gate. Any failure blocks the build.

If any check fails, stop. Ask for the missing input. Do not proceed with assumptions.

Input Priority Hierarchy

When inputs conflict or are ambiguous:

1. The SFB master reference wins for funnel architecture, component requirements, and benchmark KPIs
2. The page brief wins for page type, content, and positioning
3. The campaign launch playbook wins for pixel events, compliance requirements, and QC gates
4. The page-type kit wins for HTML structure, design system, and section architecture
5. Existing vault conventions win for file naming, directory structure, and terminology
6. Kathryn's direct instruction wins over everything else

Reference Files (Loaded During Cascade)

These files are read during the cascade, not before. Listed here for inventory — the output skill specifies when each is loaded.