> 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/features/rule-driven-processing.md). # Rule-Driven Processing At the heart of PBMS lies its rule-driven framework. Eligibility rules determine who qualifies as a beneficiary during enrolment cycles, ensuring that only citizens who meet defined criteria are enrolled. Disbursement rules operate within the context of beneficiary lists and allow programs to refine or reduce those lists when preparing disbursements. Entitlement rules are applied to disbursement lists to determine the exact goods or services each beneficiary is entitled to. By applying these rules systematically, PBMS ensures that the process is transparent, auditable, and adaptable to varying program needs. --- # 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/features/rule-driven-processing.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.