> For the complete documentation index, see [llms.txt](https://docs.openg2p.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openg2p.org/operations/deployment/_archive/packages.md).
# Packages
## Module packages
Each OpenG2P module—such as Social Registry, PBMS, SPAR, and G2P Bridge—is delivered as a deployable package. This package consists of multiple components and is provided as a Helm chart that includes several sub-charts. See the packaging hierarchy outlined below:
The contents of the Helm package may be found in the [`Chart.yaml` ](https://github.com/OpenG2P/openg2p-social-registry-deployment/tree/2.0/charts/openg2p-social-registry)file
## Package versioning
The version of the Helm Chart of the module is considered as the package version of the module. For example, Social Registry version 1.5.0 refers to the **Helm chart of the entire package.** As mentioned above, each package contains several components that may have their own versions. In case of Odoo based modules - Social Registry and PBMS - the "core" version refers to the version of the Odoo Docker, which is part of the Helm package.
Learn more on Helm charts, versioning and publishing [here](/operations/deployment/helm-charts.md#helm-chart-versions).
Refer to [versioning conventions](/operations/deployment/_archive/versioning.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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.openg2p.org/operations/deployment/_archive/packages.md?ask=&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.
