File pool policy logic "start in SSD and tier to HDD by age/date modified"

What would be the correct file pool policy layout to have a dataset under a specific directory path start in the SSD tier (less capacity but faster) and tier to HDD tier (more capacity but slower) after date modified = more than y time is reached?

My take:

Policy 1 "Move old data to HDD", first position in order:

If path = x AND date modified = older than y time -> move to HDD tier

Policy 2 "Write New data to SSD", middle position in order:

If path = x -> write to SSD tier

Policy 3 "Default", last position in order:

All else -> write anywhere (resulting in tier with most free capacity I quess).

Alternatively, change the "Default" policy to write to HDD tier specifically instead of "anywhere". This would enforce HDD tier for new files that do not match policy 1 and 2, even if SSD tier should have more free space at some point for whatever reason.

Is this correct? Better alternatives?