> 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/products/pbms/_archive/pre-consolidation-repositories.md).

# Pre-Consolidation Repositories

{% hint style="warning" %}
**Archived.** PBMS was previously developed across the separate repositories listed below. These have been **consolidated into the single** [**OpenG2P/pbms**](https://github.com/OpenG2P/pbms) **monorepo** and will be archived on GitHub. This page is retained for historical reference only — see [Repositories](/products/pbms/developer-zone/repositories.md) for the current code organization.
{% endhint %}

<table><thead><tr><th width="300">Repository (pre-consolidation)</th><th width="150">Consolidated into</th><th>Description</th></tr></thead><tbody><tr><td><a href="https://github.com/OpenG2P/openg2p-pbms-odoo">openg2p-pbms-odoo</a></td><td><code>pbms/odoo/</code></td><td>The main PBMS application based on Odoo — benefit program definition, benefit codes, geographies, service providers, rules and cycles, and beneficiary-list creation.</td></tr><tr><td><a href="https://github.com/OpenG2P/openg2p-pbms-odoo-extensions">openg2p-pbms-odoo-extensions</a></td><td><code>pbms/odoo/extensions/</code></td><td>The extensibility and customisation modules of PBMS — target registry names &#x26; models, the eligibility &#x26; entitlement summary views, and the UI theme. Bundled as Odoo modules.</td></tr><tr><td><a href="https://github.com/OpenG2P/openg2p-pbms-community-addons">openg2p-pbms-community-addons</a></td><td><code>pbms/odoo/community-addons/</code></td><td>The community Odoo addons required by PBMS.</td></tr><tr><td><a href="https://github.com/OpenG2P/openg2p-pbms-bg-tasks">openg2p-pbms-bg-tasks</a></td><td><code>pbms/core/</code></td><td>The two background-task runtimes — Celery Beat Producers and Celery Worker Tasks — that together perform all asynchronous processing for PBMS, plus the shared data models.</td></tr><tr><td><a href="https://github.com/OpenG2P/openg2p-pbms-bg-tasks-extensions">openg2p-pbms-bg-tasks-extensions</a></td><td><code>pbms/extensions/</code></td><td>The extensibility modules for the background tasks — registry models and the APIs behind the eligibility &#x26; entitlement summary views.</td></tr><tr><td><a href="https://github.com/OpenG2P/openg2p-pbms-apis">openg2p-pbms-apis</a></td><td><code>pbms/apis/</code></td><td>The PBMS portal APIs — Staff Portal, Beneficiary Portal, Agency-App and partner systems.</td></tr><tr><td><a href="https://github.com/OpenG2P/openg2p-pbms-docker">openg2p-pbms-docker</a></td><td><code>pbms/docker/</code></td><td>The Docker build scripts that created the PBMS runtime images (Odoo, and the Celery beat/worker runtimes).</td></tr><tr><td><a href="https://github.com/OpenG2P/openg2p-pbms-gen2-deployment">openg2p-pbms-gen2-deployment</a></td><td><code>pbms/deployment/</code></td><td>The Helm charts, templates and values for deploying PBMS-Odoo and the background tasks in a Kubernetes cluster.</td></tr></tbody></table>


---

# 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/products/pbms/_archive/pre-consolidation-repositories.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.