open/linkedin-studio
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity Actions

docs(linkedin-studio): N4 sannhetspass — GR-modellkorreksjon + maturity/saves/kø/SB-header + refs-badge 28

Browse source 
Del 1 (RE-verifisert mot ground truth): README maturity-note (herding 29/29 +
kald-review 29/29; gjenstår = GUI), CLAUDE.md maturity-linje (B-F10),
hardening-plan-køen t.o.m. S31a/b/c, second-brain-header (SB-S3a-e landet,
kun S4 gjenstår).

Del 2: D-1 BLOCKER — algorithm-signals GR-seksjonen omskrevet mot primærkilde
(LinkedIn engineering-blogg 2026-03-12, Hristo Danchev: Generative Recommender
(GR) offisielt navn + LLM-retrieval + utrulling annonsert); fabrikasjonsflagget
avviste en ekte primærkilde og er trukket med korreksjonsnote; 360Brew-skepsis
beholdt. D-2 — saves-begrunnelse: Marketing API v202604 har POST_SAVE på
/memberCreatorPostAnalytics (partner-gated; manuell inntasting forblir riktig
UX). B-F11 — README refs-badge 26->28 + 25-document->28-document (ls
references/*.md = 28). CLAUDE.md Architecture faar specifics-bank +
contract-gate-linjer.

CHANGELOG-catchup kommer i release-committen (0.6.0) for aa holde
versjonsdeklarasjonene konsistente per commit.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: df0a1ca3-78dd-455e-99a2-e7c133fcb5f6
This commit is contained in:
Kjell Tore Guttormsen 2026-07-17 03:35:40 +02:00
commit 5c6393f2f7
5 changed files with 32 additions and 15 deletions
Download patch file Download diff file Expand all files Collapse all files

28
references/algorithm-signals-reference.md
View file

@ -113,14 +113,25 @@ improves writing); do not justify it as "reduces reach."
## The deployed ranking model — what we can and cannot say
> **An LLM-based relevance-ranking system is live on LinkedIn in 2026.**
> **No public name. No deployment date.**
> **LinkedIn's feed ranking model has an official name: the Generative Recommender (GR).**
> Announced 2026-03-12 on LinkedIn's engineering blog (Hristo Danchev,
> [Engineering the next generation of LinkedIn's feed](https://www.linkedin.com/blog/engineering/feed/engineering-the-next-generation-of-linkedins-feed)):
> a sequential transformer-based ranker that treats member interaction history as a
> timeline, paired with a unified LLM-embedding retrieval system. Rollout announced in
> the same post.
| Claim | Statement | Source | Confidence |
|-------|-----------|--------|------------|
| A live LLM relevance system exists | Confirmed in direction by LinkedIn's 2026 communications. | LinkedIn comms (2026) | high |
| Production name | **Not publishable as fact.** The most-cited arXiv paper (2501.16450) is a Jan-**2025** *pre-production research* model (V1.0, 150B params, offline parity only), **withdrawn 2025-08-23**. A circulating "Generative Recommender / Hristo Danchev" engineering-post citation was independently flagged as **likely fabricated** — do not propagate. | arXiv 2501.16450; Gemini provenance flag | high (on the negative claim) |
| Deployment date | No primary source. The "early-2026" date is third-party extrapolation from the paper's Jan-**2025** date. **Do not assert a date.** | — | n/a |
| Production name | **Generative Recommender (GR)** — official, primary-source. | LinkedIn engineering blog, 2026-03-12 | high |
| LLM-based retrieval | Confirmed: "a unified retrieval system leveraging advances in LLMs to generate a high-quality representation of our members and content." | Same post | high |
| Deployment | Rollout announced 2026-03-12 ("rolling out a new advanced ranking system"). Full-coverage completion date not stated — do not assert one. | Same post | high (announcement), n/a (completion) |
| "360Brew" as the production name | **Still not publishable.** The arXiv paper (2501.16450) is a Jan-**2025** *pre-production research* model (V1.0, 150B params, offline parity only), **withdrawn 2025-08-23**; the "360Brew" label is third-party and has no official confirmation. GR is the official name. | arXiv 2501.16450 | high (on the negative claim) |
*Correction note (2026-07-17): this section previously said "No public name. No
deployment date." and flagged the Generative Recommender / Hristo Danchev
engineering-post citation as likely fabricated. That flag was wrong — and was already
wrong at "Last updated 2026-05": the official post had been live since 2026-03-12,
two months earlier. The fabrication flag rejected a genuine primary source.*
## Operational heuristics (directional — test per account)
@ -177,10 +188,11 @@ source.)
---
*Last updated: 2026-05. Maintained as the single canonical algorithm statement; cite, do
not restate.*
*Last updated: 2026-07-17 (GR-model correction). Maintained as the single canonical
algorithm statement; cite, do not restate.*
*Sources (per-claim quality/confidence noted inline): arXiv 2501.16450 (pre-production
*Sources (per-claim quality/confidence noted inline): LinkedIn Engineering — "Engineering
the next generation of LinkedIn's feed" (Hristo Danchev, 2026-03-12); arXiv 2501.16450 (pre-production
research paper, withdrawn 2025-08-23); LinkedIn Engineering — "Leveraging Dwell Time" (2024); Tim Jurka, Head of Feed
AI (2025-08-11); Laura Lorenzetti, VP & Exec Editor (2026-05-19); Gyanda Sachdeva, VP
Product (2026-02-16); Matt Navarra relaying LinkedIn Sr. Director Product (Aug 2025);