Attacking the claims is the work. Attacking people is not.
That single line is the whole of it. Everything below is detail.
Nova-Violet Role builds tools that make measurable assertions — theorem counts, exit codes, timings, "this gate has a negative control". We publish those numbers so that anyone can falsify them. A community organised around falsifiable claims only works if the claims are what get attacked.
- Proving a claim in our documentation is false. This is the most welcome contribution there is, and it has its own issue form.
- Showing that a test, gate or proof is vacuous — that it passes whether or not the property it names holds.
- Arguing that a design is wrong, that a benchmark is unrepresentative, or that a licence choice is a mistake.
- Saying "I could not reproduce this", and being taken seriously for it.
- Disagreeing with a maintainer, in public, at length, with evidence.
Nothing on that list is rudeness. A person who breaks our build and shows the receipt has done us a service, and will be thanked for it in the changelog.
- Harassment, intimidation, or sustained hostility toward a person.
- Slurs or demeaning language about anyone's identity — including but not limited to age, body, disability, ethnicity, sex characteristics, gender identity or expression, experience level, education, socio-economic status, nationality, appearance, race, caste, colour, religion, or sexual identity.
- Sexualised language, imagery, or attention of any kind.
- Publishing anyone's private information without their explicit permission.
- Deliberately wasting contributors' time: knowingly false reports, fabricated measurements, or output pasted as if it had been run when it had not.
That last one belongs on this list and not in a style guide. A fabricated measurement is a conduct problem, not a technical one. Our entire method rests on numbers being real. Inventing one is the only way to genuinely poison this community, and it is treated with the same seriousness as any other breach.
You will never be penalised here for:
- not knowing something,
- not being able to verify a claim on your platform,
- opening a report that turns out to be your own configuration,
- writing "I could not check this" in a pull request.
An honest gap is a result. A fabricated green is not. If you are unsure, say so plainly and ship the uncertainty with the work. That is the culture, and it is enforced in your favour.
This applies in every space the organisation runs — issues, pull requests, discussions, commit messages, code review, releases — and whenever someone is representing Nova-Violet Role in public.
Report a breach privately to the organisation owner:
- open a private security advisory on the affected repository (this works for conduct reports too, and is the most private channel we have), or
- contact @Saimonokuma directly on GitHub.
Reports are read by the organisation owner. You will get an acknowledgement. If your report concerns the owner, GitHub's own abuse reporting is the correct route and using it is not disloyal — it is the designed escalation path.
Responses, in order of severity:
| Response | |
|---|---|
| 1 | A private note naming the behaviour and what to do instead. |
| 2 | A public correction on the thread, and a warning. |
| 3 | A temporary block from interaction with the organisation's repositories. |
| 4 | A permanent ban. |
We will say which one we applied and why. An enforcement action that cannot be explained is not one we will take.
Adapted from the Contributor Covenant, version 2.1, with additions specific to a project whose claims are meant to be attacked — sections 1, 3, and the fabricated-measurement clause in section 2 are ours and are not part of the Covenant.
Nova-Violet Role · Reality is the judge.