Community Guidelines
For public repositories, models and discussions.

1. Where these guidelines apply

Everywhere content on Frazer is public or shared with people outside your organization: public repositories and their files, proposals, reviews, issues and discussions; public models, datasets and apps; releases and packages; profiles, organization pages and comments. They sit under the Acceptable Use Policy, which applies everywhere on Frazer.

2. What we want here

• Be kind and direct. Critique work, not the person. Assume good faith, and say so when you are unsure.
• Make it easy to help. Explain what you changed and why, follow a project’s contributing rules and its AGENTS.md, and keep proposals small enough to review.
• Give credit. Respect licenses, keep attribution, and say where code or data came from.
• Stay on topic. Discussions are for the project. Take personal disputes elsewhere.
• Help newcomers. Everyone started somewhere.

3. Agents as contributors

Frazer lets agents work in public projects. That only works if maintainers stay in control.

• Label it. Work done by an agent carries its provenance: which agent, acting for whom, from which session. Do not hide or remove it to pass agent work off as a person’s.
• Respect each project’s choice. A project can accept agent proposals, accept them only from people it trusts, or not accept them. Follow what it says.
• Review before you send. You are responsible for every proposal your agents open. Send what you would be willing to defend yourself.
• Do not flood. Opening many proposals, comments or issues across projects by automation, without real review, is spam, even when each one looks plausible.
• Answer as yourself. If a maintainer asks a question, a person answers it, or says plainly that an agent wrote the reply.

4. What is not allowed

• Harassment and bullying: targeting a person with insults, unwanted contact, pile-ons, or following them across projects.
• Hateful conduct: attacking people for who they are, such as race, ethnicity, national origin, religion, gender, gender identity, sexual orientation, disability, age or serious illness.
• Threats and incitement to violence, and content that glorifies violent extremism.
• Sexual content involving minors, in any form, and sexual content shared without consent. Other sexually explicit content does not belong in public projects.
• Doxxing and privacy violations: publishing others’ personal data, including their private keys, tokens and credentials.
• Impersonation of people, projects or organizations, including look-alike names meant to mislead.
• Spam and fake activity: bulk or off-topic posts, fake stars, follows or downloads, sock-puppet accounts, and promotion unrelated to the project.
• Malware and active attacks: code built to harm people who did not agree to it. Security research, proof-of-concept exploits and tools are fine when labeled and used for defense, research or teaching.
• Content that breaks the law or someone else’s rights. Copyright claims follow the Copyright and DMCA Policy.

5. Tools maintainers have

Maintainers run their projects. They can:

• set contribution rules, including whether agents may open proposals;
• hide, edit or delete comments, lock discussions and limit who may comment;
• block people from their projects;
• report content to us.

Moderation by maintainers inside their own project is not an appeal against Frazer. If a maintainer’s action itself breaks these guidelines, report it.

6. Reporting

Use “Report” on any public item, or write to abuse@frazer.ai. You do not need an account. A useful report gives:

• the exact link to each item;
• what is wrong, and which rule or law it breaks;
• your name and email address, so we can tell you what we decided (not needed for reports of child sexual abuse material);
• a statement that you believe in good faith that what you say is accurate.

We confirm that we received your report, tell you what we decided and how to challenge it, and say whether automated tools were involved. We read every report. We do not tell the person you reported who you are, unless the law requires it, as with copyright notices.

Intimate images shared without consent

If an intimate image of you, real or computer-generated, is on Frazer without your consent, write to abuse@frazer.ai with “Intimate image removal” in the subject. Include the link to each image, a statement that you are the person shown (or authorized to act for them) and that you did not consent to its publication, your physical or electronic signature, and how to reach you. We remove the image within 48 hours of a valid request, and make reasonable efforts to find and remove identical copies on Frazer.

7. What we do

We look at the content and its context, including whether it is research, news, art or criticism, and choose the lightest action that fixes the problem:

1. Hide or remove the content, or redact a file from a repository while keeping the rest of its history.
2. Warn the account.
3. Limit features for a time: commenting, opening proposals, publishing, or running public CI.
4. Suspend the account, or make a project private.
5. Close the account, for severe or repeated violations.

Severe harm, such as child sexual abuse material, credible threats or active malware, is removed at once, and we report it where the law requires.

When we act, we tell the account holder what we did, which content and which rule, how long the action lasts, whether automation was involved, and how to appeal, unless the law forbids it or telling them would put someone at risk.

8. Appeals and reinstatement

Reply to our notice, or write to abuse@frazer.ai within six months. A person who did not make the first decision reviews it and tells you the result and the reason. If we got it wrong, we restore the content and the account. An account closed for repeated violations can ask to come back after 12 months, saying what has changed.

9. Changes

We update these guidelines as our community grows. Changes are listed on the legal page, with the date and what changed.