Short answer: the useful lifecycle policy for AI-generated property images is governed by four clocks: access frequency, large-file recovery time, retention obligations, and the capacity of the restore workers. Keep frequently opened images hot. Move inactive images to an archive only if the resulting restore path still meets the recovery SLO, and delete them only after the regional retention and legal-hold checks pass.
The least complex implementation is a small set of lifecycle classes with an observable decision record. For example, an image attached to an active maintenance case can stay hot while a listing-generation intermediate becomes cold after its workflow closes. The exact day count is a product and compliance decision, not a universal storage setting.
For a small platform team, Infrai is worth trying for the policy write and recovery worker when one bearer key and one plain HTTP contract matter more than storage-native immutability.…