Article 181: Purpose and Scope
The purpose of this chapter's rules is: shared builds should respect contributions, agreements, and the right to leave; project leaders cannot monopolize interpretation. For a specific matter, first establish how the behavior actually relates to this purpose. The provision's name cannot replace an assessment of facts. Be able to explain the permissions, people, and scope of effects involved. A setting not confirmed by an official announcement must not be guessed on the spot and used to declare a violation.
Article 182: Normal Participation
This chapter preserves the following ordinary choices: build according to divided tasks, record handovers, discuss changes, and clearly attribute references. Where several approaches are possible, explain which parts are mandatory boundaries and which are negotiable. Ordinary refusal, reasonable questions, and suggestions for improvement do not automatically amount to defying administrators. Activities involving another person's permissions or property require further confirmation of the relevant consent.
Article 183: Prohibited Conduct
The following conduct crosses this chapter's boundaries: claiming all results, unilaterally overturning shared plans, or retaining personal items because someone leaves. Decisions must address conduct that actually occurred and the corresponding rule. Reasonable criticism, normal departure, and different interests must not be labeled violations. The person acting must stop ongoing effects, while administrators must keep reasonable explanation and review available. Both obligations should be respected together.
Article 184: Hypothetical Situation
As a hypothetical example: a leader displays a bridge publicly but removes contributors' names and keeps a departing teammate's tools. This example helps explain the rule; it does not mean a similar event has occurred on the server. Investigators should distinguish actual conduct, the information each participant had, and provable effects. Apparent similarity to an example must not replace confirmation of the present facts and relevant authorization.
Article 185: Initial Action
This chapter's basic approach is: check contributions and ownership, restore attribution, and handle actual handovers and improper retention. Those involved should cooperate in preventing further effects, and administrators should explain whether the current measure is temporary or final. If all facts cannot yet be established, matters requiring further investigation may remain open. Uncertainty must not become an indefinite excuse for failing to explain or respond, or for arbitrarily expanding authority.
Article 186: Evidence and Verification
Before reaching a judgment, examine: task records, building instructions, reference sources, and handover lists. Keep and use material only within the necessary scope. Do not supply unrelated details to spectators or automatically treat refusal to disclose private information as noncooperation. Logs and screenshots each have limitations. State what they establish, and do not present what they cannot establish as beyond doubt.
Article 187: Scope and Exceptions
A specific clarification of scope: unfinished contributions may also be recorded; attribution disputes do not automatically determine land ownership. Explain exceptions in terms of real needs; they must not become permanent private privileges attached to an identity. For situations this chapter does not fully cover, first consult relevant basic principles and current announcements, proposing revisions if needed. Avoid inventing unforeseeable new obligations and punishing past behavior under them.
Article 188: Communication and Correction
In disputes concerning Shared Projects and Attribution, communication should center on verifiable facts. The person receiving a reminder should first stop expanding the impact, then organize what needs clarification. Those handling the matter should also accept genuine supplementary material. Issues that can be resolved through clear explanation and appropriate correction do not require continued public humiliation to maintain supposed authority.
Article 189: Corresponding Administrative Duties
Administrative explanations concerning Shared Projects and Attribution should be clear and checkable, especially the grounds currently in force and the actual scope of the response. Demands unrelated to this chapter's purpose should not be mixed into necessary action. Important results may be published to the extent needed, while private details remain controlled. Answer players' reasonable questions with specific grounds rather than end discussion by invoking status.
Article 190: Conclusion and Continued Application
When concluding a matter, confirm completed corrections, unfinished handovers, and whether explanations need updating. This chapter's reminder is: a bridge built together should retain everyone's names. This helps explain everyday boundaries; it does not replace evidence and procedure. Rules should spare later players the same misunderstandings and let resolved problems truly end rather than become permanent labels for attacks.