> 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.md).

# Products

- [Registry](https://docs.openg2p.org/products/registry.md)
- [OpenG2P Registry (Platform)](https://docs.openg2p.org/products/registry/registry.md): OpenG2P Registry is an open-source platform for building functional registries of individuals, groups and non-human entities, that fit into a country's digital public infrastructure
- [Concepts](https://docs.openg2p.org/products/registry/registry/concepts.md): Core concepts of the OpenG2P Registry platform -- Registry, Register, Table, Programme Register, records, identifiers, change requests, hierarchy, and metadata-driven configuration.
- [Features](https://docs.openg2p.org/products/registry/registry/features.md): Overview of all features provided by the OpenG2P Registry.
- [Unified Registry Model](https://docs.openg2p.org/products/registry/registry/features/unified-registry-model.md)
- [Change Management & Approval Workflow](https://docs.openg2p.org/products/registry/registry/features/change-management-and-approval-workflow.md)
- [Audit-ability & Trace-ability](https://docs.openg2p.org/products/registry/registry/features/audit-ability-and-trace-ability.md)
- [Data Integrity, Security & Encryption](https://docs.openg2p.org/products/registry/registry/features/data-integrity-security-and-encryption.md)
- [Ingestion Pipeline](https://docs.openg2p.org/products/registry/registry/features/ingestion-pipeline.md): Operational capabilities exposed by the ingestion pipeline - APIs, configuration management, observability, and user-facing behavior.
- [Outgestion Pipeline](https://docs.openg2p.org/products/registry/registry/features/outgestion-pipeline.md): The Base Registry implements a fully asynchronous outgestion pipeline that pushes registry data changes to external partner systems through configurable transformation and WebSub-based event delivery.
- [Dynamic UI Rendering](https://docs.openg2p.org/products/registry/registry/features/dynamic-ui-rendering.md)
- [Registry Intake](https://docs.openg2p.org/products/registry/registry/features/registry-intake.md): Registry Intake is a key mechanism for creating and onboarding records into the registry.
- [Event Publishing & WebSub Integration](https://docs.openg2p.org/products/registry/registry/features/event-publishing-and-websub-integration.md)
- [Consent-Aware Data Sharing](https://docs.openg2p.org/products/registry/registry/features/consent-aware-data-sharing.md)
- [Deduplication](https://docs.openg2p.org/products/registry/registry/features/deduplication.md): Identify and manage duplicate records within the registry.
- [RBAC Roles & Permissions](https://docs.openg2p.org/products/registry/registry/features/rbac-roles-and-permissions.md): Roles, permissions, and role-permission mappings for the OpenG2P Registry module, managed via Keycloak under the 'staff' realm.
- [Metadata-Driven Extensibility](https://docs.openg2p.org/products/registry/registry/features/metadata-driven-extensibility.md)
- [Standards Compliance](https://docs.openg2p.org/products/registry/registry/features/standards-compliance.md)
- [Cloud-Native Deployment & Scaling](https://docs.openg2p.org/products/registry/registry/features/cloud-native-deployment-and-scaling.md)
- [Observability & Operational Control](https://docs.openg2p.org/products/registry/registry/features/observability-and-operational-control.md)
- [Multi-Level Approval Workflow](https://docs.openg2p.org/products/registry/registry/features/multi-level-approval-workflow.md)
- [Design](https://docs.openg2p.org/products/registry/registry/design.md): Technical architecture and design of OpenG2P Registry
- [Tech Architecture](https://docs.openg2p.org/products/registry/registry/design/registry-tech-architecture.md)
- [Data Model](https://docs.openg2p.org/products/registry/registry/design/data-model.md): Core data model of OpenG2P Registry -- registers, records, versioning, and domain extension patterns.
- [Meta Data Seeding](https://docs.openg2p.org/products/registry/registry/design/meta-data-seeding.md): How variant-specific configuration and sample data are seeded into the registry database after deployment.
- [Change Management](https://docs.openg2p.org/products/registry/registry/design/change-management.md): Change request workflow -- how every registry mutation flows through approval before being committed.
- [Ingestion Pipeline](https://docs.openg2p.org/products/registry/registry/design/ingestion-pipeline.md): End-to-end asynchronous ingestion flow -- from partner payload receipt to change request creation.
- [Outgestion Pipeline](https://docs.openg2p.org/products/registry/registry/design/outgestion-pipeline.md): Design of the outgestion pipeline for pushing data to external partner systems.
- [Encryption at Rest](https://docs.openg2p.org/products/registry/registry/design/encryption-at-rest.md): Envelope encryption approach for column-level encryption of sensitive registry data at rest.
- [Partner APIs](https://docs.openg2p.org/products/registry/registry/design/partner-apis.md): Design of the Partner API surface for external system integration
- [Deduplication](https://docs.openg2p.org/products/registry/registry/design/deduplication.md): Design of the deduplication engine for identifying and managing duplicate records
- [VC Issuance](https://docs.openg2p.org/products/registry/registry/design/vc-issuance.md): Design of verifiable credential issuance from the registry
- [Registrant Auth - OIDC](https://docs.openg2p.org/products/registry/registry/design/registrant-authentication-oidc-widget.md)
- [Detailed design](https://docs.openg2p.org/products/registry/registry/design/registrant-authentication-oidc-widget/detailed-design.md)
- [UI Engineering](https://docs.openg2p.org/products/registry/registry/design/ui-engineering-design.md): Engineering design of the OpenG2P Registry staff portal UI and schema-driven widget system.
- [Widget Library](https://docs.openg2p.org/products/registry/registry/design/ui-engineering-design/registry-ui-widget-library.md)
- [Widget Reference](https://docs.openg2p.org/products/registry/registry/design/ui-engineering-design/widget-reference.md)
- [Score Computation framework](https://docs.openg2p.org/products/registry/registry/design/score-computation-framework.md)
- [Functional ID generation](https://docs.openg2p.org/products/registry/registry/design/functional-id-generation.md)
- [Audit trail for Write Operations](https://docs.openg2p.org/products/registry/registry/design/audit-trail-for-write-operations.md)
- [Registry themes](https://docs.openg2p.org/products/registry/registry/design/registry-themes.md)
- [Completion Score](https://docs.openg2p.org/products/registry/registry/design/completion-score.md): Register Completion Score Design Document
- [Dynamic languages](https://docs.openg2p.org/products/registry/registry/design/dynamic-languages.md)
- [Intake Forms](https://docs.openg2p.org/products/registry/registry/design/intake-forms.md): Intake forms for Register
- [Input Mechanisms](https://docs.openg2p.org/products/registry/registry/design/intake-forms/input-mechanisms.md): Input mechanisms into Intake Forms
- [Record level permissions](https://docs.openg2p.org/products/registry/registry/design/record-level-permissions.md): Technical design
- [AWE Integration](https://docs.openg2p.org/products/registry/registry/design/awe-integration.md)
- [Developer Zone](https://docs.openg2p.org/products/registry/registry/developer-zone.md): Resources for developers building on and extending OpenG2P Registry.
- [Organization of Codebase](https://docs.openg2p.org/products/registry/registry/developer-zone/organization-of-codebase.md)
- [Building a Registry](https://docs.openg2p.org/products/registry/registry/developer-zone/building-a-registry.md): Creating a domain-specific registry by extending the OpenG2P Registry core.
- [Concepts](https://docs.openg2p.org/products/registry/registry/developer-zone/building-a-registry/concepts.md)
- [Registry vs Register](https://docs.openg2p.org/products/registry/registry/developer-zone/building-a-registry/concepts/registry-vs-register.md): Base registry models available in the platform
- [Base Models](https://docs.openg2p.org/products/registry/registry/developer-zone/building-a-registry/concepts/base-models.md): ORM Models and Pydantic Schemas for defining domain objects of a Registry
- [Registry Configuration](https://docs.openg2p.org/products/registry/registry/developer-zone/building-a-registry/concepts/registry-configuration.md): Configurations for the Registry Instance
- [G2PRegistryConfiguration](https://docs.openg2p.org/products/registry/registry/developer-zone/building-a-registry/concepts/registry-configuration/g2pregistryconfiguration.md): g2p\_registry\_configuration
- [Register Metadata](https://docs.openg2p.org/products/registry/registry/developer-zone/building-a-registry/concepts/registry-and-register-metadata.md)
- [G2PRegisterDefinition](https://docs.openg2p.org/products/registry/registry/developer-zone/building-a-registry/concepts/registry-and-register-metadata/g2pregisterdefinition.md): g2p\_register\_definitions - the principal metadata information on Registers
- [G2PIntakeFormDefinition](https://docs.openg2p.org/products/registry/registry/developer-zone/building-a-registry/concepts/registry-and-register-metadata/g2pintakeformdefinition.md): g2p\_intake\_form\_definitions - the principal metadata information on creation of intake forms on registers
- [G2PRegisterSchema](https://docs.openg2p.org/products/registry/registry/developer-zone/building-a-registry/concepts/registry-and-register-metadata/g2pregisterschema.md): g2p\_register\_schemas - JSON schemas for datasets
- [G2PRegisterSection](https://docs.openg2p.org/products/registry/registry/developer-zone/building-a-registry/concepts/registry-and-register-metadata/g2pregistersection.md): g2p\_register\_sections
- [G2PRegisterUITab](https://docs.openg2p.org/products/registry/registry/developer-zone/building-a-registry/concepts/registry-and-register-metadata/g2pregisteruitab.md): g2p\_register\_ui\_tabs - UI Configuration (Tabs) for Registers & Program Registers
- [G2PIntakeFormUITab](https://docs.openg2p.org/products/registry/registry/developer-zone/building-a-registry/concepts/registry-and-register-metadata/g2pintakeformuitab.md): g2p\_intake\_form\_ui\_tabs - UI Configuration (Tabs) for Intake forms
- [G2PRegisterUITabSections](https://docs.openg2p.org/products/registry/registry/developer-zone/building-a-registry/concepts/registry-and-register-metadata/g2pregisteruitabsections.md): g2p\_register\_ui\_tab\_sections - UI Tab Configuration (Sections) for Registers
- [G2PIntakeFormUITabSections](https://docs.openg2p.org/products/registry/registry/developer-zone/building-a-registry/concepts/registry-and-register-metadata/g2pintakeformuitabsections.md): g2p\_intake\_form\_ui\_tab\_sections - UI Tab Configuration (Sections) for Intake forms
- [Registry Extensions](https://docs.openg2p.org/products/registry/registry/developer-zone/building-a-registry/concepts/registry-extensions.md)
- [Platform & Extensions Model](https://docs.openg2p.org/products/registry/registry/developer-zone/building-a-registry/concepts/registry-extensions/platform-and-extensions-model.md): OpenG2P Registry is a platform + extension reusable package and a base Helm chart, plus a thin domain layer you modify during implementation
- [Extensions Contract](https://docs.openg2p.org/products/registry/registry/developer-zone/building-a-registry/concepts/registry-extensions/extensions-contract.md): Everything a domain extension must (and may) implement for the platform to load it correctly
- [Step-by-Step Guide](https://docs.openg2p.org/products/registry/registry/developer-zone/building-a-registry/guide-to-building-a-registry.md): Follow these chapters in order when building a new domain registry
- [Plan your domain](https://docs.openg2p.org/products/registry/registry/developer-zone/building-a-registry/guide-to-building-a-registry/plan-your-domain.md): Design the register graph and field inventory before writing code. Metadata UUIDs, Python class suffixes, and Helm \`idTypes\` all flow from decisions made here.
- [Scaffold the repository](https://docs.openg2p.org/products/registry/registry/developer-zone/building-a-registry/guide-to-building-a-registry/scaffold-the-repository.md): A domain registry is its own repository. Docker images, Helm wrapper, CI workflows, and the Python extension all live together - the platform repositories stay upstream dependencies.
- [Configure extensions package](https://docs.openg2p.org/products/registry/registry/developer-zone/building-a-registry/guide-to-building-a-registry/configure-extensions-package.md): The extension is a Python wheel installed into API and Celery images. At runtime it is always imported as openg2p\_registry\_extensions, regardless of source folder name.
- [Build models, schemas and services](https://docs.openg2p.org/products/registry/registry/developer-zone/building-a-registry/guide-to-building-a-registry/build-models-schemas-and-services.md): For each register mnemonic, implement the class set and export everything. Core resolves classes by name at runtime.
- [Generate metadata and sample data](https://docs.openg2p.org/products/registry/registry/developer-zone/building-a-registry/guide-to-building-a-registry/generate-metadata-and-sample-data.md): Metadata SQL is how the platform learns your domain - register catalog, staff portal layout, intake forms, partner routing, and template registry.
- [Build docker images](https://docs.openg2p.org/products/registry/registry/developer-zone/building-a-registry/guide-to-building-a-registry/build-docker-images.md): Each domain registry produces domain docker images. Service spec files pin platform git tags and stage the local extension into the build context. The db-seed image ships SQL and flat Jinja templates.
- [Construct helm charts](https://docs.openg2p.org/products/registry/registry/developer-zone/building-a-registry/guide-to-building-a-registry/construct-helm-charts.md)
- [Post install workflow](https://docs.openg2p.org/products/registry/registry/developer-zone/building-a-registry/guide-to-building-a-registry/post-install-workflow.md): After \`helm install\` completes, you may walk through this checklist. The goal is to confirm metadata landed, templates are reachable, async workers are live, and the staff portal reflects your domain.
- [Reference Implementations](https://docs.openg2p.org/products/registry/registry/developer-zone/building-a-registry/guide-to-building-a-registry/reference-implementations.md): This guide is variant-agnostic. The repositories below are concrete implementations of the same extension pattern. Use them as working templates; copy structure and conventions.
- [Deployment Design](https://docs.openg2p.org/products/registry/registry/developer-zone/building-a-registry/deployment-design.md): How to create a Registry Deployment for a target Domain
- [Developer Install](https://docs.openg2p.org/products/registry/registry/developer-zone/developer-install.md)
- [Staff Portal UI](https://docs.openg2p.org/products/registry/registry/developer-zone/developer-install/openg2p-registry-staff-portal-ui.md): Developer Installation for Openg2p Registry Staff Portal UI
- [Staff Portal API](https://docs.openg2p.org/products/registry/registry/developer-zone/developer-install/staff-portal-api.md): Developers can set up and run the OpenG2P Registry Staff Portal API on their local machines. This guide outlines the steps to install it on a Linux-based laptop or desktop.
- [Beneficiary Portal API](https://docs.openg2p.org/products/registry/registry/developer-zone/developer-install/beneficiary-portal-api.md): Developers can set up and run the OpenG2P Registry Beneficiary Portal API on their local machines. This guide outlines the steps to install it on a Linux-based laptop or desktop.
- [Partner API](https://docs.openg2p.org/products/registry/registry/developer-zone/developer-install/partner-api.md): Developers can set up and run the OpenG2P Registry Partner API on their local machines. This guide outlines the steps to install it on a Linux-based laptop or desktop.
- [Celery Beat Producers](https://docs.openg2p.org/products/registry/registry/developer-zone/developer-install/celery-beat-producers.md): Developers can set up and run the OpenG2P Registry Celery Beat Producers on their local machines. The Beat Producers schedule periodic registry jobs and enqueue them onto the Celery worker queue.
- [Celery Workers](https://docs.openg2p.org/products/registry/registry/developer-zone/developer-install/celery-workers.md): Developers can set up and run the OpenG2P Registry Celery Workers on their local machines. The Workers execute the tasks enqueued by the Celery Beat Producers.
- [API Documentation](https://docs.openg2p.org/products/registry/registry/developer-zone/api-documentation.md): API reference for OpenG2P Registry.
- [Staff Portal API](https://docs.openg2p.org/products/registry/registry/developer-zone/api-documentation/staff-portal-api.md): APIs used by the Staff Portal UI
- [Partner API](https://docs.openg2p.org/products/registry/registry/developer-zone/api-documentation/partner-api.md): APIs available for the Registry Partner ecosystem
- [Non Functional Requirements](https://docs.openg2p.org/products/registry/registry/developer-zone/non-functional-requirements.md): Performance & Security - Design & Approach
- [Deployment and Extension](https://docs.openg2p.org/products/registry/registry/deployment-and-extension.md): How the OpenG2P Registry is packaged, deployed and extended. The platform is now a complete, installable registry in its own right — with a reference registry, Helm chart, Docker images, seeding and t
- [Packaging & the reference registry](https://docs.openg2p.org/products/registry/registry/deployment-and-extension/packaging-and-reference-registry.md): The Docker images and the single Helm chart the platform publishes, the reference registry they run out of the box, and how the domain model is selected at runtime.
- [Extending into a new registry](https://docs.openg2p.org/products/registry/registry/deployment-and-extension/extending-into-a-new-registry.md): How to turn the platform into a domain registry — social, farmer, disability, … — by adding only an extension, seed, tests and a deploy overlay on top of the published images and chart.
- [Testing & the sanity suite](https://docs.openg2p.org/products/registry/registry/deployment-and-extension/testing-and-sanity-suite.md): The in-built sanity/e2e suite, its two-part model (tests that are independent of the registry's domain vs tests tied to its fields), and how a domain registry extends the field-specific tests.
- [Versions](https://docs.openg2p.org/products/registry/registry/versions.md): Where to find Registry Platform chart and image versions, and what changed in each.
- [Registry Platform Release Notes - v1.1.0](https://docs.openg2p.org/products/registry/registry/versions/registry-platform-release-notes-v1.1.0.md)
- [Registry Platform Release Notes - v1.0.0](https://docs.openg2p.org/products/registry/registry/versions/registry-platform-release-notes-v1.0.0.md)
- [Registry Release Notes - v4.0.0](https://docs.openg2p.org/products/registry/registry/versions/registry-release-notes-v4.0.0.md)
- [Registry Release Notes - v4.1.0](https://docs.openg2p.org/products/registry/registry/versions/registry-release-notes-v4.1.0.md)
- [Use Case Implementation](https://docs.openg2p.org/products/registry/registry/use-case-implementation.md)
- [Farmer Registry](https://docs.openg2p.org/products/registry/farmer-registry.md)
- [Deployment](https://docs.openg2p.org/products/registry/farmer-registry/deployment.md): How the Farmer Registry is packaged as an extension of the Registry Platform, and how to deploy it on Kubernetes.
- [Helm chart](https://docs.openg2p.org/products/registry/farmer-registry/deployment/helm-chart.md): The openg2p-farmer-registry chart — a thin wrapper over the platform chart, its images, and the values that make it the Farmer Registry.
- [Data seeding](https://docs.openg2p.org/products/registry/farmer-registry/deployment/data-seeding.md): How the Farmer Registry is seeded at install — the seed content this repo owns and the seeding machinery it inherits from the platform.
- [Sanity testing](https://docs.openg2p.org/products/registry/farmer-registry/deployment/sanity-testing.md): The in-cluster sanity suite for the Farmer Registry — what it inherits from the platform and the field-specific tests this repo contributes.
- [Versions](https://docs.openg2p.org/products/registry/farmer-registry/versions.md): Where to find Farmer Registry chart and image versions, and what changed in each.
- [National Social Registry](https://docs.openg2p.org/products/registry/national-social-registry.md)
- [PMT Score](https://docs.openg2p.org/products/registry/national-social-registry/pmt-score.md)
- [Deployment](https://docs.openg2p.org/products/registry/national-social-registry/deployment.md): How the National Social Registry is packaged as an extension of the Registry Platform, and how to deploy it on Kubernetes.
- [Helm chart](https://docs.openg2p.org/products/registry/national-social-registry/deployment/helm-chart.md): The openg2p-nsr chart — a thin wrapper over the platform chart, its images, and the values that make it the National Social Registry.
- [Data seeding](https://docs.openg2p.org/products/registry/national-social-registry/deployment/data-seeding.md): How the National Social Registry is seeded at install — the seed content this repo owns and the seeding machinery it inherits from the platform.
- [Sanity testing](https://docs.openg2p.org/products/registry/national-social-registry/deployment/sanity-testing.md): The in-cluster sanity suite for the National Social Registry — what it inherits from the platform and the field-specific tests this repo contributes.
- [Versions](https://docs.openg2p.org/products/registry/national-social-registry/versions.md): Where to find NSR chart and image versions, and what changed in each.
- [PBMS](https://docs.openg2p.org/products/pbms.md): Program and Beneficiary Management System
- [Features](https://docs.openg2p.org/products/pbms/features.md)
- [Decoupled yet Registry-Aware](https://docs.openg2p.org/products/pbms/features/decoupled-yet-registry-aware.md)
- [Support for Multiple Registries](https://docs.openg2p.org/products/pbms/features/support-for-multiple-registries.md)
- [Rule-Driven Processing](https://docs.openg2p.org/products/pbms/features/rule-driven-processing.md)
- [Multi-Goods & Multi-Services Support](https://docs.openg2p.org/products/pbms/features/multi-goods-and-multi-services-support.md)
- [Dual Cycle Management](https://docs.openg2p.org/products/pbms/features/dual-cycle-management.md)
- [Warehouses & Agencies](https://docs.openg2p.org/products/pbms/features/warehouses-and-agencies.md)
- [Verification Workflows](https://docs.openg2p.org/products/pbms/features/verification-workflows.md)
- [Controlled List Management](https://docs.openg2p.org/products/pbms/features/controlled-list-management.md)
- [Integration with Sponsor Banks](https://docs.openg2p.org/products/pbms/features/integration-with-sponsor-banks.md)
- [Integration with Warehouses & Agencies](https://docs.openg2p.org/products/pbms/features/integration-with-warehouses-and-agencies.md)
- [Reconciliation with Sponsor Bank](https://docs.openg2p.org/products/pbms/features/reconciliation-with-sponsor-bank.md)
- [Reconciliation with Warehouses & Agencies](https://docs.openg2p.org/products/pbms/features/reconciliation-with-warehouses-and-agencies.md)
- [Reporting & Dashboards](https://docs.openg2p.org/products/pbms/features/reporting-and-dashboards.md)
- [Design](https://docs.openg2p.org/products/pbms/design.md)
- [Concept](https://docs.openg2p.org/products/pbms/design/concept.md)
- [Architecture](https://docs.openg2p.org/products/pbms/design/architecture.md)
- [PBMS Tech Architecture](https://docs.openg2p.org/products/pbms/design/pbms-tech-architecture.md)
- [Static definitions](https://docs.openg2p.org/products/pbms/design/pbms-odoo.md)
- [Rule definitions](https://docs.openg2p.org/products/pbms/design/rule-definitions.md)
- [Enrolment & Disbursement Cycles](https://docs.openg2p.org/products/pbms/design/enrolment-and-disbursement-cycles.md): A benefit program typically goes through two distinct repetitive cycles - enrolment cycles and disbursement cycles.
- [Enrolment cycle](https://docs.openg2p.org/products/pbms/design/enrolment-workflow.md)
- [Disbursement cycle](https://docs.openg2p.org/products/pbms/design/disbursement-workflow.md)
- [Workflow design](https://docs.openg2p.org/products/pbms/design/workflow-design.md): Workflow for Enrolment & Disbursement Cycles
- [Roles & privileges](https://docs.openg2p.org/products/pbms/design/roles-and-privileges.md)
- [Post disbursement workflow](https://docs.openg2p.org/products/pbms/design/g2p-bridge-workflow.md)
- [Deployment](https://docs.openg2p.org/products/pbms/deployment.md): PBMS Deployment
- [PBMS Installation](https://docs.openg2p.org/products/pbms/deployment/deployment-instructions.md): PBMS deployment instructions
- [PBMS Helm Chart 4.x](https://docs.openg2p.org/products/pbms/deployment/pbms-helm-chart-4.x.md)
- [Configurations](https://docs.openg2p.org/products/pbms/deployment/configurations.md): The instructions here are related to configuration of base settings for PBMS using the Odoo UI
- [Domain names & certificates](https://docs.openg2p.org/products/pbms/deployment/domain-names-and-certificates.md): Domain names and certificates for PBMS
- [Developer Zone](https://docs.openg2p.org/products/pbms/developer-zone.md)
- [Repositories](https://docs.openg2p.org/products/pbms/developer-zone/repositories.md)
- [Developer Install](https://docs.openg2p.org/products/pbms/developer-zone/developer-install.md)
- [PBMS Docker](https://docs.openg2p.org/products/pbms/developer-zone/pbms-docker.md): Information regarding the PBMS Odoo, portal API, and background-task Docker images and how they are built.
- [API Reference](https://docs.openg2p.org/products/pbms/developer-zone/api-reference.md)
- [Beneficiary portal APIs](https://docs.openg2p.org/products/pbms/developer-zone/api-reference/beneficiary-portal-apis.md)
- [Staff portal APIs (for Odoo)](https://docs.openg2p.org/products/pbms/developer-zone/api-reference/staff-portal-apis-for-odoo.md)
- [Tech Guides](https://docs.openg2p.org/products/pbms/developer-zone/tech-guides.md)
- [Country Implementation Guide](https://docs.openg2p.org/products/pbms/developer-zone/tech-guides/country-implementation-guide.md)
- [Registry Database Contract](https://docs.openg2p.org/products/pbms/developer-zone/tech-guides/registry-database-contract.md)
- [Registry Addons](https://docs.openg2p.org/products/pbms/developer-zone/tech-guides/registry-addons.md)
- [Key Components](https://docs.openg2p.org/products/pbms/developer-zone/tech-guides/registry-addons/key-components.md)
- [Example Implementation Workflow](https://docs.openg2p.org/products/pbms/developer-zone/tech-guides/registry-addons/example-implementation-workflow.md)
- [Registry Connector](https://docs.openg2p.org/products/pbms/developer-zone/tech-guides/registry-connectors.md)
- [Key Components](https://docs.openg2p.org/products/pbms/developer-zone/tech-guides/registry-connectors/key-components.md)
- [Example Implementation Workflow](https://docs.openg2p.org/products/pbms/developer-zone/tech-guides/registry-connectors/example-implementation-workflow.md)
- [Summary View](https://docs.openg2p.org/products/pbms/developer-zone/tech-guides/summary-view.md): A brief discussion about the summary view in PBMS odoo user interface followed by ways to customize the same
- [Eligibility Summary View](https://docs.openg2p.org/products/pbms/developer-zone/tech-guides/summary-view/eligibility-summary-view.md)
- [Entitlement Summary View](https://docs.openg2p.org/products/pbms/developer-zone/tech-guides/summary-view/entitlement-summary-view.md)
- [Theme Extension](https://docs.openg2p.org/products/pbms/developer-zone/tech-guides/theme-extension.md)
- [Versions](https://docs.openg2p.org/products/pbms/versions.md): PBMS versions
- [SPAR](https://docs.openg2p.org/products/spar.md): Social Payments Account Registry
- [Features](https://docs.openg2p.org/products/spar/features.md): SPAR Features
- [SPAR Mapper](https://docs.openg2p.org/products/spar/features/spar-mapper.md): aka ID Account Mapper
- [SPAR Beneficiary Portal](https://docs.openg2p.org/products/spar/features/spar-self-service.md): Providing self-update features for beneficiaries via the Beneficiary Portal API
- [Privacy & Security](https://docs.openg2p.org/products/spar/features/privacy-and-security.md): SPAR Privacy & Security
- [Interoperability](https://docs.openg2p.org/products/spar/features/interoperability.md)
- [Performance & Scale](https://docs.openg2p.org/products/spar/features/performance-and-scale.md)
- [Monitoring & Reporting](https://docs.openg2p.org/products/spar/features/monitoring-and-reporting.md)
- [Deployment](https://docs.openg2p.org/products/spar/deployment.md): Deploying OpenG2P SPAR on Kubernetes using Helm charts.
- [Helm Chart](https://docs.openg2p.org/products/spar/deployment/helm-charts.md): The single, consolidated SPAR Helm chart
- [Keycloak Client](https://docs.openg2p.org/products/spar/deployment/keycloak-client.md): Historical — the Keycloak/Keymanager crypto backend removed after 1.0.0
- [Domain Names and Certificates](https://docs.openg2p.org/products/spar/deployment/domain-names-and-certificates.md): Domain names and mapping for SPAR
- [Teardown / Uninstall](https://docs.openg2p.org/products/spar/deployment/teardown.md): Completely uninstalling a SPAR release
- [User Guides](https://docs.openg2p.org/products/spar/user-guides.md)
- [Link FA (Self Service)](https://docs.openg2p.org/products/spar/user-guides/self-update-id-with-financial-address-information.md)
- [Link FA (Admin)](https://docs.openg2p.org/products/spar/user-guides/admin-guide-to-link-id-with-financial-address-information.md)
- [Development](https://docs.openg2p.org/products/spar/development.md)
- [Jira Board](https://docs.openg2p.org/products/spar/development/jira-board.md): You can find the status of the current sprints, releases and backlogs in the Jira Board.
- [Testing](https://docs.openg2p.org/products/spar/development/testing.md)
- [Unit Testing](https://docs.openg2p.org/products/spar/development/testing/unit-testing.md)
- [Functional Testing](https://docs.openg2p.org/products/spar/development/testing/functional-testing.md)
- [Performance Testing](https://docs.openg2p.org/products/spar/development/testing/performance-testing.md): Performance testing of SPAR sub modules
- [Mapper](https://docs.openg2p.org/products/spar/development/testing/performance-testing/mapper.md): Mapper Performance Testing
- [Resolve API](https://docs.openg2p.org/products/spar/development/testing/performance-testing/mapper/resolve-api.md): Performance testing of Resolve API
- [Link API](https://docs.openg2p.org/products/spar/development/testing/performance-testing/mapper/link-api.md)
- [Unlink API](https://docs.openg2p.org/products/spar/development/testing/performance-testing/mapper/unlink-api.md)
- [Update API](https://docs.openg2p.org/products/spar/development/testing/performance-testing/mapper/update-api.md)
- [Developer Install](https://docs.openg2p.org/products/spar/development/developer-install.md)
- [SPAR Mapper Partner API](https://docs.openg2p.org/products/spar/development/developer-install/spar-mapper-api.md): This guide walks through setting up the SPAR Mapper Partner API for local development. It covers the full stack: shared libraries, database, application server, and optional Docker-based setup.
- [Repositories](https://docs.openg2p.org/products/spar/development/repositories.md): The SPAR subsystem source code
- [API Reference](https://docs.openg2p.org/products/spar/development/api-reference.md)
- [Tech Guides](https://docs.openg2p.org/products/spar/development/tech-guides.md)
- [Technology Stack](https://docs.openg2p.org/products/spar/development/technology-stack.md)
- [Versions](https://docs.openg2p.org/products/spar/versions.md): SPAR Versions
- [Releases](https://docs.openg2p.org/products/spar/releases.md)
- [1.0.0](https://docs.openg2p.org/products/spar/releases/release-notes.md): SPAR Release Notes for 1.0.0
- [1.1.0](https://docs.openg2p.org/products/spar/releases/release-notes-1.md): SPAR Release Notes for 1.1.0 - WIP
- [G2P Bridge](https://docs.openg2p.org/products/g2p-bridge.md)
- [Features](https://docs.openg2p.org/products/g2p-bridge/features.md)
- [Cash, goods & services](https://docs.openg2p.org/products/g2p-bridge/features/cash-goods-and-services.md)
- [Disbursement Management](https://docs.openg2p.org/products/g2p-bridge/features/disbursement-management.md): Features for Disbursement Management
- [Funds Management](https://docs.openg2p.org/products/g2p-bridge/features/funds-management.md): Funds Management with Sponsor Bank
- [Geography Allocation](https://docs.openg2p.org/products/g2p-bridge/features/geography-allocation.md): Geography resolution
- [Warehouse Allocation](https://docs.openg2p.org/products/g2p-bridge/features/warehouse-allocation.md): Features of Warehouse allocation
- [Agency Allocation](https://docs.openg2p.org/products/g2p-bridge/features/agency-allocation.md)
- [Financial address resolution](https://docs.openg2p.org/products/g2p-bridge/features/financial-address-resolution.md)
- [Reconciliation with Sponsor Bank](https://docs.openg2p.org/products/g2p-bridge/features/reconciliation-with-sponsor-bank.md)
- [Notification to partners & beneficiaries](https://docs.openg2p.org/products/g2p-bridge/features/notification-to-partners-and-beneficiaries.md)
- [Extensibility Layer](https://docs.openg2p.org/products/g2p-bridge/features/extensibility-connect-to-sponsor-banks.md)
- [Scaling for High Volumes](https://docs.openg2p.org/products/g2p-bridge/features/scaling-for-high-volumes.md)
- [Design](https://docs.openg2p.org/products/g2p-bridge/design-specifications.md): System Design Summary
- [Partner APIs](https://docs.openg2p.org/products/g2p-bridge/design-specifications/partner-apis.md): OpenG2P G2P Bridge Partner API Documentation
- [Connectors & Extensibility](https://docs.openg2p.org/products/g2p-bridge/design-specifications/connectors-and-extensibility.md): How the G2P Bridge core stays standard while connectors are pluggable per deployment
- [Celery](https://docs.openg2p.org/products/g2p-bridge/design-specifications/celery.md): Design & architecture - Asynchronous background processes
- [Physical Organization](https://docs.openg2p.org/products/g2p-bridge/design-specifications/physical-organization.md): Physical organization of source code in the g2p-bridge monorepo
- [Example Bank](https://docs.openg2p.org/products/g2p-bridge/design-specifications/example-bank.md): openg2p-g2p-bridge-example-bank (bank simulator)
- [example-bank-models](https://docs.openg2p.org/products/g2p-bridge/design-specifications/example-bank/openg2p-g2p-bridge-example-bank-models.md): openg2p-g2p-bridge-example-bank-models
- [example-bank-api](https://docs.openg2p.org/products/g2p-bridge/design-specifications/example-bank/openg2p-g2p-bridge-example-bank-api.md): openg2p-g2p-bridge-example-bank-api
- [example-bank-celery](https://docs.openg2p.org/products/g2p-bridge/design-specifications/example-bank/openg2p-g2p-bridge-example-bank-celery.md): openg2p-g2p-bridge-example-bank-celery
- [Extensions](https://docs.openg2p.org/products/g2p-bridge/tech-guides.md): Guides for building custom implementations of the Bridge's extension points
- [Geo resolver](https://docs.openg2p.org/products/g2p-bridge/tech-guides/geo-resolver.md): Design & Implementation
- [Sponsor Bank connector](https://docs.openg2p.org/products/g2p-bridge/tech-guides/bank-connector-interface-guide.md): Design & Implementation
- [Warehouse allocator](https://docs.openg2p.org/products/g2p-bridge/tech-guides/warehouse-allocator.md): Design & Implementation
- [Agency alloctor](https://docs.openg2p.org/products/g2p-bridge/tech-guides/agency-alloctor.md): Design & Implementation
- [Financial address resolver](https://docs.openg2p.org/products/g2p-bridge/tech-guides/address-resolver.md): Design & Implementation
- [Address resolver with SPAR](https://docs.openg2p.org/products/g2p-bridge/tech-guides/address-resolver/account-mapper-resolution.md)
- [Notification connector](https://docs.openg2p.org/products/g2p-bridge/tech-guides/notification-connector.md): Design & Implementation
- [Deployment](https://docs.openg2p.org/products/g2p-bridge/deployment.md): Deploying OpenG2P G2P Bridge on Kubernetes using Helm charts.
- [Helm Chart](https://docs.openg2p.org/products/g2p-bridge/deployment/helm-charts.md): The single, consolidated G2P Bridge Helm chart
- [Keycloak Client](https://docs.openg2p.org/products/g2p-bridge/deployment/keycloak-client.md): Historical — the Keycloak/Keymanager crypto backend removed after 1.0.0
- [Partner Signing Key (.p12)](https://docs.openg2p.org/products/g2p-bridge/deployment/partner-signing-key.md): Steps to supply the Bridge's own outbound signing key (.p12) at install
- [Onboarding Partners](https://docs.openg2p.org/products/g2p-bridge/deployment/onboarding-partners.md): How to onboard a partner so its signed requests are trusted
- [Example Bank & Treasury Account](https://docs.openg2p.org/products/g2p-bridge/deployment/deployment-of-example-bank.md): The bundled Example Bank simulator and the digital-cash treasury account
- [Domain Names and Certificates](https://docs.openg2p.org/products/g2p-bridge/deployment/domain-names-and-certificates.md): Domain names and mapping for G2P Bridge
- [Dashboards (Superset)](https://docs.openg2p.org/products/g2p-bridge/deployment/dashboards.md)
- [Teardown / Uninstall](https://docs.openg2p.org/products/g2p-bridge/deployment/teardown.md): Completely uninstalling a G2P Bridge release
- [Developer Zone](https://docs.openg2p.org/products/g2p-bridge/development.md)
- [Testing](https://docs.openg2p.org/products/g2p-bridge/development/testing.md)
- [Regression Sanity Suite](https://docs.openg2p.org/products/g2p-bridge/development/testing/regression-sanity-suite.md): Black-box regression / sanity suite for an installed G2P Bridge
- [API Walkthrough (Postman)](https://docs.openg2p.org/products/g2p-bridge/development/testing/api-walkthrough.md): A hands-on, manual Postman walkthrough of the disbursement APIs (also a trainer)
- [Developer Install](https://docs.openg2p.org/products/g2p-bridge/development/developer-install.md)
- [G2P Bridge](https://docs.openg2p.org/products/g2p-bridge/development/developer-install/installing-openg2p-bridge-on-linux.md): Installation of G2P Bridge on a developer machine
- [Example Bank](https://docs.openg2p.org/products/g2p-bridge/development/developer-install/example-bank.md): Installation of Example Bank Simulator on a developer machine
- [API Reference](https://docs.openg2p.org/products/g2p-bridge/development/api-reference.md)
- [Technology Stack](https://docs.openg2p.org/products/g2p-bridge/development/technology-stack.md)
- [Versions](https://docs.openg2p.org/products/g2p-bridge/versions.md): G2P Bridge Versions
- [User Guides](https://docs.openg2p.org/products/g2p-bridge/user-guides.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 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://docs.openg2p.org/products.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.