跳到主内容
Ciallo
← 服务器文集

Server Constitution · Draft for Review · 34 / 60

Chapter 34: Explaining Backups and Recovery

待审阅草案。本文不代表服务器已正式采用这些entries款,执行范围和权限以现行公告为准。

Text size18
Read at your own pace

Article 331: Purpose and Scope

The shared aim of this chapter is: backup and recovery policies should match actual capabilities rather than reassure players with unlimited promises. Players and administrators must both comply within the actual scope. Identity, familiarity, or past contributions do not create unconditional exceptions. In a dispute, distinguish confirmed facts from assumptions still requiring investigation. Final decisions must not rest solely on popularity, guesswork, or personal likes and dislikes.

Article 332: Normal Participation

Players may do the following: explain existing measures and limits, record recovery decisions, and suggest keeping records of key progress. While undertaking these ordinary activities, still respect current settings and the clear boundaries of the people involved. Without a concrete violation, someone should not be punished merely because another person dislikes a reasonable choice. Administrators may explain and coordinate, but cannot automatically turn a suggestion into an obligation everyone must accept.

Article 333: Prohibited Conduct

This chapter prohibits the following: falsely claiming permanent backups or guaranteed recovery, or encouraging risky actions through guarantees known to exceed actual capabilities. Neither players nor administrators gain exemptions through friendships, contributions, or temporary permissions. Clarify necessary information first where conduct may reflect a misunderstanding. Where evidence is clear and the impact is still expanding, necessary limits may be imposed to prevent further damage, followed by decisions based on confirmable facts.

Article 334: Hypothetical Situation

This chapter uses the following hypothetical situation: an administrator verbally promises recovery of every loss, but no copy covers the relevant period. This illustrates relationships that need investigation; it is not evidence itself. In a real incident, authorization, reminders, mistaken actions, and subsequent corrections must each be checked. Adverse assumptions about someone must be identified as assumptions. An example must not be used to circulate an unconfirmed allegation as established fact.

Article 335: Initial Action

When a relevant problem arises, give priority to the following: correct the promise, check available material, and offer genuinely feasible options. Keep the response within what is necessary to achieve its purpose, avoiding blanket punishment for one dispute. Ongoing harm may be stopped first; matters that have ceased should allow conditions for investigation. Retain a brief reason for important decisions and adjust promptly when later facts change.

Article 336: Evidence and Verification

Relevant material for verification includes: backup availability, record coverage, recovery scope, and original explanations. Check this information against the actual environment rather than selecting only a passage favorable to one side. Everyone involved may identify omissions or differences in understanding; administrators should consider their real relevance to the dispute. If some material cannot be obtained, use other reliable information where possible and explain the actual basis for the conclusion.

Article 337: Scope and Exceptions

When handling special circumstances, note: this draft does not confirm backup frequency or retention periods; new policies should be announced before implementation. Any broader interpretation must be supported by specific facts and a practical purpose, rather than expanded simply for the convenience of the person handling the matter. Changes to published permissions and rules need a clear process for revision and explanation, taking into account the reasonable expectations players have already formed.

Article 338: Communication and Correction

Those involved may submit a concise explanation concerning Explaining Backups and Recovery, stating their understanding of authorization, rules, or facts. Explanations should address the specific issue. An appeal must not be used to continue spamming, insulting, or contacting someone who has clearly refused contact. Administrators should separate the original issue from any new issue arising during the explanation, rather than use a disputed earlier conclusion to silence all further explanation.

Article 339: Corresponding Administrative Duties

Enforcing this chapter requires more than players' self-discipline; administrators must also act consistently and with restraint in matters of Explaining Backups and Recovery. A permission restriction must have an explainable connection to the problem it addresses. After a reasonable correction, promptly review whether the restriction remains necessary. Acknowledge and correct mistakes instead of maintaining an unsupported decision out of fear of losing face.

Article 340: Conclusion and Continued Application

Ultimately, this chapter serves an order in which everyday life can continue, rather than disputes that never end. The phrase to remember is: state only the certainty you have. Address manageable effects through concrete corrections, promptly end restrictions that can end, and clarify conditions for unresolved parts. Revise rules when necessary, with revisions public, understandable, and considerate of expectations for normal participation.

在两部文集中查找

Search涵盖介绍与宪法草案的All正文。

Contact Ender

Say hello, discuss a commission, or send a little kindness. Here's where to find me.

© 2026 Ender · Cat Garden