Library

Policy

Rules, reporting duties, and liability. Filed when we can name the institution and the document.

Follow this shelf

Start here

One worked check, four list prices, then three questions — before you trust what changed this week.

Worked check: PlanAssist cut officer assessment time up to 58% in pilots — DeepMind’s figure; a human still decides. Field card · prices and 4 checks

  1. Measurement — which named test, on which date, scored by whom.
  2. Bill — list input and output per million tokens on the vendor page.
  3. Door — live API, lab claim, replay, or a downloadable file — keep them separate.

Models · Agents · Fine-tuning · All chapters

In this briefing

Nothing on this shelf cleared the bar in the current briefing. The shelf stays up so the category is not mistaken for a gap in the field.

Key companies and projects

No standing list yet. A company appears here when a primary page gives us a reason.

Related tags

  • regulation

The questions worth tracking

Three questions organize this shelf. Who must test a system before it is released, the lab or an independent body? Who must report an incident when an agent acts in the world, and how fast? Who pays if it causes harm? A hearing, a statute, an executive order, or a lab policy counts when the text exists and we can link it.

Voluntary pledges and binding duties are different objects. We will say which one a document is.

How an item earns a place

Policy entries show up in the briefing as sourced developments, then settle here as standing context. Until a document is in hand, this page stays a frame. Policy rumors move faster than the public record, and this shelf is for the document.