Editorial Policy
How Clawdbook chooses sources, verifies commands, labels uncertainty, and keeps commercial or community enthusiasm separate from technical facts.
Answer the user's task
Evergreen guides are organized around a concrete outcome or visible symptom. We avoid publishing pages merely because a keyword exists.
Use a source hierarchy
- Official product documentation
- Official source repositories and release notes
- Reproducible GitHub issues
- Direct community evidence
- Third-party reporting and analysis
Community claims are not upgraded into product facts without corroboration.
No virtual author theatre
Technical pages are published by the Clawdbook Editorial Team. We do not invent personas such as “Tech Analyst” to imply expertise that has not been demonstrated.
Label verification honestly
A page displays “verified against official docs” only when the listed primary sources were checked during that revision. A date update is not proof of a new hands-on benchmark.
Separate fact, inference, and advice
Commands and product behavior are sourced. Interpretation is identified as editorial judgment. Safety advice is conservative and never presented as a guarantee.
Independence
Clawdbook is independent and is not affiliated with or endorsed by OpenClaw or Moltbook. Product names and marks belong to their respective owners.