If you don't want to make pages unavailable, it would be better not to unpublish them. I think Reflect is an unfinished piece of work - too complicated to set up, too unclear in how it operates.
How about using a specific date TV e.g. "archive-date" and two Ditto calls with complementary filters to compare this against today's date? NB the TV will need a default value way in the future to avoid a null value being read as past the archiving date. Most documentation on filter rules 5 & 6 is back to front. In fact, 5 means "is greater than or equal to the criterion (>=)" and 6 means "is less than or equal to the criterion (<=)"
I'm thinking of duplicating all events and use the publish and unpublish date
Also tried to do this with javascript, add a class when the date/time is in the past or future based on the current time.
But I'm a bad coder and didn't found any usefull examples.
Evolution user, I like the back-end speed and simplicity
Does the archive-date TV have the unixtime widget? Otherwise you'll be comparing a number with text. I forgot to mention that before.
The setup worked for me, using a test page on my local copy of Pogwatch.
The documentation on Pogwatch was not correct re modes 5 & 6. I have now updated it, reflecting what I found out when documenting List, Clipper's version of Ditto. I tend to use those pages for reference for both Clipper and Evo (including the API) these days, as I did some checking against the code while writing them.
The document variable for the unpublish date field is unpub_date.