Item 16: landing migration to the shuffle2 reference (dark base, gradient H1, 3-col mistakes, relocated sections)

.okf/build/test-gates.md

@@ -4,7 +4,7 @@ title: Test gates and when they block commits
 description: bin/qtest --changed is the routine gate; bin/rake test:critical at milestones; bin/test AND bin/dtest once at PR prep (or on explicit confirmation) for themes/, layouts/, or CSS changes.
 tags: [testing, visual-regression, gates]
 status: stable
-generated: { by: claude/fable-5, at: 2026-08-01T18:00:00Z }
+generated: { by: claude/opus-4-8, at: 2026-08-12T20:20:00Z }
 verified: { by: claude/fable-5, at: 2026-08-01T11:30:00Z }
 ---
 
@@ -179,3 +179,12 @@ extend it when adding components or critical files. The macOS full suite remains
   the repo - fresh clones had a hooksPath pointing at nothing. Adding any
   root dotfile/dot-dir? Check `git check-ignore -v <path>` before assuming
   it's tracked.
+- REPORT-ONLY build gates (each flips to blocking once its backlog hits
+  zero via an env flag): `bin/check-svg-floor` (`SVG_FLOOR_BLOCK=1`)
+  catches course SVGs whose smallest text renders <9px@390;
+  `bin/check-course-paths` (`COURSE_PATH_BLOCK=1`) catches lesson
+  `Next:`/branch drift vs `data/course_sequence.yaml`. Both are standalone
+  (NOT yet wired into hugo-build/CI), carry a `--self-test`, and print a
+  burn-down list + exit 0 until their env flag is set. (A landing-parity
+  variant was tried and dropped as redundant - YAGNI: a report-only gate
+  nobody wires in earns its keep only when it guards an active backlog.)

.okf/log.md

@@ -1,5 +1,21 @@
 # Bundle Update Log
 
+## 2026-08-12 (item16 landing migration) - below-fold coverage gap confirmed
+
+* **Update**: `.okf/build/test-gates.md` documents the REPORT-ONLY build-gate
+  pair (`bin/check-svg-floor`, `bin/check-course-paths`) - standalone, each
+  with a `--self-test`, flipping to blocking via an env flag once its backlog
+  is zero.
+* **Coverage-gap confirmed from both sides**: item16's below-fold changes
+  (dark NOT-cover band, merged endcap, compacted module cards) produced
+  ZERO Linux dtest reds - only the hero-fold desktop/course/landing baseline
+  shifted (T2/T4). Below-fold visual work is gated by rendered chrome-devtools
+  review at 1280+390, never by the pixel suite.
+* **Dropped**: a `bin/check-landing-parity` report-only gate was tried as the
+  wave's 20%-slot and removed as redundant (Paul, YAGNI) - a report-only
+  gate nobody wires into hugo-build/CI doesn't earn its keep unless it guards
+  an active backlog the way svg-floor/course-paths do.
+
 ## 2026-08-09 (CEO decisions) - delivery goes dual-route, client picture corrected
 
 * **Update**: no concept file changed - this is a business-layer decision, and the

content/course/tech-for-non-technical-founders-2026/_index.md

@@ -43,23 +43,7 @@ The first checkpoint comes fast: two to three weeks in, at an evenings-and-weeke
 
 Two ways in: [Start Lesson 1.1 →](/course/tech-for-non-technical-founders-2026/form-your-founding-hypothesis-90-minute-sprint/) or [see the full syllabus ↓](#module-map). *Prefer a map first? [How This Course Works](/course/tech-for-non-technical-founders-2026/how-this-course-works/) (10 minutes) and the [FAQ](/course/tech-for-non-technical-founders-2026/faq/) cover the route and the most common blockers.*
 
-## Take this course if
-
-- You are a first-time founder with an idea
-- You want the fastest route from that idea to your first paying customer
-- You can read a [Stripe](https://stripe.com) invoice but not a GitHub commit
-- You have never systematically validated a business before
-- You might have tinkered with no-code tools, but you want a structured path instead of guessing
-
-Skip this course if you want to learn to code or hand off founder judgment to someone else. And if what you need most is cohort deadlines and peers, [YC Startup School](https://www.startupschool.org/) runs free - this course is the self-paced, artifact-first alternative.
-
-Already building, or paying someone to build for you? Start at the [ownership audit in Lesson 4.2](/course/tech-for-non-technical-founders-2026/github-aws-database-ownership-checklist/) - the [side-path below](#already-started-building) explains the fork.
-
-## Who built this
-
-Built by [JetThoughts](https://jetthoughts.com). We've run a Rails-first dev shop since 2011, and we have sat on the receiving end of enough first builds gone wrong to know which mistakes repeat: a 15-page wishlist spec where a one-page brief should have been, or a GitHub account registered to a contractor who stopped replying. This course is the desk reference we wish those founders had before their first build decision.
-
-Why free? A founder who validates before building makes a better future client than one we meet mid-disaster, and there is nothing to buy inside the course.
+Already building, or paying someone to build for you? Start at the [ownership audit in Lesson 4.2](/course/tech-for-non-technical-founders-2026/github-aws-database-ownership-checklist/) - the [Already started building? side-path](/course/tech-for-non-technical-founders-2026/how-this-course-works/#already-started-building) explains the fork.
 
 ## Why this course exists
 
@@ -74,33 +58,6 @@ The five mistakes below sink more first products than bad code does - we have wa
   <li class="mistake-list__cta">Each mistake maps to a module - <a href="#module-map">jump to the module map ↓</a></li>
 </ul>
 
-## What this course does NOT cover
-
-To save your time, here is what we intentionally exclude - none of it is needed for the promised result (idea → first paying customer):
-
-<div class="scope-grid">
-  <div class="scope-card">
-    <h3 class="scope-card__title">How to code</h3>
-    <p>The course assumes zero coding ability - <a href="https://lovable.dev">Lovable</a> + <a href="https://supabase.com">Supabase</a> + <a href="https://stripe.com">Stripe</a> handle the technical side.</p>
-  </div>
-  <div class="scope-card">
-    <h3 class="scope-card__title">Hiring &amp; managing a team</h3>
-    <p>Covered as a build-path decision in Lesson 4.1, not as org design; early-stage management lives in the <a href="/course/tech-for-non-technical-founders-2026/friday-demo-rule-founder-progress/">Friday Demo Rule</a> + <a href="/course/tech-for-non-technical-founders-2026/weekly-dev-report-template-founders/">Weekly Dev Report</a>.</p>
-  </div>
-  <div class="scope-card">
-    <h3 class="scope-card__title">Raising venture capital</h3>
-    <p>The course produces the artifacts investors want to see. It does not teach pitch decks or fundraising mechanics.</p>
-  </div>
-  <div class="scope-card">
-    <h3 class="scope-card__title">Acquisition at scale</h3>
-    <p>Module 5 covers your first customers; SEO, content marketing, and paid acquisition at scale are a separate discipline.</p>
-  </div>
-</div>
-
-<p class="scope-residual">Also out of scope: mobile-only and marketplace-only specifics (they have their own playbooks), and legal incorporation, taxes, and IP filings - use a lawyer or a service like <a href="https://stripe.com/atlas">Stripe Atlas</a>, <a href="https://www.clerky.com/">Clerky</a>, or <a href="https://www.firstbase.io/">Firstbase</a>. If you need something on this list, the course won't help with it.</p>
-
-<div class="course-band course-band--gray">
-
 ## Module map
 
 Read the modules in order - each module's output is the next module's input, and each card's **"You leave with"** line names its output. The artifacts bundle into a single Google Drive folder - your **Founder OS** ([printable pack index](/course/tech-for-non-technical-founders-2026/founder-os-pack/)).
@@ -244,12 +201,32 @@ Read the modules in order - each module's output is the next module's input, and
 
 </div>
 
-</div>
+<div class="course-band course-band--dark">
+
+## What this course does NOT cover
+
+To save your time, here is what we intentionally exclude - none of it is needed for the promised result (idea → first paying customer):
 
-## Going further (after first paying customer)
+<div class="scope-grid">
+  <div class="scope-card">
+    <h3 class="scope-card__title">How to code</h3>
+    <p>The course assumes zero coding ability - <a href="https://lovable.dev">Lovable</a> + <a href="https://supabase.com">Supabase</a> + <a href="https://stripe.com">Stripe</a> handle the technical side.</p>
+  </div>
+  <div class="scope-card">
+    <h3 class="scope-card__title">Hiring &amp; managing a team</h3>
+    <p>Covered as a build-path decision in Lesson 4.1, not as org design; early-stage management lives in the <a href="/course/tech-for-non-technical-founders-2026/friday-demo-rule-founder-progress/">Friday Demo Rule</a> + <a href="/course/tech-for-non-technical-founders-2026/weekly-dev-report-template-founders/">Weekly Dev Report</a>.</p>
+  </div>
+  <div class="scope-card">
+    <h3 class="scope-card__title">Raising venture capital</h3>
+    <p>The course produces the artifacts investors want to see. It does not teach pitch decks or fundraising mechanics.</p>
+  </div>
+  <div class="scope-card">
+    <h3 class="scope-card__title">Acquisition at scale</h3>
+    <p>Module 5 covers your first customers; SEO, content marketing, and paid acquisition at scale are a separate discipline.</p>
+  </div>
+</div>
 
-Once you've passed the Module 5 gate, the continuation chapters - churn triage, pivot-or-persevere, hiring, agency oversight - live with their read-this-when triggers in the [First-Paying-Customer Operating Kit](/course/tech-for-non-technical-founders-2026/first-paying-customer-operating-kit/#going-further-triggers).
+<p class="scope-residual">Also out of scope: mobile-only and marketplace-only specifics (they have their own playbooks), and legal incorporation, taxes, and IP filings - use a lawyer or a service like <a href="https://stripe.com/atlas">Stripe Atlas</a>, <a href="https://www.clerky.com/">Clerky</a>, or <a href="https://www.firstbase.io/">Firstbase</a>. If you need something on this list, the course won't help with it.</p>
 
-## Already started building?
+</div>
 
-If you just have an idea or a half-built prototype you're tinkering with, skip to [Module 1](#module-1). If you are already typing, or paying someone an hourly rate to type for you, start with the ownership audit in [Lesson 4.2 · Who Owns Your GitHub, AWS, and Database?](/course/tech-for-non-technical-founders-2026/github-aws-database-ownership-checklist/) - it carries the full pre-flight list to run before you approve any more work.

content/course/tech-for-non-technical-founders-2026/customers-leaving-churn-triage-not-acquisition/index.md

@@ -8,7 +8,7 @@ course_chapter: true
 author: "JetThoughts Team"
 slug: customers-leaving-churn-triage-not-acquisition
 course_nav_prev:
-  url: "/course/tech-for-non-technical-founders-2026/#going-further-after-first-paying-customer"
+  url: "/course/tech-for-non-technical-founders-2026/first-paying-customer-operating-kit/#going-further-triggers"
   module: "Going further"
   title: "All Going-further chapters"
 course_nav_next:

content/course/tech-for-non-technical-founders-2026/github-aws-database-ownership-checklist/index.md

@@ -120,7 +120,7 @@ Whose inbox did the AWS root email land in tonight? If the honest answer is "I'm
 
 ## Already mid-build with a contractor?
 
-A side-path for readers who came from the course landing's [Already started building?](/course/tech-for-non-technical-founders-2026/#already-started-building) fork - you are already typing, or paying someone an hourly rate to type for you. The ownership audit above is step one. Run these before you approve any more work:
+A side-path for readers who came from the course overview's [Already started building?](/course/tech-for-non-technical-founders-2026/how-this-course-works/#already-started-building) fork - you are already typing, or paying someone an hourly rate to type for you. The ownership audit above is step one. Run these before you approve any more work:
 
 1. Demand one Friday demo with working software only - no Jira tickets, no slides, no "almost done." - [Friday Demo Rule](/course/tech-for-non-technical-founders-2026/friday-demo-rule-founder-progress/)
 2. Require a plain-English weekly report: what shipped, what's blocked, what's next. - [Weekly Dev Report](/course/tech-for-non-technical-founders-2026/weekly-dev-report-template-founders/)

content/course/tech-for-non-technical-founders-2026/how-this-course-works/index.md

@@ -40,6 +40,18 @@ This course takes a non-technical founder from a rough idea to a signed paid pil
 
 ---
 
+## Take this course if
+
+- You are a first-time founder with an idea
+- You want the fastest route from that idea to your first paying customer
+- You can read a [Stripe](https://stripe.com) invoice but not a GitHub commit
+- You have never systematically validated a business before
+- You might have tinkered with no-code tools, but you want a structured path instead of guessing
+
+Skip this course if you want to learn to code or hand off founder judgment to someone else. And if what you need most is cohort deadlines and peers, [YC Startup School](https://www.startupschool.org/) runs free - this course is the self-paced, artifact-first alternative.
+
+---
+
 ## The Big Picture
 
 ![Program map: five modules on one spine, each output feeding the next input. Module 1 Hypothesis & Smoke Test produces a tested hypothesis and a live page that takes payment; Module 2 Validate the Problem produces 10 customer interviews and a validated problem statement; Module 3 Design from Evidence produces a one-page product brief in real customer words; Module 4 Build It Yourself produces a live MVP at a real URL with every account in your name; Module 5 First Paying Customer produces a signed paid pilot with a deposit in the bank.](program-map.svg)
@@ -146,7 +158,7 @@ The brief is the handoff document. It goes to Lovable, a hired developer, or a f
 
 **Important distinction:** your warm network is the right place to sell your first paid pilot, and the wrong place to validate the problem. Friends and other founders will tell you your idea is great because they're being polite. Only cold strangers who describe the problem in their own words and pay money produce a real signal.
 
-> **Going further:** After your first paid pilot, the course has continuation chapters for churn triage, pivot-or-persevere decisions, hiring, management (Friday Demo Rule, Weekly Dev Report), and AI-era topics (token bill auditing, slopsquatting, agency AI questions).
+> **Going further:** After your first paid pilot, the course has continuation chapters for churn triage, pivot-or-persevere decisions, hiring, agency oversight and management (Friday Demo Rule, Weekly Dev Report), and AI-era topics (token bill auditing, slopsquatting, agency AI questions). Once you've passed the Module 5 gate, they live with their read-this-when triggers in the [First-Paying-Customer Operating Kit](/course/tech-for-non-technical-founders-2026/first-paying-customer-operating-kit/#going-further-triggers).
 
 ---
 
@@ -203,14 +215,28 @@ If you fail a gate, the system requires you to go back, not forward. Failing at
 
 Read the overview once. Then start at [Module 1, Lesson 1.1: Form Your Founding Hypothesis](/course/tech-for-non-technical-founders-2026/form-your-founding-hypothesis-90-minute-sprint/). Come back to this page when you need to see where you are in the full route.
 
-If you're not at the idea stage - you're already building, or paying someone to build for you - see the [Already started building?](/course/tech-for-non-technical-founders-2026/#already-started-building) section on the course landing page.
+If you're not at the idea stage - you're already building, or paying someone to build for you - see [Already started building?](#already-started-building) below.
 
 > **Done when:** You have read the full route and know which module to start with.
 > **Next click:** [1.1 · Form Your Founding Hypothesis](/course/tech-for-non-technical-founders-2026/form-your-founding-hypothesis-90-minute-sprint/)
 > **If blocked:** If your idea is too vague to fill the hypothesis blanks, Lesson 1.1's "If this fails" section shows how to anchor the blanks with real customer complaints from Reddit and G2.
 
 ---
 
+## Already started building?
+
+If you just have an idea or a half-built prototype you're tinkering with, skip to [Module 1](/course/tech-for-non-technical-founders-2026/#module-1). If you are already typing, or paying someone an hourly rate to type for you, start with the ownership audit in [Lesson 4.2 · Who Owns Your GitHub, AWS, and Database?](/course/tech-for-non-technical-founders-2026/github-aws-database-ownership-checklist/) - it carries the full pre-flight list to run before you approve any more work.
+
+---
+
+## Who built this
+
+Built by [JetThoughts](https://jetthoughts.com). We've run a Rails-first dev shop since 2011, and we have sat on the receiving end of enough first builds gone wrong to know which mistakes repeat: a 15-page wishlist spec where a one-page brief should have been, or a GitHub account registered to a contractor who stopped replying. This course is the desk reference we wish those founders had before their first build decision.
+
+Why free? A founder who validates before building makes a better future client than one we meet mid-disaster, and there is nothing to buy inside the course.
+
+---
+
 **Updated July 2026.** Recent changes:
 
 - Lesson 1.1 split into two short sittings - write first, score later

content/course/tech-for-non-technical-founders-2026/module-5-walkthrough-mia/index.md

@@ -14,7 +14,7 @@ course_nav_prev:
   module: "Lesson 5.6"
   title: "5.6 · Charge Before You Ship: The Paid Pilot Contract"
 course_nav_next:
-  url: "/course/tech-for-non-technical-founders-2026/#going-further-after-first-paying-customer"
+  url: "/course/tech-for-non-technical-founders-2026/first-paying-customer-operating-kit/#going-further-triggers"
   module: "After the course"
   title: "Going further: churn triage, pivot-or-persevere, the operating kit"
 ---

content/course/tech-for-non-technical-founders-2026/pivot-or-persevere-decision-framework/index.md

@@ -12,7 +12,7 @@ course_nav_prev:
   module: "Going further"
   title: "When Your Customers Are Leaving: Churn Triage"
 course_nav_next:
-  url: "/course/tech-for-non-technical-founders-2026/#going-further-after-first-paying-customer"
+  url: "/course/tech-for-non-technical-founders-2026/first-paying-customer-operating-kit/#going-further-triggers"
   module: "Going further"
   title: "All Going-further chapters"
 keywords: