docs(tac): add founder learning loop guidance

Fold the three-video business, macro, and AI-learning synthesis into TAC loop-engineering guidance. Convert market stories, money-flow narratives, and AI demos into small receipt-bound operating loops with niche/distribution, money-flow, AI-amplifier, and seven-day experiment checks.

pipeline/test_loop_engineering_meta_prompt.py

@@ -36,6 +36,12 @@ def test_loop_engineering_meta_prompt_locks_safety_fields():
         "Sweeper",
         "Architect/Primitive keeper",
         "role collapse means expertise is obsolete",
+        "Founder learning loop",
+        "Niche/distribution thesis",
+        "Money-flow map",
+        "AI amplifier check",
+        "Seven-day learning protocol",
+        "xunx7VvlOgs",
         "Insider-threat model",
         "least-privilege access",
         "no raw secrets",

plans/meta-prompts/loop_engineering.md

@@ -114,6 +114,19 @@ Treat AI-era role archetypes as activity modes in the delivery loop, not permane
 
 Do not claim role collapse means expertise is obsolete. The safer claim is that boundaries flex while specialties, ownership, and best practices remain necessary.
 
+## Founder learning loop note
+
+For product/factory bets, do not treat market stories, macro narratives, or AI demos as strategy by themselves. Convert them into small operating loops:
+
+- **Niche/distribution thesis** — name the narrow buyer, geography/channel, hard-to-replace acquisition route, and revenue concentration risk.
+- **Money-flow map** — name what trust, incentive, or regime shift moves budget toward or away from the product.
+- **AI amplifier check** — name what AI improves, what system weakness it does not fix, and which verification/cost signals prove the improvement.
+- **Seven-day learning protocol** — summarize sources, extract one work-relevant idea each, run three micro-experiments, define KPIs, compare to baseline, then kill one / keep one / improve one.
+
+Treat these as hypothesis inputs until receipts, customer evidence, or measurable experiment output exist.
+
+References: My First Million `OXgqzF382o8`, Anthony Pompliano `bJD-Ftig30M`, Dylan Beattie / NDC `xunx7VvlOgs`.
+
 ## Insider-threat model note
 
 Treat coding agents and frontier-model work agents as potential insider threats once they can read files, call tools, write code, or touch deploy paths. Plans that give an agent business-impacting access must include: