The value of this wiki depends entirely on its reliability. A wiki that contains both accurate technical guidance and unchecked speculation is less useful than one that contains only the former. These policies exist to protect quality - not to restrict contribution.
Neutral, practical tone. This is a technical reference, not an advocacy site. Write as if advising a technically capable friend who needs accurate, actionable information - not as if writing a manifesto.
Claims require sources. Link to primary sources (official documentation, peer-reviewed research, verifiable community practice) inline on each page. Do not state capabilities or failure modes without evidence.
No speculation as fact. If something is uncertain, say so. Use language like "may," "in some configurations," or "reports suggest" - not "will" or "is."
Scope enforcement. Content must address a defined threat scenario from the Foundations threat model and remove a named dependency. Content that does not answer "what dependency does this remove?" is out of scope.
No vendor capture. If a page recommends a single vendor without comparison, it needs a justification. Prefer open-source, community-supported, or multi-vendor options.
Source requirements. Peer-reviewed sources, official documentation, or verifiable community practice. Personal experience is acceptable as supporting evidence, not primary evidence.
Contested claims. When editors disagree on a factual claim: add a note on the talk page, link to both positions, and escalate to a trusted editor if unresolved after 72 hours.
Outdated content. Pages with time-sensitive information (specific software versions, pricing, hardware availability) should be reviewed annually. Use the [STALE] tag to flag pages that may be outdated.
Testing requirements. Project and blueprint pages should only be published after the described build has been completed and tested by at least one contributor.
No hard ownership. Any registered user can improve any page. Ownership of a concept or project does not entitle anyone to veto improvements.
Trusted editor review. High-stakes pages (homepage, core principles, scorecard domains) require review by a trusted editor before publication.
Trusted editor nomination. Any user may nominate themselves or another. Criteria: 10+ accepted edits, no policy violations, demonstrated domain knowledge. Approved by existing trusted editors by simple majority.
In scope:
Out of scope: