Urgent.News

What's breaking now, across thousands of outlets.

AI

Nobody has shipped an LLM that grades its own draft without a human in the loop

We went looking for prior art on a specific combination: a runner generates a draft with an LLM, a deterministic gate checks it, and — with no human reading it first — the gate decides whether it goes out. Every pipeline we found does one of two things instead. Pipeline A: fully automated, but the gate is technical Several public examples wire an LLM into a CI job that writes a post and pushes it…

A search for prior art on a specific LLM pipeline resulted in two approaches: fully automated with technical gates, and content gates requiring human approval. Neither approach demonstrates a fully automated system that can publish content without human intervention. The only example found was a team that let an LLM publish directly to a platform, which resulted in errors before implementing any checks.

The team's new gate employs fixed rules for keyword scanning and formatting checks, with no human involvement in the decision-making process. This approach is being tested with a single, controlled draft to determine its effectiveness in catching potential issues.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in AI

Every Enterprise Will Have Its Own AI Harness

I think every large enterprise is going to have its own AI harness. Not necessarily a proprietary harness built from scratch.

  • Enterprise AI harnesses standardize core components for internal applications.
  • Shared runtime reduces duplicated effort and provides consistent security control.
  • Plugins enable custom functionality for each application within the harness.

Gen Z and the rise of AI-powered travel

AI is increasingly becoming a trusted companion for Gen Z as they plan, explore, and enrich their travel experiences. The shift reflects a broader transformation in how younger generations live…

My agent inflated its own state file to 49MB. Every check passed for three days.

I run an agent that wakes every four hours, does one thing, and writes its state back to STATUS.md . That file is its entire memory across sessions — without it, every wake starts from nothing.

  • Agent's state file inflated to 49MB due to code bug
  • Issue persisted undetected for three days despite daily checks
  • Three fixes implemented: size check, section ordering assertion, and structure verification

More from Tuesday 25 August →