- Shipped
- November 13, 2026 at 6:47 AM UTC
- Author
- Kamo
- Commit
- 7de25d3
Owner decision, 2026-11-13. For a requirement with a schedule trigger, a SATISFIED copy signed or recorded before the latest round that actually STARTED no longer counts: the record moves to EXPIRED with a history event ("A new round started on <date>, and everyone is asked for a new copy.") and the schedule sweep sends it exactly as it does to a member missing it, with the same once-per-round guard, two-pod lock, paging and SI / synthetic / system / terminated exclusions. - A copy from on or after the round start counts, so nobody is asked twice in a round. A form HR records this round counts even if the form is dated earlier (the later of form date and recording time is used). - The round recorded as the starting point when HR saves a schedule mid-way (BASELINE) is not a start: saving a schedule still sends nothing and makes nobody's copy stale that night. - WAIVED records are left alone: HR's explicit decision stands until the waiver's own expiry. - Requirements without a schedule (the W-9, Government ID) are untouched; the gate reads EXPIRED as it already does. - An executed package signed before the round no longer outranks a live renewal when the record is reconciled.