A proposal for the file system

[nuclearfall]

NOTE: I really need to put my computer away in the middle of the night. This is a huge undertaking and I will someday start it in my own little corner of github. I'm going to mark this closed.

Abstraction of a hierarchy agnostic file system which provides self encapsulated elements of component, permission, and member systems:

Component System

• Metadata may include binary data linking low level file system specifics, applications, or may be text with unique identifiers, tags, data types, application references, etc.
• Tags act as a specific form of organizational metadata allowing for a hierarchy agnostic approach to file handling which can associate devices, records, data types and uids.
• Records are containers for data and metadata. Record metadata may refer to one or more applications, contain mixed data types, and be associated with zero or more tags.
• Applications consist of the binaries, data, and metadata necessary to interoperate with and utilize records and other applications using apis and pipelines.
• Systems data includes physical hardware, drivers, the file system, and the operating system. Access may be restricted via blacklists, whitelists, and through the permission system.

Permission System

• Allows for standard permissions of R-W-X for the component system.
• Adds permissions for Protected, Encrypted, and Hidden all system elements.
• Permissions may differentiate between local and remote members and component elements.

Member System

• Members include users and groups and makes a distinction between local and remote members.
• Replaces root user with a primary system operator with self-selected username.
• Sysop usernames may be anonymized via proxy users and group communications.
• Mail is delivered and may be picked up at a central repository by those with permission to do so.
• Maintains a level of security through anonymity and inaccessibility. Out of site out of mind.
• Sysops need not even know the existence or privileges of other sysops.
• SysOps may be accountable for very specific system tasks or sysytem-wide oversight.