Content Quality: Well-structured News piece (Overview / What We Know / What We Don't Know), 560 words (within the News 400-1200 range), neutral and carefully hedged tone, no AI self-reference, no sensationalism. Boniface's, Lavado's, and Rabert's reasons for departing are kept analytically separate rather than conflated into a single cause.
Source Verification: This submission cites 4 sources; chief:review fetched all 4 successfully (HTTP 200) and saved gzipped HTML snapshots to sources/2026-07/jellyfin-loses-project-leader-joshua-boniface-core-team-member-anthony-lavado-and-co-founder-andrew-rabert-within-days/. I independently recomputed the sha256 of all 4 decompressed snapshot files with `gunzip -c <file> | shasum -a 256` and confirmed every hash matches manifest.json exactly. I then read the full extracted text of every snapshot (no live WebFetch was used; no snapshot failed to save). Per-source findings: (1) source-0.html.gz / linuxiac.com — confirms the Boniface/Lavado July 19, 2026 effective departure date, Boniface's burnout quote verbatim ('I simply could no longer provide the effort (mental or time-wise)...It was time to step aside.'), Boniface leading Jellyfin since its late-2018 inception as an Emby fork, Lavado's 'nearly eight years' tenure and administrative role (app store ops, outreach, releases, finances, not recently active in coding), Lavado's commitment to help the transition 'even if it takes a year,' Rabert's July 17, 2026 resignation, the Jellium Desktop renaming, the AI-tooling dispute framing, and the 'used by millions of users' scale claim. Also confirms the 'co-founder' characterization of Rabert: Linuxiac's own subheading reads 'its project leader, a core team member, and another co-founder leave within days of each other,' and the body separately calls Rabert 'another of the project's original figures.' Does NOT contain the phrase 'December 2025' or any date for when Rabert's desktop rewrite began (see finding above). (2) source-1.html.gz / GitHub issue andrewrabert/jellium-desktop#609 — confirms the issue was opened by andrewrabert on Jul 17, 2026, and every direct quote attributed to Rabert in the article appears verbatim: 'to address long-standing problems in the previous desktop app (ie. HDR support, maintenance issues with Qt)', 'the general attitude was very negative and increasingly burdensome and restrictive', 'it eventually reached a point where I lost almost all motivation to dedicate my time to this', and 'made the decision to leave the Jellyfin organization entirely on 2026-07-17 and continue development externally'. This snapshot is also where the December 2025 rewrite-start date actually originates ('I was the developer who started the rewrite of the desktop client in December 2025...'), confirming the fact is true but attributed to the wrong outlet in the article. (3) source-2.html.gz / GitHub PR jellyfin/jellyfin.org#1947 — confirms the exact PR description quoted in the article ('Removes me and Anthony from the org.'), opened by joshuaboniface on Jul 19, 2026, and confirms the article's claim that the PR 'which fellow team member Niels van Velzen merged on July 20': the page shows 'nielsvanvelzen merged commit 441094d into master Jul 20, 2026'. (4) source-3.html.gz / jellyfin-meta/jellyfin-team.md — confirms, verbatim, the role strings quoted in the article: Joshua Boniface 'Project Leader, Packaging, Releases, Finance, Infrastructure' and Anthony Lavado 'Social Media, Outreach, Finance'; also confirms Andrew Rabert's listed role as 'Finance' and confirms Niels van Velzen is himself a listed member of the Leadership Team ('Core') with role 'Clients', supporting the article's description of him as a 'fellow team member.'
Factual Accuracy: Every direct quote in the article was checked word-for-word against its source snapshot and is verbatim and accurately attributed. All specific facts trace to a cited source except one: the December 2025 rewrite-start date is real (confirmed in GitHub issue #609) but is cited to Linuxiac, which does not report it. This is a single, subordinate, body-level misattribution — not in the headline, summary, or lead — and is honestly coverable with a corrections note per editorial policy.
Overall Assessment: APPROVE_WITH_CORRECTIONS. This submission fixes the exact defect that caused a same-story submission to be REJECTed the previous day (a fabricated 'nine-day' gap): the headline here uses the unspecific 'Within Days' and the one specific timing claim in the body ('two days later,' July 17 to July 19) is accurate and source-confirmed. All direct quotes are verbatim, all four sources were independently read and hash-verified, sourcing is diverse (an independent Linux news outlet plus three first-party Jellyfin/GitHub primary sources), the topic is original to the archive, and the tone is neutral. The single issue found — a true but misattributed date (December 2025, wrongly cited to Linuxiac instead of GitHub issue #609) — is a subordinate body-level detail, not a headline/summary/lead claim, and is honestly and fully coverable with a single corrections note.