> For the complete documentation index, see [llms.txt](https://docs.mulearn.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mulearn.org/the-mulearn-story-and-philosophy/how-were-built.md).

# How We're Built

μLearn is a Section 8 not-for-profit under Group of Technology Companies (GTech), A consortium of technology companies in Kerala. Its governance is designed to be person-independent. The protocol runs the ecosystem. People steward it.

Understanding how μLearn is built matters for anyone operating within it campus leads, replication leads, partners, and IG leads all need to understand the governance structure to work within it correctly.

### <mark style="color:$primary;">Legal Structure</mark>

μLearn Foundation is a **Section 8 Company** a not-for-profit registered under Indian law.

> Section 8 means one thing structurally: μLearn cannot distribute profits. Every resource generated goes back into the ecosystem. This is a legal commitment not a values statement.

Section 8 structure means μLearn optimises for ecosystem health the quality of learning, the reliability of validation, and the real-world outcomes it produces not for revenue or user growth.

### <mark style="color:$primary;">GTech</mark>

Group of Technology Companies (GTech) is the Industry body of Information Technology (IT) and Business Process Management (BPM) organisations in Kerala. GTech works closely with the Government of Kerala to promote the accelerated growth of the IT industry in the state. Established in 2001. GTech provides the platform for domain and technology companies from across the world for enterprise and strategic alliances with Member Organisations.

GTech over the years has built a strong membership of more than 260 IT companies comprises Innovative Start-ups, Small & Medium size companies, large Home Grown companies and International Majors like Infosys, TCS, Tata Elxsi, Wipro, Cognizant, Ernst & Young, Allianz Technology, UST Global, IBS, Quest Global, NeST, Qburst, Envestnet and SunTec.

GTech is the reference point for the IT Industry in the State and works alongside the Government of Kerala in promoting the State as an ideal IT/BPM destination. GTech contributes, through various initiatives, to the overall welfare of entrepreneurs and professionals in the industry, enabling an ecosystem best suited for transformative and inclusive growth. GTech proactively works towards the enhancement of the social and economic development of all citizens.

### <mark style="color:$primary;">The Massive Transformative Purpose</mark>

*Empowering the next generation of learners with the right mindset and unlocking their full potential through decentralised, peer-driven education, fostering innovation and growth, connecting to communities globally.*

This is the legal purpose of the registered not-for-profit the thing μLearn is structurally committed to pursuing above everything else.

### <mark style="color:$primary;">μLegacy</mark>

μLegacy is μLearn's long-term sustainability mechanism a governance structure of past fellows and enablers who ensure the ecosystem continues to function and grow independent of any individual.This is what makes μLearn **person-independent.**&#x4E;o single person's departure should break the system. The protocol runs the ecosystem. People steward it.

### <mark style="color:$primary;">Protocol-First Design</mark>

μLearn is designed to be **protocol-first, people-second.**

Which means:

* The framework governs not individuals
* Roles are defined by the protocol not by personality
* The ecosystem continues regardless of who occupies any given role

This principle is not philosophical. It is a structural design decision that determines how every role, every node, and every initiative is built.

If the core team disappeared for a week the ecosystem should still run. That is the test of a healthy protocol.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.mulearn.org/the-mulearn-story-and-philosophy/how-were-built.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.