Soft deletes now use a time representation for “deleted at” - this can be a datetime or an integer seconds-from-epoch. Given that it is now an ordered column an index makes more sense - BUT a key piece of info is that it is nullable and standard find() queries will be “IS NOT NULL”, so it is sort of still functioning like a boolean.
I’m not a DBA but I was told to index “anything that is searched against regularly” and this field will probably be hit even more than primary for any models using these tables - hence the question!