> 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/~/changes/xKUM0sBXFkyR8F24yAMq/community/documentation-guides/openg2p-module-doc-template.md). # OpenG2P Module Doc Template The title should have the exact module name, e.g. g2p\_notifications\_voucher ### Module name g2p\_notifications\_voucher ### Module title G2P Notifications: Voucher ### Technology base \ ### Functionality * Is it an extension of an existing module? * What does this model do/support as functionality? * What are the limitations and features/functions not supported? * Is it overriding any existing functionality? ### Design notes * What are salient design features? * Why were certain design decisions taken in a particular way? * Design patterns used. * Algorithms used. * Anything a developer should know about the design of this module. * Any scope for improvement and further design work that is pending. ### Relationships with other entities {% @mermaid/diagram content="graph TD G2PNotificationsVoucher --->|sends SMS via| SMSServer G2PNotificationsVoucher --->|sends Email via| EmailServer" %} ### Dependencies * Any external libraries used. List them. * `g2p_entitlement_voucher` * `g2p_notifications_base` ### User interface * Any new screens created/modified (with screenshots) * Any new menu items created. * Any new actions created. ### Configuration * Any system configurations and parameters that apply to this module. * Any configurations required for using this module. (List) ### Error codes * What are the error codes/exceptions thrown by this module. ### Source code ### Installation ### --- # 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/~/changes/xKUM0sBXFkyR8F24yAMq/community/documentation-guides/openg2p-module-doc-template.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.