Skip to content
Community226

Uncertainty

Not knowing something is a normal outcome, not a failure to work around. This site is built so uncertainty is always visible rather than quietly smoothed over — this page covers how to carry that same honesty into an answer.

Say so plainly: “SOLMEME’s documentation doesn’t cover this yet” is a complete, correct, useful answer. It’s more useful than a fluent paragraph built from adjacent facts and general crypto-project conventions, because a confident-sounding guess is harder for the person reading it to catch than an honest “not documented.”

Say what it does answer, and name what it doesn’t. Reference already models this on-page: it explains what the Brand Book/Media Kit/Mascot sections will eventually cover, while stating plainly that none of the three has real content published yet — the reader gets a real, useful answer about scope without being told a specific fact that isn’t actually confirmed.

Don’t silently pick one. Name the apparent conflict and point to Canonical Sources’s resolution rule (the deeper, purpose-built page wins over a page that only mentions the topic in passing) rather than guessing which one is right.