The AIDDLC Standard is a technical standards community. The conduct standards here reflect that purpose: they are designed to enable precise, evidence-based, good-faith technical work. They are not designed to enforce a particular social atmosphere.
Precision: Make specific, grounded statements. Vague commentary ("this seems off", "I'm not sure about this") is not a contribution. If something is wrong, identify what is wrong, cite the relevant section, and propose what would be better.
Directness: Say what you mean. Diplomatic indirection wastes everyone's time. Disagree explicitly, argue clearly, and accept decisions gracefully when the process has run its course.
Evidence-based argument: Support your positions with evidence. Acceptable forms of evidence include: implementation experience (with specifics), regulatory text or guidance, research, examples from practice, logical consequence of agreed principles. "In my opinion" is not evidence; "in my implementation, I found that..." is.
Good faith engagement: Assume that other participants are trying to improve the standard, even when you disagree with them. Engage with the argument, not the person.
Respect for process: The contribution process exists for good reasons. If you disagree with a decision, use the process to appeal or propose an alternative — do not circumvent it.
Personal attacks: Criticism of a person rather than their argument. This includes: insults, mockery, attributing bad motives, disparaging professional background, and all forms of harassment.
Vague criticism: Criticism without specific content. Every negative statement about a proposal must include: what is wrong, why it is wrong, and what would be better. Vague objections that do not meet this standard will be disregarded.
Bad-faith engagement: Participating in the process to obstruct rather than to improve. This includes: bad-faith appeals, deliberately misreading proposals, using process as a harassment vector, and submitting proposals with no genuine intent to engage with the review.
Harassment: Any behaviour intended to intimidate, coerce, or cause distress to another participant. This applies in all spaces associated with the AIDDLC Standard, including GitHub, email, and any other communication channel.
This code of conduct applies to all spaces managed by the AIDDLC Standard organisation, including:
- GitHub repositories (issues, pull requests, discussions, comments)
- Email correspondence to aiddlc.ai addresses
- Any events or forums where an individual is representing the AIDDLC Standard
Reports of conduct violations should be sent to conduct@aiddlc.ai with:
- Description of the behaviour
- Links or screenshots if applicable
- Your preferred outcome (if any)
Reports are treated confidentially. The reporter's identity is not disclosed to the subject of the report without explicit consent.
We will acknowledge reports within 5 business days.
- First instance: Written warning from a board member, identifying the specific behaviour and the conduct standard it violates.
- Second instance: Temporary suspension of contribution rights (period determined by severity: 30–90 days).
- Third instance, or severe first instance: Permanent removal of contribution rights.
Severe first instances (including harassment, doxxing, or targeted bad-faith campaigns) may proceed directly to permanent removal without prior warning.
Enforcement decisions may be appealed by emailing governance@aiddlc.ai within 30 days of the decision. Appeals are reviewed by a board member not involved in the original decision.
Maintained by 10QBIT Technologies · aiddlc.ai