Article 18 | Obligations for Alliance Members

(1) General Obligations: All Alliance Members, regardless of tier, category, or fee-exemption status, shall adhere to the following mutual commitments:

• Constitutional Compliance: Comply with this Charter, the Bharat Pacific Principles of AI Standardisation, the ISAIL AI Principles, and the governing provisions of the ISAIL Charter.

• Active Open Collaboration: Participate regularly in OpenBharat.net activities, working sprints, and technical consultations, contributing code, empirical data, architectural insights, or policy expertise to advance sovereign AI infrastructure.

• Responsible Disclosure and Safety Reporting: Promote model safety, algorithmic audibility, and vulnerability management by responsibly disclosing critical system flaws, edge-case failures, or alignment vulnerabilities identified within shared testbeds or open codebases.

• IP and Licensing Discipline: Honor the open-source licensing designations, Contributor License Agreements (CLAs), and attribution rules established under Article 6 of this Charter and Article 6a of the ISAIL Charter, respecting upstream dependencies and preserving the public commons.

• Confidentiality and Operational Trust: Safeguard sensitive pre-release benchmarks, unannounced security vulnerability disclosures, and proprietary compute infrastructure data shared in confidence within restricted working tracks.

• Financial and Resource Integrity: Remit applicable tier fees under Article 14 on time, or actively fulfill verifiable technical contribution metrics where holding fee-exempt Contributor status.

(2) Special Obligations for Fee-Exempt and Contributor Tier Members: In exchange for full fee waivers, entities admitted under the Alliance Member (Contributor) track or receiving fee exemptions under Article 14 and Article 17 shall undertake the following operational commitments:

• Public Commons and Open Code Contributions: Actively commit, document, and maintain at least one open-source technical deliverable, benchmark evaluation harness, or architectural reference implementation within an OpenBharat.net Working Group (OWG) repository.

• Empirical and Safety Case Studies: Furnish reproducible test results, red-teaming summaries, or deployment post-mortems from their real-world implementations to enrich the collective safety baseline of the ecosystem.

• Developer Mentorship and Ecosystem Enablement: Contribute technical maintainers, lead code reviews, or facilitate community workshops, hackathons, and regional training tracks to help onboard independent developers and student researchers into sovereign AI architectures.

• Regional Diffusion and Sandbox Participation: Make reasonable efforts to test candidate specifications, neurosymbolic tools, or open-weight models within localized environments and regional diffusion testbeds.

(3) Monitoring, Sanctions, and Enforcement:

• The OpenBharat.net Governing Council (OBGC), supported by the ISAIL Secretariat, shall periodically monitor compliance with the obligations set out in this Article through transparent repository activity tracking, CLA verifications, and sprint participation audits.

• Where an entity persistently fails to satisfy its contribution obligations, acts in bad faith, or engages in proprietary enclosure of open-source assets, the OBGC may, following a fifteen (15) day notice period:

  • Issue a private cure notification specifying required technical remediations;

  • Revoke fee-exempt status and reclassify the entity to standard dues under Article 14; or

  • Suspend or formally terminate Alliance Membership and associated Working Group convenor standing.