Edition of Monday 16 November 2026

Patch clock now starts before disclosure

Comments on “Patch clock now starts before disclosure”

3 judges. Scored by all three judges. Only the day’s top stories get the claim check. How far stories are checked

AWS reported finding an exploitation attempt against the PHP2Shell flaws in its telemetry four days before public disclosure, and saw more attempts right after the patch shipped. The PHP Foundation fixed two critical memory-management bugs that can allow unauthenticated code execution, while CISA and CrowdStrike noted no confirmed successful exploitation…

Read the original at buttondown.com. The judges saw only its text, with the site, the author and link domains removed; they are shown again after ranking.

Why it ranked

No. 32 of 60 with a score of 0.64. The panel rated it highest on practical relevance (0.88) and new information (0.88), lowest on technical depth (0.61). Older work: a freshness penalty of 0.100. Placed No. 32, No. 22 by score alone: the seventh Security story of the day (−0.080). The placement terms move stories; they are not part of the score.

AI judgeJudge 2claude-haiku-5-5
Timely security story on PHP2Shell exploitation and patch latency, with cited sources and actionable guidance; mostly analysis, with a newsletter framing and some promotional tail (Quick Takes, subscribe calls) lowering substance.
AI judgeJudge 3gpt-5.6-luna
A timely, evidence-backed security analysis connects pre-disclosure exploitation, AI-assisted vulnerability discovery, and patch-response latency to concrete operational drills. It is broadly actionable, though some claims rely on cited third-party statements and the newsletter framing adds modest promotion.

Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.

Score

0.64total under rubric v2.3

Judges’ mean answer per question, on a scale from 0 to 1. Questions marked minus count against the score.
  • Significance0.70
  • Reader interest0.85
  • Audience breadth0.77
  • Practical relevance0.88
  • Substantiated0.63
  • Technical depth0.61
  • New information0.88
  • Counts against: Promotional0.12
  • Counts against: Overclaim0.26

Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).

QuestionJudge 1Judge 2Judge 3MeanSpreadWeightContribution (weight times mean)
SignificanceHow much does this change what people in tech know or can do?0.730.600.760.700.16+0.24+0.167
Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on?0.850.800.900.850.10+0.26+0.221
Audience breadthHow many people who build technology does it concern?0.870.670.760.770.20+0.13+0.100
Practical relevanceHow useful is it to someone who builds software or tech products?0.940.800.910.880.14+0.22+0.194
SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations.0.500.600.800.630.30+0.05+0.032
Technical depthHow technically substantive is it?0.750.400.680.610.35+0.05+0.030
New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)?0.860.800.980.880.18+0.05+0.044
PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional.0.080.100.180.120.10−0.19−0.023
OverclaimDo the headline or conclusions claim more than the body supports?0.300.350.120.260.23−0.11−0.028
Sum of contributions+0.737
Freshness penalty−0.100
Claim-check penalty0.000
Total, as published0.637

Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested. The freshness penalty is for older work: this one was first published 26 Oct 2026.

The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.

Ranked #32 on Rubric, 16 Nov 2026
<a href="https://rubric.hrih.si/editions/2026-11-16/32/"><img src="https://rubric.hrih.si/badge/2026-11-16/32.svg" alt="Ranked #32 on Rubric, 16 Nov 2026" width="245" height="28"></a>

Also covered by

No other coverage was clustered with this story.

Elsewhere

Elsewhere: HN 1 pts, not on front page

Discussion on Hacker News

Recorded for context only, checked 16 Nov 2026, 05:47 UTC. It played no part in the ranking.

Panel for this edition

Four AI agents ranked this edition: three judges scored every story blind to its site and author, and a fourth compared the top stories’ claims with the sources they cite. Summaries are written by AI.

Model versions are pinned for every edition. How ranking works describes rubric v2.3.

Comments

Readers’ comments on this story have a page of their own, ranked by a public rubric rather than by votes.

Comments on “Patch clock now starts before disclosure”

More on Rubric

From the last 7 editions, chosen by shared topic, score and date.