> For the complete documentation index, see [llms.txt](https://gramhal.gitbook.io/bolbhav/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gramhal.gitbook.io/bolbhav/welcome.md).

# Welcome

## Welcome to Bolbhav Documentation

Whether you are new to Bolbhav or you have built Bolbhav, this is a space to get the most authoratitative information on any of the Bolbhav features or its roadmap. 

### Version and Last updated date

{% hint style="info" %}
Check the version number and last updated date in [here](/bolbhav/chapter-14-change-log/documentation.md) before reading forward. 
{% endhint %}

## Purpose of this documentation?

This documentation is written with multiple objectives in mind:

<table data-view="cards"><thead><tr><th></th><th></th><th></th></tr></thead><tbody><tr><td><strong>Onboarding</strong> </td><td>Whenever any new team member or external contributor join the team, read through the documentation in one go to quickly get up to the speed. </td><td></td></tr><tr><td><strong>Ongoing</strong></td><td>This document is written as modules so that it can assit in your everyday work. Before you start working on anything, read in detail about it in the specific module.</td><td></td></tr><tr><td><strong>For public</strong></td><td>Bolbhav may or may not achieve PMF but this experiment's detailed documentation can guide current and future agri-innovators in their product development journey. </td><td></td></tr></tbody></table>

## How to read this document?

1. The best way to read this document is to start with Chapter-1. It is fundamental to understanding any other thing in the whole document. Without reading it other things might not be clear.
2. Once you have gone through the Chapter-1, either you can go in order chapter-wise or you can directly pick the topics that excited you the most.&#x20;
3. It may be tough to understand everything at once, hence keep coming back to this documentation.&#x20;

## Introduction about the app

The Bolbhav app has five main use cases:

<table data-view="cards"><thead><tr><th></th><th></th><th></th></tr></thead><tbody><tr><td><p><strong>Viewing crop prices</strong> </p><p></p><p><br>A user can see the latest prices of a mandi-crop combination including the image of individual sales receipt and aggregated statistics.</p></td><td></td><td></td></tr><tr><td><strong>Contributing crop sales receipts</strong><br><br>Any user can contribute the crop sale data for themselves for after taking consent of any other farmer. In this they share the image of the sale receipt and the associated data. </td><td></td><td></td></tr><tr><td><strong>Validation of crop sale receipts</strong><br><br>Any user can validate the receipts submitted by other users. Only validated receipts are shown to the users in the frontend.</td><td></td><td></td></tr><tr><td><p><strong>Purchasing silver tokens through subscription</strong></p><p><br><br>A user can buy silver tokens by paying to Bolbhav.</p></td><td></td><td></td></tr><tr><td><strong>Redeeming gold tokens into money</strong></td><td></td><td>Contributors can convert their earned tokens into real currency.</td></tr><tr><td><strong>Other use cases</strong></td><td></td><td><br>There are other necessary features like referral, FAQ, statement of tokens, receipt submitted, terms and conditions.</td></tr></tbody></table>

## *<mark style="color:green;">`LET'S GET STARTED`</mark>*


---

# 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://gramhal.gitbook.io/bolbhav/welcome.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.