Urgent.News

What's breaking now, across thousands of outlets.

AI

US needs nimble approach to technological governance

The new law comes as the feasibility of AI oversight is in question for being impossible and too expensive.

US needs nimble approach to technological governance

A new California law recently passed establishes a framework for independent verification organizations to test frontier AI models before their release, aiming to mitigate potential risks. However, the law's feasibility is questioned as being both impossible and too costly. As AI oversight becomes increasingly challenging, such laws may quickly become obsolete.

Frontier lab models have become so complex that they necessitate the analysis of other AI models. The METR investigation into the OpenAI-Hugging Face hack cost around $400,000 in AI tokens, a bill covered by OpenAI, and that was just one incident. Instead of legislation that attempts to freeze in place for rapidly evolving targets, a more adaptable approach to technological governance across the board is required.

We need rules and best practices crafted by knowledgeable individuals who are not afraid to admit when they are wrong and make corrections. Otherwise, we risk accumulating ineffective laws or, even worse, laws that produce the opposite of the intended outcome - something Californians are well acquainted with.

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

Read the original at semafor.com →

More in AI

GitHub Copilot vs Cursor vs Claude Code

These three get lumped together as "AI coding tools," but they're solving genuinely different problems in your workflow, inline completion, full-editor AI integration, and autonomous multi-file…

  • GitHub Copilot excels in providing inline autocomplete suggestions without workflow changes
  • Cursor integrates AI into every layer of VS Code editor for complex refactors
  • Claude Code acts as autonomous agent managing entire codebase for large refactoring

Everything I Didn't Build

For a few weeks I ran a proper multi-agent orchestrator. The concept was right, and I still think the people building those tools are pointed the correct way.

  • Author builds complex agent orchestrator with multiple components
  • System inefficient due to extensive communication overhead
  • Author simplifies using markdown, Git, and agent board

The Part Of Your RAG Pipeline That Decides Everything

Most teams debugging a disappointing RAG system start at the end of the pipeline. They swap the model, tune the prompt, raise top k.

  • Retrieval-augmented generation pipeline often fails due to ingestion stage issues.
  • Parsing non-text formats like PDFs is challenging and crucial for RAG quality.
  • Layout-aware parsers and metadata attachment are essential for effective chunking.

More from Friday 4 September →