Urgent.News

What's breaking now, across thousands of outlets.

Tech

Guardrails Are a Design Review, Not a Filter

Originally published at Trida AI . An agent that can issue refunds, update inventory, or write back to a system of record does not fail in its wording first. It fails in its actions: a refund approved above the limit the business intended, a record changed that should only have been read, a write executed when the instruction was to prepare a draft. A filter placed on the final answer inspects…

Guardrails are not a final filter, but rather a critical design review process that occurs before an AI system is deployed. These guardrails consist of a stack of controls that are placed at various points to prevent different types of failures, such as preventing a refund from being approved above a set limit, or stopping a system from changing a record that should only have been read.

Input checks occur before the model sees any data, while tool permissions are assigned to specific actions that an agent can perform. Output checks occur before the response is delivered to a user or downstream system. Human escalation is a separate layer that provides a last line of defense. When an action is flagged, a person receives the proposed action, the reason it was flagged, and the authority to approve, modify, or reject it.

An audit trail records every blocked input, permission denial, approval, and override, with the specific request and control decision. Authority is distributed through a set of levels, and should be granted based on operational evidence and trust. An agent should only have the authority necessary for its specific task, and this authority should be increased as more evidence is gathered.

Policies must be converted into runtime controls, and traced back to the obligation behind them, to ensure compliance with legal and internal regulations. Access control and guardrails are separate, with authentication establishing who is acting, but not whether the action is allowed. Logging and recording of all actions and decisions are critical to understanding the effectiveness of the guardrail system.

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 Tech

Trunk-Based Development With Coding Agents: What Replaces Code Review?

TL;DR: Trunk-Based Development With Coding Agents On August 13th, Amp's Will Dollman explained why Amp's trunk-based development, with engineers pushing straight to main and no pull requests, still…

  • Before push, agents provide proof of code functionality using demos, test matrices, and logs.
  • Continuous Integration (CI) tests, infrastructure checks, and security scans block failing changes.
  • Traceability links each commit to its Amp thread, ensuring accountability and transparency.

Clockworks TikTok Scraper Alternative: Same Input JSON, 6x Cheaper

I pasted one TikTok scraping input into two Apify Actors on 20 October 2026. Same JSON, same account, under a minute apart. One run cost $0.071 .

  • Same TikTok scraping input tested on two Apify Actors
  • Cheaper actor priced at $0.011, first actor at $0.071
  • Cheaper actor returns videos up to 3.8 years old

More from Tuesday 20 October →