Designing an Always-On Agent
Comments on “Designing an Always-On Agent”
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
An engineering post argues that the gap between today's chatbots and the Jarvis-style assistant is mostly about form factor rather than raw model capability. It describes an architecture for an always-on agent: a single thread that manages its own context through compaction tools, sub-agents for heavy work, a heartbeat for…
Why it ranked
No. 24 of 46 with a score of 0.61. The panel rated it highest on new information (0.79) and reader interest (0.79), lowest on substantiated (0.37). Placed No. 24, No. 16 by score alone: the sixth AI & machine learning story of the day (−0.060). The placement terms move stories; they are not part of the score.
- AI judgeJudge 2claude-haiku-5-5
- Clear architectural essay on always-on agents with concrete design patterns (compaction tools, heartbeats, notifications), but largely experience-based with little evidence and some unsupported claims about model discernment.
- AI judgeJudge 3gpt-5.6-luna
- A substantive architecture proposal for persistent, proactive agents, with concrete mechanisms for context management, dispatch, heartbeats, notifications, and discernment. It is useful and timely, though largely experiential rather than experimentally validated.
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.61total under rubric v2.3
- Significance0.54
- Reader interest0.79
- Audience breadth0.66
- Practical relevance0.72
- Substantiated0.37
- Technical depth0.66
- New information0.79
- Counts against: Promotional0.16
- Counts against: Overclaim0.27
Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).
| Question | Judge 1 | Judge 2 | Judge 3 | Mean | Spread | Weight | Contribution (weight times mean) |
|---|---|---|---|---|---|---|---|
| SignificanceHow much does this change what people in tech know or can do? | 0.61 | 0.40 | 0.62 | 0.54 | 0.22 | +0.24 | +0.130 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.71 | 0.80 | 0.86 | 0.79 | 0.15 | +0.26 | +0.205 |
| Audience breadthHow many people who build technology does it concern? | 0.70 | 0.60 | 0.68 | 0.66 | 0.10 | +0.13 | +0.086 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.79 | 0.60 | 0.78 | 0.72 | 0.19 | +0.22 | +0.159 |
| 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.19 | 0.35 | 0.58 | 0.37 | 0.39 | +0.05 | +0.019 |
| Technical depthHow technically substantive is it? | 0.74 | 0.60 | 0.63 | 0.66 | 0.14 | +0.05 | +0.033 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.82 | 0.70 | 0.86 | 0.79 | 0.16 | +0.05 | +0.040 |
| 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.11 | 0.20 | 0.18 | 0.16 | 0.09 | −0.19 | −0.031 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.23 | 0.30 | 0.28 | 0.27 | 0.07 | −0.11 | −0.030 |
| Sum of contributions | +0.611 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.611 | ||||||
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.
<a href="https://rubric.hrih.si/editions/2026-11-09/24/"><img src="https://rubric.hrih.si/badge/2026-11-09/24.svg" alt="Ranked #24 on Rubric, 9 Nov 2026" width="238" height="28"></a>Claim check
Claim check: 1 matches source · 7 no source given. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.
No source givenGeneralization
Compaction is the de facto standard for managing context windows in agents.
The article gives no link or citation for it.
The article says “Compaction is the de facto standard for managing context windows”
The source says No source to compare with.
No source givenCausal conclusion
Rubric Labs found that compaction, especially when done by a third-party process, hurts the agent's momentum.
The article gives no link or citation for it.
The article says “we've found that compaction lobotomizes the agent's momentum, especially when it's done by a third-party process”
The source says No source to compare with.
No source givenGeneralization
In Rubric's setup, agents tend to wait for a lull, like the end of a task, before compacting their context, folding away reasoning and tool calls they won't need again.
The article gives no link or citation for it.
The article says “our agents tend to wait for a lull, like the end of a task, before they compact”
The source says No source to compare with.
No source givenCausal conclusion
Coding agents became very capable with a single tool for running terminal commands on users' computers.
The article gives no link or citation for it.
The article says “Coding agents got great with one simple tool for running terminal commands on our computers”
The source says No source to compare with.
Matches sourceNumber
Jev is a small system-one model that can classify notifications as important or unimportant.
The cited source says the same thing.
The article says “classify notifications as important or unimportant with a smaller model, such as a system one model like Jev”
The source says “we asked Jev two questions: Does this notification need the recipient to act? And is it time-sensitive”
Source cited by the article: rubriclabs.com/blog/what-can-you-build-with-jev
No source givenCausal conclusion
Today's models lack discernment because their RL training taught them to crush tasks, so they struggle in ambiguous environments.
The article gives no link or citation for it.
The article says “Everything in their training (specifically their RL arenas) has taught them how to crush tasks”
The source says No source to compare with.
No source givenGeneralization
Agents processing Slack messages often act on messages not addressed to them, then write a design doc after discovering they lack the mandate, access and context.
The article gives no link or citation for it.
The article says “agents processing messages on Slack often decide to act on messages that aren't addressed to them”
The source says No source to compare with.
No source givenCausal conclusion
Disagreement over whether AGI has been reached stems more from form factor than from model capabilities.
The article gives no link or citation for it.
The article says “the reason people disagree about whether we've reached AGI is more about form factor than it is about model capabilities”
The source says No source to compare with.
Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN 2 pts, not on front page
Recorded for context only, checked 9 Nov 2026, 05:46 UTC. It played no part in the ranking.