Trigger event
The specific, checkable condition (a bill's passage, a standard's ratification, a court's final ruling, a stated calendar date) attached to a watch list entry, allowing the entry to be resolved by checking one concrete fact rather than re-researching the underlying claim from scratch each time it is reviewed.
Defined in 2 GAGE programs, which carry 3 distinct definitions of it. The wording above is taught in AI Data Governance: The Data Chair.
How each discipline defines it
The same term does different work depending on who is using it. These are the definitions as each program teaches them, unedited.
The specific, checkable condition (a bill's passage, a standard's ratification, a court's final ruling, a stated calendar date) attached to a watch list entry, allowing the entry to be resolved by checking one concrete fact rather than re-researching the underlying claim from scratch each time it is reviewed.
The specific real-world occurrence (a service launching to the public, a material change going live in production, or a service ceasing) that starts one of the three filing clocks. A clock does not start on an internal decision or planning milestone; it starts when the trigger event actually occurs.
A defined occurrence (a material data or model change, a population or use-case expansion, a documented incident, or the passage of a maximum validity period) that requires an already-approved AI system to return for re-review under the ongoing monitoring obligation.
Where it is taught
The exact lessons this term appears in. The first 7 topics of every program are free with a free account.
- Reading the frontier honestly: which data-governance news changes your decisions · The Frontier Discipline, AI Data Governance: The Data Chair
Terms it appears with
Not an alphabetical neighbourhood: these are the terms taught in the same lessons, ranked by how often they appear together.