This controls whether a confirmation rule stays permanently active and keeps matching future discoveries, fires once and then ages out after a set duration, or fires once and never expires. An admin picks onceAging(1) for a temporary bulk-approval window that closes itself automatically, versus always(0) for a standing auto-accept policy for a trusted, ongoing batch of installs. For example, using onceAging(1) during a scheduled mass-install weekend lets installers plug in pre-approved units freely, with the rule closing on its own once the window elapses.