Compleet
2.2 KiB
Editorial commitments
This document is public because the publication should be judged against promises a reader can inspect. It is a working policy, not a claim of infallibility.
Voice
We ask one recurring question with cheerful suspicion: when a system claims to be verified, trustless, sovereign, private, safe, or autonomous, what does that mean in practice and where did the trust move?
Stories begin with people and consequences. Technical machinery is explained in plain English. Jargon is defined when it is first used. Outrage is reserved for what the evidence supports.
Authorship and maintenance
An author and a maintainer are different roles. Every published item identifies its author. Maintained material also names the person responsible for review.
Git records provenance and revision history. It does not certify truth, fairness, completeness, or independence. Those remain editorial responsibilities.
Corrections and challenges
Corrections are attached to the relevant passage, dated, and described plainly. Substantive changes are not silently folded into a story.
Public challenges should identify the passage, objection, and supporting basis. First-hand testimony can be evidence. Sensitive material must use a private channel rather than a public issue.
An article-level disputed status is used only when the dispute materially changes how the whole article should be read. A challenge to one passage does not automatically label an entire story disputed.
Sources and safety
This public repository never contains confidential source identities, unpublished interview notes, private contact information, embargoed drafts, or documents whose publication could endanger a source. Public source links belong in the relevant article; protected reporting material belongs elsewhere.
Conflicts and commercial boundaries
Relevant financial, professional, and personal conflicts are disclosed. Sponsorship never buys inclusion, favourable treatment, access to corrections, or influence over review status.
Review dates
A last reviewed date means a named maintainer genuinely checked the material on that date. It is not updated mechanically to make an archive appear fresh.