Community Governance Charter

link to this sectionCommunity Governance Charter

Effective 2026-08-31 for Public Preview. Community ratification and named stewards are required before Public Beta.

This charter defines the intended boundary. It does not claim that a three-person steward group, quorum, election process, or moderation rotation is already active. Named stewards, decision procedures, conflict rules, contact routes, and real ownership must be published before Public Beta.

link to this sectionAuthority

The intended community steward body governs ordinary project admission, content policy, moderation review, appeals, and collaboration rule changes. Project maintainers govern roles and scope within their projects, subject to network policy. Research conclusions remain attributable claims and evaluations, not platform votes.

link to this sectionDecisions and conflicts

• Record the question, policy, evidence, participants, conflicts, decision, and review date.
• Require at least two participating stewards for ordinary Beta decisions.
• Require a materially conflicted person to disclose the conflict and not decide the matter.
• Prefer narrow, reversible access controls and preserve the audit trail.
• Explain and permit appeal unless law or safety prevents disclosure.

link to this sectionEmergency platform authority

Platform operators may act without prior community approval only for credible legal, security, privacy, safety, or infrastructure emergencies. The action must record its reason, operator, time, scope, and follow-up review. Emergency authority cannot declare research true, erase disagreement, create competitive visibility, or quietly alter signed history.

Governance actions use discovery, access, and download overlays. Required Artifact removal uses a tombstone and content hash. An appeal should be reviewed by people who did not make the initial decision when enough eligible stewards exist.

During Public Preview, governance review requests reach maintainers at yuunagi.cn@outlook.com.