Article 8 | Stakeholder Collaboration and Working Group Proceedings

(1) Purpose and Scope: This Article establishes the operational procedures for structuring deliberations, forming session agendas, and facilitating technical and policy collaboration within OpenBharat.net Working Groups (OWGs), without duplicating the identification protocols set out in Article 6.

(2) Agenda Setting and Session Planning: The agenda for any OWG proceeding or review sprint shall be set under the direction of the presiding Technical or Policy Convenor, developed from:

• The defined deliverables and milestones of the working track charter under Article 5;

• Policy inputs, empirical directives, or strategic recommendations submitted by the OBGC, the ISAIL Academic Council, or the Global Advisory Council;

• Urgent technical, statutory, or security issues identified during previous working sprints or open-source testbeds; and

• Direct submissions and issue-tracking pull requests raised by participating stakeholders.

(3) Convenor Discretion and Imperative Prioritization: The presiding Convenors of an OWG may:

• Adopt an iterative, sprint-based agenda to address rapid technological shifts, empirical findings, or code/model vulnerabilities; and

• Prioritize deliberative and drafting items based on their direct relevance to the technical, commercial, legal, and ethical imperatives set out in Schedule 1 of this Charter.

(4) Stakeholder Participation in OWG Sprints:

• Stakeholders admitted under Article 6 may participate in working sprints, code reviews, and policy deliberations corresponding to their domain competence.

• Participating stakeholders may be invited to:

  • Present architectural blueprints, benchmark evaluations, or legal-compliance mappings;

  • Offer technical feedback, pull requests, and documentation improvements; and

  • Participate in consensus-building deliberations under the guidance of the Convenors.

• The OWG Convenors and the OBGC shall endeavor to:

  • Ensure deliberative balance, preventing undue capture or disproportionate influence by dominant commercial platform interests;

  • Provide reasonable notice and repository access for upcoming deliberative sessions; and

  • Maintain adherence to the open-source collaboration norms and intellectual property mandates set out in Article 6 and Article 6a of the ISAIL Charter.

(5) Recordkeeping and Repository Archiving: The Secretariat, in coordination with the OWG Convenors, shall maintain records of working group collaboration, which may include:

• Roll calls and participant registries for formal sessions;

• Minutes of proceedings, consensus notes, and dissenting technical opinions;

• Public issue trackers, pull requests, Contributor License Agreements (CLAs), and written submissions; and

• Conflict-of-interest declarations filed under Article 4 of the ISAIL Charter.

(6) Lifecycle Milestones: Substantive stakeholder input shall be formally recorded at pivotal junctures across the standardisation lifecycle established under Article 5:

• Inception & Scoping: Consolidating baseline problem statements, architecture requirements, and initial stakeholder submissions.

• Drafting & Prototyping Review: Documenting technical resolutions, benchmark results, and iterative revisions.

• Final Ratification Review: Certifying that deliberating stakeholders had the opportunity to review candidate specifications prior to formal clearance under Schedule 2 of the ISAIL Charter.

(7) Working Session Administration: To maintain technical rigor and prevent procedural gridlock, the OWG Convenors, with the concurrence of the OBGC, may:

• Structure proceedings into specialized sub-tracks or focused drafting sprints;

• Rebalance session attendance based on subject-matter relevance to specific agenda items; and

• Delegate specific drafting or benchmark testing assignments to designated Academic Members or technical contributors.