pr/jobs: revert cycle-18 verify-person same-run corroboration (Cody gate → HOLD-FOR-STEVE). The stale read defers LinkedIn corroboration to a future re-verify; fixing it to corroborate same-run is DEFENSIBLE (eventual state is identical — old code corroborates on the next run) but its SOLE effect touches a contested trust behavior: whether org+title site evidence should promote a search-LOCATED, surname-matched LinkedIn URL to found_corroborated at all (site evidence corroborates the ROLE, not the URL identity). That's a trust-model decision for Steve. Left a NOTE comment; drafted the question to pending-approval

a1432cf2c0cadabe469e31d8542f5dd85a524579 · 2026-08-06 00:27:06 -0700 · Steve

Files touched

M src/pr/jobs/index.js

Diff

commit a1432cf2c0cadabe469e31d8542f5dd85a524579
Author: Steve <steve@designerwallcoverings.com>
Date:   Thu Aug 6 00:27:06 2026 -0700

    pr/jobs: revert cycle-18 verify-person same-run corroboration (Cody gate → HOLD-FOR-STEVE). The stale read defers LinkedIn corroboration to a future re-verify; fixing it to corroborate same-run is DEFENSIBLE (eventual state is identical — old code corroborates on the next run) but its SOLE effect touches a contested trust behavior: whether org+title site evidence should promote a search-LOCATED, surname-matched LinkedIn URL to found_corroborated at all (site evidence corroborates the ROLE, not the URL identity). That's a trust-model decision for Steve. Left a NOTE comment; drafted the question to pending-approval
---
 src/pr/jobs/index.js | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/src/pr/jobs/index.js b/src/pr/jobs/index.js
index d21045ca..e1b5b5a7 100644
--- a/src/pr/jobs/index.js
+++ b/src/pr/jobs/index.js
@@ -293,11 +293,11 @@ const handlers = {
       const hit = rep.items[0];
       if (hit) {
         await people.update(pid, { linkedin_url: hit.linkedin_url, linkedin_status: 'found_uncorroborated' }, 'system:verify-person');
-        // Keep the in-memory `p` fresh: the corroboration check below reads p.linkedin_url /
-        // p.linkedin_status. Without this, a JUST-located URL is invisible there (stale read from
-        // the load at the top), so a site-backed person wouldn't corroborate until a future re-verify.
-        p.linkedin_url = hit.linkedin_url;
-        p.linkedin_status = 'found_uncorroborated';
+        // NOTE (open design question — see pending-approval memo): the corroboration check below reads
+        // a STALE in-memory `p` (loaded at the top), so a JUST-located URL is only promoted to
+        // found_corroborated on a FUTURE re-verify, not same-run. Whether that promotion should happen
+        // at all on org+title site evidence (which corroborates the ROLE, not the URL's identity) is a
+        // trust-model decision for Steve — deliberately NOT changed here.
         await db.query('UPDATE pr_people SET linkedin_indexed_title=$2, linkedin_indexed_snippet=$3 WHERE id=$1', [pid, hit.indexed_title, hit.indexed_snippet]);
         await people.attachEvidence(pid, {
           source: { source_type: 'search_api', source_name: 'LinkedIn locate (authorized search)', url: hit.source_url, short_excerpt: hit.indexed_snippet, is_primary_source: false, license_or_usage_note: li.sourceMeta().license_or_usage_note, adapter: 'linkedin' },

← 5df9e1d2 pr/jobs: fix stale-read in verify-person that deferred Linke · back to Rentv 2026 · auto-save: 2026-08-06T00:47:08 (7 files) — data/deals-regist 0ada77c4 →