How we treat each other.
Disagreement with ideas is welcome and expected. Attacks on people are not. The conference and its review process do not tolerate harassment, discrimination, or personal attacks.
Where this applies.
This applies to the conference in Port of Spain, 28–31 October 2026, including the field day at the Pitch Lake. It applies to authors, reviewers, speakers, organizers, and anyone attending. It applies to the public repository, to reviews and author responses, to this website, and to email sent to the conference.
It also applies to the Studio form and to mail sent to roger@algorithmacy.org. Studio is a separate practice. The same rule about people stands there: a commercial conversation is not a license to harass.
What we expect.
Critique the work, not the author. Public reviews need more care than a private note, because the author and the audience can both read them. Argue the claim, the method, and the evidence.
Give people room to take part. That includes speakers, students, worker representatives, and anyone who has traveled to be in the room. Do not publish someone else’s personal contact details beyond what a submission already places in the public record on purpose.
What we do not accept.
Harassment, discrimination, and personal attacks are grounds for removal from the program. That includes slurs, sexual attention that is not welcome, intimidation, and sustained interruption of someone’s talk or review. It includes doing those things in a hallway, at the reception, on a pull request, or by email.
A sharp disagreement about a paper is not, by itself, a breach. The test is whether the remark is about the work or about the person.
How to report it.
Write to Roger Hunt at rhunt@bentley.edu. Say what happened, when, and who was involved, as far as you are willing. You do not have to make a public GitHub issue. Those issues are public, and a conduct report should not have to be.
If the report is about the person who reads that mailbox, write to roger@algorithmacy.org instead and say that you want it handled apart from the conference inbox.
What happens next.
We will read the report, tell you we have it, and do something that matches what happened. That can include a warning, removing someone from review, declining or closing a submission that is an attack rather than a contribution, ending a Studio conversation, or asking someone to leave the event.
A pull request that is already public can be closed. GitHub history may still show it. We will not promise a particular timetable, and we will not publish the report itself.