Guard by Default

Would it not be cleaner and use 1 less mapping if we were to set a default state variable, for example, defaultGuard = True
Then you only need to maintain a single list of excaptions to the default,
so if the default is Guard unless allowed, then the mapping would contain a white list, if the status is Allow, then it would be a black list.
Of course, having more states than a single logic would work, I just feel having 2 address arrays is additional storage that is not space efficient, and what would happen if a Single address managed to get into both lists? My years of development have taught me to only have single source of truth.

No files or tests are named. Start by reviewing the DSGuard and DSAuthority behavior described by the repository, then determine whether a default guard state with one exception list preserves the authorization semantics. Done means reaching and documenting a clear design decision about replacing the two address mappings and handling addresses present in both.

Written by the indexing model from the issue text.