Wick is a thinking partner. The community around it should reflect that.
Direct, warm, and zero patience for bad-faith argument. Disagreement is welcome — disagreement that wastes everyone's time is not.
In practice:
- Critique the work, not the person. "This skill is too narrow" is fine. "You don't understand skills" is not.
- Steelman before you argue. If you're about to say someone's wrong, restate their position in its strongest form first. If you can't, you don't yet understand it well enough to argue.
- Cite when you claim. "Tetlock found X" without a paper / page is rumor. "I think X because Y" is fine — "X is true" without backing is not.
- Admit uncertainty. "I don't know" is a complete answer. "I'm not sure but my best guess is…" is even better.
- No bigotry, harassment, or doxxing. Self-evident. Reports go to contact@agoradynamics.dev.
- No spam, marketing, or LLM-generated low-effort PRs. If your PR or issue could have been a tweet, post it as a tweet.
Anyone interacting with the Wick repo, community channels, or Wick's named maintainers in their Wick capacity. Contributors, reviewers, issue reporters, discussion participants.
- First offense for low-stakes issues — a comment from a maintainer pointing at this file. Almost always sufficient.
- Repeated or higher-stakes issues — temporary block from the repo (issues + PRs).
- Severe issues (harassment, doxxing, threats) — permanent block, with a public explanation if appropriate, no public explanation if appropriate.
Maintainers are expected to apply this standard to themselves first. Power doesn't suspend it.
Email: contact@agoradynamics.dev with subject [wick-conduct]. Reports are confidential.
If a report names a maintainer, it goes to the other maintainers, not back to the named one.
This document is itself MIT-licensed and adapted from common open-source patterns (Contributor Covenant, etc.) plus Wick's own voice rules. Reuse it freely.