Design Document: Security Department #399
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR includes a rewrite of the Security Department design document, following the template from #397. It's originally based on a proposal by @keronshb.
This is a directional design document, meaning the goal is to define boundaries and goals for the game area (in this case, the Security department). It is not aiming to provide specific mechanics or implementations, and instead act as a guidance for future PRs in this area, both for contributors when making PRs and Maintainers when evaluating them.
Should this PR be merged it will act as a reference point for future departmental and game area design docs, as an example for how a directional documents should look.