Consider the following : 1. Aarogya Setu 2. CoWIN 3. DigiLocker 4. DIKSHA Which of the above are built on top of open-source digital platforms ?

States a government policy pattern: new digital public infrastructure for agriculture will be built as open source, open standard and interoperable public good.

A student could infer that similar central policies or preferences for open-source/open-standards might apply to other recent government digital public goods (like health apps) and then check whether Aarogya Setu follows that pattern.

Mentions the National Digital Health Blueprint/National Digital Health Mission as the governmental digital health implementation framework.

One could check whether Aarogya Setu was developed under or aligned with this national digital health framework and whether that framework mandates open-source platforms.

Describes a broader government emphasis on building Digital Public Infrastructure (JAM Trinity etc.) as a repeatable model for public digital goods.

A student could use this pattern — that the government builds centralized digital public infrastructure — to investigate if Aarogya Setu was released as part of such infrastructure and whether those infrastructures are open-source.

Gives an example of a government 'portal' (Stand-up India) described as a digital platform built to support public programmes.

Use this example to reason that many government services are implemented as platforms/portals and then check whether the health-sector equivalent (Aarogya Setu) followed the same build-model and its licensing/open-source status.

Describes multiple government-led digital platforms for skilling and workforce mapping (PRIME, ASEEM) illustrating a pattern of creating sectoral digital platforms.

Compare these platform examples to Aarogya Setu to see if the health platform was similarly structured and whether those platforms were open-source or proprietary.

States that digital public infrastructure for agriculture will be built as open source, open standard and interoperable public good — indicating a government policy/precedent favoring open-source DPIs.

A student could infer the government’s stated preference for open-source DPIs and check whether CoWIN, as a national DPI for vaccination, follows the same policy (e.g., by looking for public code repositories or policy documents).

Mentions implementation of a National Digital Health Blueprint/National Digital Health Mission, showing that the government plans structured, centralized digital health platforms.

Using basic knowledge that CoWIN is a national health IT service, a student could compare CoWIN’s architecture to the Blueprint’s open/standards guidance to see if it aligns with open-source principles.

Describes the Stand-up India portal as a government digital platform built to support services — an example that Indian government often uses dedicated digital portals for national schemes.

A student can use this pattern (government uses portals) to expect documentation/implementation details for CoWIN and then search for whether that portal’s code or design is open-source.

Describes ASEEM and Future Skills PRIME as government digital/AI-based platforms, reinforcing that multiple government services are implemented as online platforms.

A student could treat these as examples to look for common deployment practices (open APIs, open standards, or open-source releases) and then inspect CoWIN for similar traits.

Notes SWAYAM and other government MOOC portals as free online government platforms, illustrating government use of large-scale digital public services.

Given SWAYAM is a national DPI-style service, a student might look for public licensing, repositories, or policy links for SWAYAM and analogously for CoWIN to infer openness.

Identifies DigiLocker explicitly as one of the 'digital public goods' / 'digital repositories'.

A student could combine this with policy statements about how digital public goods should be implemented (see snippet 4) to infer likely platform design choices.

States a general rule that 'digital public infrastructure' will be built as open source, open standard and interoperable public goods.

A student could apply this rule to other items classified as digital public goods (like DigiLocker) to suspect they are/should be on open‑source platforms and then seek confirmation.

Describes the Digital India programme's broad aim to create digital governance and electronic empowerment through connected government platforms.

Using the programme's emphasis on unified digital governance, a student might expect government digital services (including DigiLocker) to follow prevailing DPI design principles such as openness and interoperability.

Mentions 'one nation, one digital platform' (DIKSHA) as an example of unified national digital platforms for public services.

This pattern of centralized/unified public platforms suggests a policy preference for common standards and possibly open implementations, which a student could check against DigiLocker's classification.

States DIKSHA is the 'one nation, one digital platform' for school education, showing DIKSHA is a government national digital platform for education.

A student could use this to focus verification on government digital platforms (like DIKSHA) and then check whether such named national platforms adopt open‑source approaches.

Says digital public infrastructure for agriculture will be built as open source, open standard and interoperable public good, giving a government policy pattern for DPI design.

A student could infer a government tendency/policy to make digital public infrastructure open‑source and investigate whether that policy also applied to education DPI like DIKSHA.

Discusses 'Digital Public Infrastructure' as a government emphasis and pillar (JAM Trinity), indicating a broader policy focus on national digital infrastructures.

Use this to reason that DIKSHA, as a national education DPI, might follow the general DPI principles and so check official DPI design guidelines or announcements for open‑source commitments.

Describes Gati Shakti as a digital platform uniting ministries for integrated planning, illustrating examples where the government builds central digital platforms for cross‑departmental use.

Compare design/implementation practices of other central digital platforms (like Gati Shakti) to DIKSHA to see if open‑source approaches are typical or mandated.

Mentions a unified Skill India Digital platform to expand the digital ecosystem for skilling, another instance of government creating national digital platforms.

A student could examine whether this and similar platforms were built open‑source to infer patterns applicable to DIKSHA, then verify DIKSHA specifically.