Edition of Friday 13 November 2026

Running Doom as a Temporal Workflow

Comments on “Running Doom as a Temporal Workflow”

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

A Temporal blog post shows how DOOM can run as a Temporal Workflow, using the engine's deterministic design. Player inputs are delivered as Workflow Updates and recorded in Event History, so a new Worker can replay them to rebuild game state after a crash.

Read the original at temporal.io. 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. 113 of 137 with a score of 0.57. The panel rated it highest on new information (0.91) and technical depth (0.88), lowest on significance (0.46). Placed No. 113, No. 111 by score alone: the 16th Programming & dev tools story of the day (−0.080). The placement terms move stories; they are not part of the score.

AI judgeJudge 2claude-haiku-5-5
A detailed, technically specific write-up of running DOOM on a durable-execution platform; substantive and reproducible, but a novelty demo with some promotional framing and modest practical reach.
AI judgeJudge 3gpt-5.6-luna
A technically detailed, reproducible engineering demonstration maps deterministic event sourcing, replay, snapshots, versioning, and multiplayer coordination onto durable workflows. It offers broadly useful infrastructure lessons, though the specific DOOM application is primarily illustrative.

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.57total under rubric v2.3

Judges’ mean answer per question, on a scale from 0 to 1. Questions marked minus count against the score.
  • Significance0.46
  • Reader interest0.73
  • Audience breadth0.50
  • Practical relevance0.62
  • Substantiated0.78
  • Technical depth0.88
  • New information0.91
  • Counts against: Promotional0.18
  • Counts against: Overclaim0.18

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.460.300.620.460.32+0.24+0.110
Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on?0.680.600.900.730.30+0.26+0.189
Audience breadthHow many people who build technology does it concern?0.550.400.550.500.15+0.13+0.065
Practical relevanceHow useful is it to someone who builds software or tech products?0.650.500.720.620.22+0.22+0.137
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.800.700.840.780.14+0.05+0.039
Technical depthHow technically substantive is it?0.950.800.880.880.15+0.05+0.044
New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)?0.860.900.960.910.10+0.05+0.045
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.070.400.080.180.33−0.19−0.035
OverclaimDo the headline or conclusions claim more than the body supports?0.230.200.120.180.11−0.11−0.020
Sum of contributions+0.575
Claim-check penalty0.000
Total, as published0.575

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 badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.

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

Also covered by

No other coverage was clustered with this story.

Elsewhere

Elsewhere: HN 3 pts, not on front page

Discussion on Hacker News

Recorded for context only, checked 15 Nov 2026, 20:42 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 “Running Doom as a Temporal Workflow”

More on Rubric

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