Schedule 2 – Outcome Document Drafting Guidelines for Committees

General Metadata and Identification Guidelines

(1) Every outcome document, specification sprint deliverable, or formal summary report shall include a metadata header specifying:

• Document Title and Primary Track (such as Policy & Governance, Engineering & AI Systems, or Strategic & Sovereign Systems);

• Working Group designation and session or sprint topic;

• Publication date and release status (pursuant to Article 9 classifications);

• Presiding Technical Convenor or Policy Convenor;

• Contributing maintainers, editors, and participating member entities; and

• Semantic versioning tag and canonical URI or repository commit hash.

(2) Document Numbering Syntax: Deliverables must follow the standardized OpenBharat.net sequence to ensure chronological continuity:

• Policy & Governance Track (formerly Policy Innovation Committee):

  
  

  OPENBHARAT-POL-[4-digit sequence]-[YYYY]

• Engineering & AI Systems Track (formerly AI Development Committee):

  
  

  OPENBHARAT-ENG-[4-digit sequence]-[YYYY]

• Strategic & Sovereign Systems Track (formerly Strategic Affairs Committee):

  
  

  OPENBHARAT-STR-[4-digit sequence]-[YYYY]

• Joint Inter-Track Deliverables:

  
  

  OPENBHARAT-JNT-[4-digit sequence]-[YYYY]

(3) For documents transitioning from or updating legacy AiStandard.io publications, the header must explicitly cross-reference the corresponding legacy identifier (such as AISTANDARDIO-ADC-[xxxx]) to preserve citation integrity.

Core Structure of Outcome Documents

(1) Scope and Problem Statement: Clearly state the technical, regulatory, or operational issue addressed during the sprint or session, ensuring direct alignment with the Working Group's track mandate.

(2) Technical Observations and Empirical Baselines:

• Detail experimental results, architecture demonstrations, code evaluations, or regulatory analyses.

• Include benchmark figures, testing parameters, and reproducible data where software prototypes or model weights are reviewed.

• Document feedback, design objections, and technical tradeoffs raised by participating contributors.

(3) Actionable Outcomes and Deliverables: Summarize actionable next steps using clean bulleted lists, categorized into:

• Repository merge targets and pull request assignments;

• Normative drafting assignments and standard clause revisions;

• Empirical sandboxing or compute testbed schedules; and

• Outstanding blockers or security disclosures referred to the OBGC.

Formatting and Citation Protocol

(1) Documents must be composed in clean, parseable Markdown or approved standard publication templates using consistent structural typography.

(2) Inline references and footnotes must provide direct hyperlinked citations to open code repositories, academic DOIs, or official statutory notices.

(3) Outcome documents must conclude with an Artifacts and Session Records section providing persistent URLs to code branches, recorded deliberations (where classified as public), and related OPENBHARAT references.

Track-Specific Focus Areas

Policy & Governance Track (OWG-POL)

• Focus on statutory alignment, legal doctrine, model auditability, safety standards, and algorithmic transparency.

• Capture regulatory and ethical tradeoffs identified by stakeholders, avoiding generic rhetoric in favor of enforceable specifications and compliance metrics.

• Maintain a dedicated Regulatory Interoperability section evaluating cross-border and domestic legal impacts.

Engineering & AI Systems Track (OWG-ENG)

• Focus on working prototypes, neurosymbolic architectures, compute optimization, open-weight tooling, and developer infrastructure.

• Document real-world demonstrations in detail, recording architecture diagrams, library dependencies, compute constraints, and deployment lessons learned.

• Include reproducible test runs, error-handling observations, and safety red-teaming evaluations.

Strategic & Sovereign Systems Track (OWG-STR)

• Focus on domestic compute autonomy, supply chain resilience, sovereign foundation models, and regional geopolitical technology dynamics.

• Deliver concise, actionable situational analyses evaluating infrastructural vulnerabilities, high-risk operational scenarios, and sovereign testbed deployments.

• Frame technical recommendations directly around domestic capacity building, critical infrastructure safety, and non-aligned international technology standardisation.