diff --git a/pipeline/test_loop_engineering_meta_prompt.py b/pipeline/test_loop_engineering_meta_prompt.py
index 907ac5a..becd30e 100644
--- a/pipeline/test_loop_engineering_meta_prompt.py
+++ b/pipeline/test_loop_engineering_meta_prompt.py
@@ -16,6 +16,9 @@ def test_loop_engineering_meta_prompt_locks_safety_fields():
         "end-loop guardrails",
         "latency, token use",
         "YouTube `GrNbuWWJYiI`",
+        "Open-source model portability",
+        "quality gate checklist",
+        "YouTube `dJI2GRG1GEE`",
         "Model Workspace Protocol",
         "00-intake/",
         "40-ship/",
diff --git a/plans/meta-prompts/loop_engineering.md b/plans/meta-prompts/loop_engineering.md
index b58cc14..056f0a0 100644
--- a/plans/meta-prompts/loop_engineering.md
+++ b/plans/meta-prompts/loop_engineering.md
@@ -50,6 +50,22 @@ LLMOps/hill-climbing only promotes a changed prompt, retrieval config, tool conf
 
 Reference: Sean's AI Stories, "You Can Learn AI Agent Harness & Loop Engineering In 19 Min" (YouTube `GrNbuWWJYiI`).
 
+## Open-source model portability note
+
+A strong harness should make the task portable across model tiers, including open-source or lower-cost models. Plans must spell out enough context, phases, and quality gates that a non-frontier model can follow the work without relying on hidden taste.
+
+For outbound/productized work, require:
+
+- explicit prospect/input target;
+- crawler or source gathering step;
+- report generation step;
+- cover letter or executive summary when the output is meant to sell or persuade;
+- design/report review phase;
+- quality gate checklist that loops back to the builder when review fails;
+- model/cost notes when choosing GLM/open-source/local models over frontier models.
+
+Reference: Jordan Urbs, "GLM 5.2 Proves Open Source AI Can Match Fable 5 (AI Harness Engineering)" (YouTube `dJI2GRG1GEE`).
+
 ## Model Workspace Protocol note
 
 For sequential workflows with human review between stages, prefer folder-structured orchestration before multi-agent framework code. The Model Workspace Protocol pattern treats numbered folders as stages, markdown files as role/context carriers, and local scripts as the boring mechanical layer.