Editorial transparency

Who maintains this project, and what does “reviewed” mean?

Cognitive Biases is an independent public knowledge project maintained by Dzmitryi Kharlanau. The goal is not to make every page sound certain. The goal is to make the source, review state, limits and next useful question visible.

Maintainer

Dzmitryi Kharlanau

Project maintainer and editor. The maintainer is responsible for the project direction, public data contract and editorial workflow. A maintainer credit does not turn the project into an academic institution or make every legacy page independently verified.

Read the methodology See current quality status

What review labels mean

Reviewed is a process claim, not a prestige label.

Evidence-reviewed

The project has checked the public explanation against cited sources and recorded evidence limits and a review date. It does not mean the page is a peer-reviewed paper or a formal systematic review unless stated.

Legacy / generated

Older generated educational material can remain in the library while it waits for evidence review. Generated does not mean independently reviewed.

Research note

Research notes explain what the project found in a source or evidence update and distinguish project interpretation from established findings.

Editorial workflow

How a claim moves toward publication.

  1. Collect a source, correction or research question.
  2. Check source identity, relevance and what the source actually supports.
  3. Compare the source with the current canonical record and conflicting evidence.
  4. Write or revise the explanation in original language with visible limits.
  5. Run editorial, data-integrity and site-quality checks before publication.
  6. Keep review dates and corrections visible so conclusions can change when evidence changes.

Automation and AI

Useful for the workflow, not a substitute for evidence.

Allowed
  • Discover candidate sources and research questions.
  • Prepare drafts, structured data and consistency checks.
  • Run deterministic validation, duplicate checks and build tests.
Not allowed
  • Automatically promote an unreviewed claim to reviewed evidence.
  • Invent sources, findings or certainty to complete a page.
  • Diagnose a person or team with a cognitive bias from limited information.

Corrections

The project should be able to change its mind.

If a source is wrong, a claim is too strong, a relation is misleading or the data contract is inconsistent, corrections are welcome. Evidence-related changes require provenance and editorial review before they change the public evidence state.

Contribution and correction guide ↗