> For the complete documentation index, see [llms.txt](https://india-energy-stack.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://india-energy-stack.gitbook.io/docs/propose-a-schema.md).

# Propose a Schema

A proposal travels a fixed **\~4-week lifecycle** — from the form below to a published entry in the [schema catalogue](/docs/schemas/schemas-ies.md). Your submission opens a public GitHub issue, and that issue stays the single record for it through every stage. Include a **concept note** built on the [use-case overview template](https://github.com/India-Energy-Stack/ies-accelerator/blob/main/.github/templates/use-case-overview.md) — after the architecture review, the IES Cell turns it into the use-case write-up that goes for final sign-off.

```mermaid
flowchart LR
    A["<b>Proposal</b><br/>Day 0<br/>form or issue<br/>+ concept note"] -->|issue opened| B["<b>Open comments</b><br/>Weeks 1–2<br/>ecosystem review"]
    B -->|freeze v0.1| C["<b>Targeted review</b><br/>Week 3<br/>picked experts"]
    C -->|v0.2| D["<b>Architecture review</b><br/>Week 4<br/>IES specs &amp; conventions"]
    D -->|v0.3| E["<b>Use-case review</b><br/>Week 4<br/>IES Cell finalises;<br/>concept note → use case"]
    E -->|use case ready| F["<b>Final review</b><br/>Week 4<br/>CEA &amp; authorities"]
    F -->|approved| G["<b>Published</b><br/>IES Cell lists it"]
```

| When          | Stage                                                             | Output            |
| ------------- | ----------------------------------------------------------------- | ----------------- |
| Day 0         | Proposal — form below or a GitHub issue, **with a concept note**  | Proposal issue    |
| Weeks 1–2     | Open ecosystem comments                                           | **v0.1** (frozen) |
| Week 3        | Targeted review by picked experts (1-week deadline)               | **v0.2**          |
| Week 4        | Architecture review — IES specs, schema conventions               | **v0.3**          |
| Week 4        | IES Cell finalises the schema; concept note → **use-case review** | Use case          |
| Week 4        | CEA / authorities final review                                    | Approved          |
| End of Week 4 | IES Cell lists it in the schema catalogue                         | Published         |

Revising an existing schema follows the same flow: non-breaking changes (new optional fields or enum values) stay within the minor version; breaking changes get a new sibling version, and the old one stays reachable.

***

The IES ecosystem grows through community-proposed schemas. If you're working on a data model that a use case needs, propose it here — tell us who you are, which use case it supports (existing or new), the schema itself, and the standards it builds on.

Fill in the form below. Your contact details (email and mobile) are kept **private** — shared only with the IES secretariat. A public tracking issue is created automatically for the proposal itself (schema, use case, standards) so the community can review and discuss it. No GitHub account is required to submit.

{% hint style="info" %}
Optionally include your GitHub username and we'll tag you on the tracking issue so you can follow the discussion.
{% endhint %}

{% hint style="info" %}
Two references worth keeping open as you fill this in: the [IES term taxonomy](https://india-energy-stack.gitbook.io/docs/schemas/taxonomy) — check your terms align with it — and the [use-case overview template](https://github.com/India-Energy-Stack/ies-accelerator/blob/main/.github/templates/use-case-overview.md) to structure your concept note. Share the concept note as a **public link** (a Google Doc set to "anyone with the link", or a GitHub link).
{% endhint %}

{% @ies-schema-proposal/schema-proposal content="" %}

If the form above doesn't load, [open it in a new tab](https://forms.gle/ESVk4PDcfEerPo6f7).

After submitting, your proposal is posted to the [GitHub Issue Tracker](https://github.com/India-Energy-Stack/ies-accelerator/issues) — you should see an issue populated with your request, where the community reviews and discusses it.

Not sure which use case yours fits? Browse the use-case overviews first, starting with [Consumer Energy Passport](/docs/use-case-overviews/consumer-energy-passport.md).


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://india-energy-stack.gitbook.io/docs/propose-a-schema.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
