> For the complete documentation index, see [llms.txt](https://pmse.gitbook.io/pmse-dhdk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://pmse.gitbook.io/pmse-dhdk/1.-project-charter/1.3-constraints.md).

# 1.3 Constraints

The GNA chatbot is subject to some constraints that shape its development and functionality. These constraints can be categorized into technical, operational, and organizational aspects.

## Technical Constraints

* **AI Model Limitations**: While the chatbot leverages an advanced language model like [*Mistral NeMo*](https://mistral.ai/news/mistral-nemo/), the accuracy and relevance of its responses depend on the quality of the AI pipeline development and fine-tuning. Limitations in natural language understanding, especially for domain-specific queries, may arise.
* **Integration Requirements**: The chatbot must integrate seamlessly with the GNA platform and any pre-existing systems, addressing potential compatibility challenges with legacy software and specific APIs. Additionally, the application must ensure compatibility with the grantor's existing CRM systems, which may include a web-based documentation platform and GIS software applications.
* **Infrastructure**: Hosting and cloud service constraints, such as server capacity, response times, and scalability, can impact the chatbot's reliability during high-traffic periods.
* **Language Constraints**: The chatbot will initially be developed exclusively in Italian, meaning that its natural language processing capabilities will be tailored to the Italian language. This limitation imposes certain constraints, such as the need for accurate linguistic features that can handle the nuances of Italian grammar, syntax, and regional variations. These language-specific constraints will be addressed in the early stages of development to ensure the chatbot provides a fluent and effective user experience for Italian-speaking users.
* **Alternative Flows**. The chatbot application can be designed to include accessibility features, particularly for users with disabilities. For instance, it could implement voice functionality to allow users to input messages through speech and receive responses in an audible format, enhancing usability and inclusivity. However, this feature will not be included as a requirement in the initial version of the application.

## Operational Constraints

* **Budget**: The project must adhere to predefined financial limitations, including development, operational, and maintenance costs.
* **Timeframe**: The development and deployment phases must align with the GNA schedules and milestones. Delays could affect stakeholder confidence or project funding.
* **User Support**: Limited resources for post-deployment support and updates may constrain the chatbot's ability to adapt to evolving user needs.

## Organizational Constraints

* **Regulatory Compliance**: The chatbot must comply with data protection regulations (e.g., GDPR) to ensure the privacy and security of user interactions and data.
* **Stakeholder Expectations**: Meeting the diverse requirements of stakeholders, including ministry officials, researchers, and other users, may present challenges in balancing functionality with usability.
* **Change Management**: Encouraging adoption and training users to interact effectively with the chatbot may require additional effort and resources.

These constraints necessitate careful planning, prioritization, and ongoing collaboration among the project team and stakeholders to ensure the GNA chatbot meets its objectives within the defined parameters.


---

# 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://pmse.gitbook.io/pmse-dhdk/1.-project-charter/1.3-constraints.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.