From 6738f7d573e30752ae7bed849f7515a10a1cf519 Mon Sep 17 00:00:00 2001
From: Matthias Nott <mnott@mnsoft.org>
Date: Fri, 10 Apr 2026 15:53:15 +0200
Subject: [PATCH] fix: require JD verification before adding to triage

---
 workflows/NewTriage.md |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/workflows/NewTriage.md b/workflows/NewTriage.md
index ab1adc3..2219d20 100644
--- a/workflows/NewTriage.md
+++ b/workflows/NewTriage.md
@@ -171,7 +171,7 @@
 
 ### Build master job list with REAL LINKS
 
-**EVERY job in the triage file MUST have a clickable link.** Never use placeholder text like "LinkedIn (from Python alert)" or "JobUp UUIDs (need Playwright)". If the link was in the email, extract it. If it wasn't, note what's needed to find it.
+**EVERY job in the triage file MUST have a clickable link AND a verified JD.** Never list a job based solely on an email digest title. The actual job page must be visited (via Playwright for LinkedIn) and the JD confirmed to exist before adding to the triage. Email digests (especially Sunday JYMBII weekly digests) often contain stale, closed, or non-existent listings. Subagents have been caught hallucinating job IDs from digest emails. Trust but verify - scrape the JD, then list.
 
 Format:
 - LinkedIn: `[LI XXXXXXXXXX](https://www.linkedin.com/jobs/view/XXXXXXXXXX)`

--
Gitblit v1.3.1