Article 7 | Use Case Classification, Tracking and Risk Analysis

(1) Institutional Responsibility & Discretion: The classification, empirical tracking, and risk assessment of use cases under this Article may be undertaken by the relevant OpenBharat.net Working Group (OWG) charged with the technical track, or conducted directly under the supervisory discretion of the OpenBharat.net Governing Council (OBGC).

(2) Ecosystem Classification: An OWG or the OBGC may evaluate and categorize use cases across relevant sectoral and ecosystem tiers, including:

• Start-ups & Scale-ups: Autonomous, early-stage, or high-growth ventures deploying domain-specific AI models or architectures.

• MSMEs & Industrial Users: Micro, small, and medium enterprises adopting or embedding AI systems into production, operational, or trade workflows.

• Research Laboratories & Academic Testbeds: Initiatives originating from academic institutions, private foundational research centers, or sovereign testbeds.

• Open-Source & Developer Collectives: Community-driven repositories, independent practitioner projects, and decentralized computational efforts.

• Public Interest & Social Infrastructure: Compute or algorithmic deployments addressing civic administration, accessibility, and public service delivery.

(3) Problem Typing and Doctrinal Triage: An OWG or the OBGC may categorize use cases across critical functional problem domains, including but not limited to:

• Technical Viability & Architecture: Inherent computational limits, neurosymbolic integration bottlenecks, open-weight stability, and inference latency.

• Regulatory & Compliance Alignment: Interactions with statutory data protection rules, emerging national AI guidelines, and liability exposure.

• Adjudicatory & Doctrinal Questions: Complex legal questions surrounding training-data lineage, intellectual property authorship, evidence admissibility, and model explainability.

• Infrastructure & Compute Access: Hardware dependencies, sovereign cloud limitations, distributed compute constraints, and energy efficiency.

• Market Distortion & Ecosystem Capture: Monopolistic API dependencies, proprietary platform lock-in, and commoditization risks facing domestic developers.

(4) Imperative Alignment: An OWG or the OBGC may evaluate and record how a candidate use case maps to the technical, commercial, legal, and ethical imperatives established under Schedule 1 of this Charter.

(5) Risk Assessment Framework: When deemed necessary for open standardisation, deployment benchmarking, or model safety guidelines, an OWG or the OBGC may perform a risk analysis assessing:

• Technical Risks: Implementation complexity, non-deterministic failure modes, data drift, security vulnerabilities, and adversarial robustness.

• Operational & Resource Risks: Infrastructure switching costs, dependencies on non-sovereign compute clusters, and developer talent deficits.

• Compliance & Liability Risks: Cross-border transfer conflicts, regulatory reporting mandates, statutory non-compliance, and tortious liability exposures.

• Ecosystem Sustainability Risks: Proprietary wrapper obsolescence, downstream licensing revoking, and open-model dilution.

(6) Mitigation Strategies & Cross-Cutting Factors: An OWG or the OBGC may formulate and document mitigation strategies addressing systemic intersections, such as the convergence of algorithmic auditing with trade-secret protection, or balancing open-weight dissemination with malicious-use guardrails.

(7) Discretionary Records and Tracking Dossiers: An OWG or the OBGC may maintain working records for prioritized use cases, which may encompass:

• The technical rationale behind assigning the use case to a specific OWG track;

• The documented alignment with the Schedule 1 imperatives;

• Risk-matrix summaries and associated engineering or licensing countermeasures; and

• Milestone updates reflecting changes in model capability, compute topology, or statutory environments over the standardisation lifecycle.