Skip to content

Latest commit

 

History

History
71 lines (51 loc) · 2.01 KB

File metadata and controls

71 lines (51 loc) · 2.01 KB

Code of Conduct

IX-Vahdat is a humanitarian water-resilience proof-of-concept. The project should remain serious, respectful, evidence-first, and safety-bound.

Expected Behavior

Contributors and participants are expected to:

  • communicate respectfully
  • preserve humanitarian intent
  • stay factual
  • identify uncertainty clearly
  • avoid exaggeration
  • avoid political targeting
  • avoid country-specific prescriptions
  • respect local authority and community review
  • treat water safety as high consequence
  • prioritize human review over software confidence

Unacceptable Behavior

Unacceptable behavior includes:

  • harassment or threats
  • discriminatory language
  • knowingly false technical claims
  • fake data or fake field measurements
  • unsafe water-safety claims
  • pressure to remove review gates
  • pressure to bypass local public-health or engineering review
  • turning the project toward weapon, surveillance, or coercive use
  • using the project to target a population, nation, agency, or group
  • presenting synthetic examples as real deployment evidence

Technical Disagreement

Technical disagreement is welcome.

When disagreeing, focus on:

  • evidence
  • assumptions
  • test behavior
  • risk boundaries
  • failure modes
  • review requirements
  • safety consequences

Do not attack contributors personally.

Humanitarian Neutrality

IX-Vahdat should support drought-stressed and infrastructure-stressed communities generally.

It should not become:

  • a geopolitical directive
  • a propaganda tool
  • a sanction-bypass tool
  • a military project
  • an intelligence project
  • a replacement for local governance
  • a replacement for public-health authority

Enforcement

Maintainers may close, reject, or revert contributions that violate the project’s safety boundaries, humanitarian scope, or respectful collaboration expectations.

The safest default is simple:

When water, public health, infrastructure, or emergency reserves are involved, software should hold or block unless evidence and human review are strong enough to continue.