File is File not exclusively because it has to do with files (though file-related actions should also be there) but because of relative significance versus the other menus

In the "File" menu you are doing something that has the potential to fundamentally alter the app you are using, by tampering with (typically a large portion or even all of) the data files it contains, or by resetting the state of a running session (file > new window in browsers)

"Edit," semantically, is the same but for a subset of that data, often only a single piece of data. Here I'll sustain that the "create a singular new password/event" button could be under Edit, not File, since those are not actions scoped to the whole app or to the filesystem, instead only to individual records in a database.

"View" is read-only and actions under here should not write anything anywhere. And so on.

Please do not abandon decades of UX tradition in favor of inserting tautologies into your programs.

(1Password/Passwords, Automator/Automations, really? might as well put a pictogram there rather than duplicate the word - I already know what the app does, I want the UI to signal what scope my actions are applying to)

"Project" for DaVinci Resolve makes sense, probably because it's a synonym lol