> For the complete documentation index, see [llms.txt](https://host2host.onibonje.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://host2host.onibonje.com/docs/49-bid-proposal.md).

# Bid Proposal — Heirs Group-Wide Host-to-Host Integration Platform

**Submitted to:** Heirs Technologies / Group Integration Office\
**Offer validity:** 90 days from submission\
**Base contract value (floor):** **USD 2,000,000** (minimum guaranteed scope)\
**Extension framework:** Success-triggered optional phases — negotiated in good faith as milestones are met (Section 7.2)\
**Contract term:** **24 months** (base program); extensions up to **36 months** by mutual agreement\
**First business delivery:** **Month 8** (pilot production go-live)\
**Architecture baseline:** 48-document sign-off — [Architecture Sign-Off](/docs/42-architecture-sign-off.md)

***

## 1. Executive Summary

Heirs Technologies requires a **single, bank-grade Host-to-Host (H2H) integration platform** that standardizes corporate banking connectivity across **20+ African Finacle markets** — replacing fragmented file drops, bespoke APIs, and manual reconciliation with **straight-through processing (STP)**, **centralized governance**, and **regional execution**.

We propose to **design, build, and operationalize** that platform over **24 months** at a **base contract floor of USD 2,000,000** — the minimum investment that delivers a **production-grade platform** through pilot go-live and multi-country readiness. **USD 2.0M is not a ceiling.** As the program proves value at each milestone, both parties may activate **pre-agreed extension options** (Section 7.2) to accelerate rollout, deepen capabilities, or expand managed services — **without re-tendering the core platform**.

**Demonstrable production value at Month 8:** encrypted bulk payments from a pilot corporate partner through Finacle, with ACK delivery, full audit, and low-code configuration — **without redeploying application code** for partner or mapping changes.

**Architecture is complete.** Forty-eight signed-off design documents define modules, data models, security controls, and delivery phases. **Implementation begins on Day 1** against a proven blueprint — not discovery. That de-risks timeline and cost.

We are committed to delivery discipline: fixed milestones, measurable exit criteria, bank-side governance gates, and transparent reporting. **Base scope is fixed at USD 2.0M.** Work beyond the base program follows the **extension clause** or formal change control — never unpriced scope creep.

***

## 2. Understanding of the Challenge

| Challenge                           | Our response                                                                                                         |
| ----------------------------------- | -------------------------------------------------------------------------------------------------------------------- |
| Fragmented H2H across countries     | One composable platform; country differences via **database-driven configuration** and country packs                 |
| Slow partner onboarding             | Low-code admin portal: draft → test → **maker–checker approval** → publish                                           |
| Volume and reliability              | Apache Camel STP pipelines, idempotency, broker-delayed scheduling (survives outages)                                |
| Finacle heterogeneity (FCJ / FCUBS) | **`h2h-core-banking-api` base library** — Finacle is one CBS provider type; extensible to other core banking systems |
| Security and audit                  | PGP, Vault, Keycloak RBAC, immutable audit, segregation of duties                                                    |
| Multi-channel ingress               | SFTP, HTTP, WebSocket, MQ — all **channel\_config**-driven                                                           |
| Operational visibility              | OpenTelemetry, SLA monitoring, ops dashboard, email/SMS alerting                                                     |
| Future scale                        | Kafka event backbone, modular JARs, Kubernetes — cloud-agnostic Helm                                                 |

***

## 3. Proposed Solution

### 3.1 Platform in one view

```
Corporate / ERP / Fintech
         │
         ▼
┌────────────────────────────────────────────┐
│  H2H Gateway (SFTP · HTTP · WS · MQ)       │
└────────────────────┬───────────────────────┘
                     ▼
┌────────────────────────────────────────────┐
│  Apache Camel Runtime (composable JARs)    │
│  Transform → Validate → Idempotency → CBS  │
└────────────────────┬───────────────────────┘
                     ▼
              Finacle (FCJ / FCUBS)
                     │
         ACK / NACK / Statements / Events
```

### 3.2 Technical foundation (locked)

| Layer              | Technology                                                                | Business outcome                         |
| ------------------ | ------------------------------------------------------------------------- | ---------------------------------------- |
| Integration engine | Apache Camel                                                              | Banking-proven EIP; surgical JAR updates |
| Configuration      | RDBMS (PostgreSQL / Oracle / SQL Server)                                  | No partner logic in code                 |
| Core banking       | **`h2h-core-banking-api` base library** + CBS providers (Finacle default) | One contract; extensible CBS types       |
| Events             | Kafka + **database-driven** `event_def`                                   | Extensible without redeploy              |
| Jobs / schedules   | Broker-delayed messages                                                   | No missed EOD after outage               |
| Approvals          | Camunda + `h2h-workflow`                                                  | Maker–checker, multi-level sign-off      |
| Notifications      | Email / SMS SPI (Africa's Talking, SES, etc.)                             | Ops and checker alerts                   |
| Security           | Vault, PGP, Keycloak                                                      | Enterprise IAM and secrets               |
| Runtime            | **Deployment-agnostic** — K8s, standalone JAR, legacy WAR                 | Cloud, on-prem DC, or hybrid             |

### 3.3 What the bank operates (deliverables)

| Deliverable                             | Description                                                                            |
| --------------------------------------- | -------------------------------------------------------------------------------------- |
| **`h2h-runtime`**                       | Production integration engine — **executable JAR, WAR, or K8s image** (bank's profile) |
| **`h2h-core-banking-api`**              | CBS base library (vendor-neutral contract)                                             |
| **`h2h-finacle-wrapper`**               | Finacle CBS provider type (default for Heirs)                                          |
| **Admin portal**                        | Partner onboarding, mappings, publish center, ops dashboard                            |
| **Admin API**                           | REST control plane for configuration and operations                                    |
| **30+ Maven modules**                   | Payments, file management, Finacle, security, events, workflow, notifications          |
| **Flyway schema + seed data**           | Config, events, approvals, notifications                                               |
| **Helm charts + legacy install guides** | K8s (Profile A) and VM/app-server (Profiles B/C)                                       |
| **CI/CD pipeline**                      | Build, test, security scan, artifact publish                                           |
| **Runbooks & training**                 | Per [41 Training and Handover](/docs/41-training-and-handover.md)                      |
| **Architecture corpus**                 | 48 documents (maintained in repository)                                                |

***

## 4. Delivery Plan — 24 Months, First Value at Month 8

### 4.1 Milestone summary

| Milestone                          | Month | Business outcome                                                   | Payment (USD) |
| ---------------------------------- | ----- | ------------------------------------------------------------------ | ------------- |
| **M0 — Contract & mobilization**   | 0     | Team onboarded, environments provisioned, Finacle access confirmed | 150,000       |
| **M1 — Foundation complete**       | 4     | Config store live, Finacle sandbox post, SFTP ingest, CI/CD green  | 250,000       |
| **M2 — First production delivery** | **8** | **Pilot partner: SFTP bulk payment STP + ACK + admin MVP**         | **400,000**   |
| **M3 — API & operations channel**  | 12    | REST payments, Kafka events, ops dashboard, notifications          | 350,000       |
| **M4 — Full product suite**        | 18    | Collections, MT940 statements, reconciliation workbench            | 400,000       |
| **M5 — Multi-country readiness**   | 22    | Country pack framework, 2nd market pilot, partner portal MVP       | 300,000       |
| **M6 — Program closure**           | 24    | Hypercare complete, knowledge transfer, sign-off                   | 150,000       |
|                                    |       | **Base program total**                                             | **2,000,000** |

```mermaid
gantt
    title Bid Delivery Timeline (24 months)
    dateFormat YYYY-MM
    axisFormat %b %Y

    section Phase 1
    Foundation and CI/CD           :p1, 2026-07, 4M

    section Phase 2
    MVP Bulk Payments Pilot          :p2, after p1, 4M

    section Phase 3
    API Events Ops Dashboard         :p3, after p2, 4M

    section Phase 4
    Collections Statements Recon     :p4, after p3, 6M

    section Phase 5
    Country Pack 2nd Market          :p5, after p4, 4M

    section Milestones
    M2 First Production Go-Live      :milestone, m2, after p2, 0d
    M3 API Channel Live              :milestone, m3, after p3, 0d
    M5 Platform Feature Complete     :milestone, m5, after p5, 0d
```

### 4.2 Month 8 — First delivery (detailed)

**Objective:** Prove end-to-end STP for one corporate partner in one production country.

| Capability    | Included                                                          |
| ------------- | ----------------------------------------------------------------- |
| Inbound       | PGP-encrypted CSV via SFTP                                        |
| Processing    | Validate → transform → idempotency → Finacle post                 |
| Outbound      | ACK/NACK file to partner outbox                                   |
| Control plane | Partner wizard, mapping editor, test harness                      |
| Governance    | Maker–checker publish workflow                                    |
| Audit         | Correlation ID end-to-end; immutable config and transaction trail |
| Security      | Vault credentials, Keycloak RBAC                                  |
| Resilience    | Retry, DLQ, global error handler                                  |

**Acceptance tests (representative):**

1. Pilot partner uploads production payment file; ≥99% valid lines post to Finacle within SLA.
2. ACK delivered within configured `ACK_DELIVERY_TIME`.
3. Duplicate file rejected; no double payment.
4. Config mapping change published by analyst, approved by supervisor — **next file uses new mapping without JAR redeploy**.
5. Security sign-off on PGP, IAM, and audit sampling.

### 4.3 Months 9–24 — Platform expansion

| Period    | Technical scope                                                                                                      | Business scope                                                  |
| --------- | -------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------- |
| **9–12**  | REST API ingress, Kafka/`event_def`, HTTP/WebSocket channels, ops dashboard, email/SMS alerts, webhook subscriptions | Real-time API partners; NOC visibility; SLA breach notification |
| **13–18** | Collections routes, ISO 20022 / MT940, reconciliation engine + workbench                                             | Bill collections; statement delivery; settlement matching       |
| **19–24** | Country pack import/export, 2nd country config pilot, partner portal MVP, DR runbook execution, hypercare            | Second market go-live path; self-service status; handover       |

***

## 5. Scope Boundaries

### 5.1 In scope — base program (USD 2.0M floor)

* All items in Section 4 and architecture docs 01–48
* One **pilot production partner** at Month 8; one **second-country configuration pilot** by Month 22
* Finacle FCJ/FCUBS integration for payment, collection, and statement flows defined in roadmap
* Sandbox + UAT + production environment **deployment support** (Helm); bank provides infrastructure
* Training per [41 Training and Handover](/docs/41-training-and-handover.md): integration analysts (3 days), ops (2 days), architects (1 day)
* **8 weeks hypercare** after Month 8 go-live; **4 weeks** after Month 22

### 5.2 Out of scope — base program (extension-eligible)

The items below are **not included in the USD 2.0M floor** but are available under **Section 7.2 Extension Options** once success triggers are met, or via ad-hoc change request at any time.

| Item                                                       | Extension path                                   |
| ---------------------------------------------------------- | ------------------------------------------------ |
| Finacle licensing / CBS infrastructure                     | Bank responsibility                              |
| Accelerated multi-country rollout (3+ countries in Year 2) | **EXT-01** Country acceleration pack             |
| Additional CBS provider adapters (non-Finacle)             | **EXT-02** CBS adapter program                   |
| Hardware / cloud consumption costs                         | Bank or separate infra contract                  |
| 24×7 managed operations (MSO)                              | **EXT-03** Managed services retainer             |
| Penetration test execution                                 | Bank vendor; we provide remediation support (CR) |
| Treasury / FX advanced interfaces                          | **EXT-04** Treasury module                       |
| Extended hypercare beyond base weeks                       | **EXT-05** Hypercare extension                   |
| Partner portal full feature set                            | **EXT-06** Portal expansion                      |

***

## 6. Team & Governance

### 6.1 Vendor delivery team (steady-state average)

| Role                           | FTE  | Responsibility                                   |
| ------------------------------ | ---- | ------------------------------------------------ |
| Solution Architect / Tech Lead | 1.0  | Architecture integrity, Finacle/CBS, code review |
| Senior Java Engineers          | 2.5  | Camel, modules, config runtime, integrations     |
| Frontend Engineer              | 1.0  | Admin portal, ops UI                             |
| DevOps / SRE                   | 0.75 | K8s, CI/CD, Vault, Kafka, monitoring             |
| QA / Test Automation           | 1.0  | Integration, regression, load (Phase 3+)         |
| Business Analyst               | 0.75 | UAT, partner specs, acceptance                   |
| Finacle SME                    | 0.5  | FCJ/FCUBS mapping, sandbox, cut-over             |
| Program Manager                | 0.5  | Plan, RAID, steering, commercial                 |

**Peak (Months 1–8):** \~8 FTE. **Taper (Months 19–24):** \~5 FTE.

### 6.2 Bank-side prerequisites (critical path)

| Dependency                                                                            | Required by |
| ------------------------------------------------------------------------------------- | ----------- |
| Finacle sandbox + FCJ/FCUBS credentials                                               | Month 1     |
| Kubernetes cluster (dev/UAT/prod) **or** VM/app-server targets per deployment profile | Month 2     |
| Vault and Keycloak integration with bank AD                                           | Month 3     |
| Pilot partner nomination + file format spec                                           | Month 5     |
| Security architecture approval                                                        | Month 6     |
| Production cut-over window approval                                                   | Month 8     |

### 6.3 Governance cadence

| Forum                   | Frequency | Purpose                           |
| ----------------------- | --------- | --------------------------------- |
| Steering committee      | Monthly   | Scope, risk, milestone acceptance |
| Technical design review | Bi-weekly | Architecture compliance           |
| Sprint demo             | Bi-weekly | Working software                  |
| RAID log                | Weekly    | Blockers, dependencies            |

***

## 7. Commercial Terms

### 7.1 Base contract (floor)

| Term                            | Value                                                                                    |
| ------------------------------- | ---------------------------------------------------------------------------------------- |
| **Base contract value (floor)** | **USD 2,000,000** — minimum; not a ceiling                                               |
| **Currency**                    | United States Dollars                                                                    |
| **Base duration**               | 24 months from contract effective date                                                   |
| **Payment basis**               | Milestone acceptance (Section 4.1)                                                       |
| **Invoicing**                   | Net 30 on signed milestone acceptance certificate                                        |
| **Change control**              | Written CR for work outside base scope and outside activated extensions                  |
| **IP**                          | Bank owns bespoke configuration and country packs; platform source per contract schedule |
| **Warranty**                    | 90-day defect remedy on delivered software post each milestone                           |

**Payment profile:** USD 800K cumulative through Month 8 (foundation + first production delivery). Remaining USD 1.2M funds platform expansion through Month 24. **This floor delivers a complete, operable platform** — not a prototype with hidden follow-on costs for core capability.

### 7.2 Success-based extension clause

Both parties acknowledge that **platform value increases non-linearly** after first production go-live: partner onboarding accelerates, country packs reuse configuration, and operational confidence grows. To align commercial terms with that trajectory, the following **optional extension framework** is embedded in the base contract. Extensions are **activated by mutual written agreement** — typically at steering committee following a success trigger — **without a new RFP for the core platform**.

#### Extension activation principles

| Principle                     | Application                                                                                     |
| ----------------------------- | ----------------------------------------------------------------------------------------------- |
| **Success first**             | Extensions offered after defined triggers — not assumed Day 1                                   |
| **Pre-priced options**        | Indicative rates below; final SOW negotiated per activation                                     |
| **No obligation**             | Bank may decline any extension; base program completes at USD 2.0M                              |
| **Good-faith negotiation**    | Rates adjust ±15% based on volume, timeline compression, and bank-side resource contribution    |
| **Cumulative cap (optional)** | Parties may agree a **program ceiling** (e.g. USD 4.0M–5.0M over 36 months) at contract signing |

#### Pre-agreed extension catalog

| ID         | Extension                                                                                    | Typical trigger                              | Indicative range (USD)                   | Duration       |
| ---------- | -------------------------------------------------------------------------------------------- | -------------------------------------------- | ---------------------------------------- | -------------- |
| **EXT-01** | **Country acceleration** — 3–5 additional country packs (config, UAT, hypercare per country) | M2 accepted + steering approval to expand    | **$240K – $600K** ($80K–$120K × country) | 6–12 months    |
| **EXT-02** | **Additional CBS provider** — new `h2h-cbs-{vendor}` adapter + mapping                       | Acquisition or non-Finacle market identified | **$150K – $350K** per CBS type           | 3–6 months     |
| **EXT-03** | **Managed services (MSO)** — L2/L3 support, monitoring, release management                   | M3 accepted; ops team requests vendor run    | **$120K – $250K / year**                 | Annual renewal |
| **EXT-04** | **Treasury module** — FX, liquidity interfaces per doc 27                                    | Treasury product owner sign-off post-M4      | **$200K – $400K**                        | 4–6 months     |
| **EXT-05** | **Extended hypercare** — +4 weeks per major go-live                                          | Post go-live incident rate or partner volume | **$40K – $80K** per period               | Per event      |
| **EXT-06** | **Partner portal expansion** — full self-service, API catalog, sandbox automation            | M5 accepted; partner demand confirmed        | **$100K – $200K**                        | 3–4 months     |
| **EXT-07** | **Program year 3** — continuous improvement, regulatory changes, performance tuning          | M6 accepted; 12-month renewal                | **$400K – $800K**                        | 12 months      |
| **EXT-08** | **Compliance / screening integration** — sanctions, AML hooks                                | Compliance mandate post-M2                   | **$80K – $180K**                         | 2–4 months     |

#### Success triggers (recommended)

| Trigger                        | Milestone                                  | Extension commonly discussed                 |
| ------------------------------ | ------------------------------------------ | -------------------------------------------- |
| **T1 — Production proof**      | M2 accepted (Month 8)                      | EXT-01 (country rollout), EXT-05 (hypercare) |
| **T2 — Channel scale**         | M3 accepted; ≥2 API or event partners live | EXT-03 (MSO), EXT-06 (portal)                |
| **T3 — Product completeness**  | M4 accepted; recon in production use       | EXT-04 (treasury), EXT-08 (compliance)       |
| **T4 — Group rollout mandate** | Board approval for ≥5 countries            | EXT-01 at volume discount                    |
| **T5 — Program renewal**       | M6 accepted                                | EXT-07 (year 3)                              |

#### Extension negotiation process

1. **Steering committee** reviews milestone evidence and business case.
2. **Vendor** submits extension SOW referencing catalog ID(s) and indicative range.
3. **Parties negotiate** scope, price within range, timeline, and bank dependencies (30-day target).
4. **Written amendment** signed; work begins; **separate milestone schedule** where applicable.
5. **Base contract** remains in force; extensions are additive.

**Illustrative program trajectory (not a commitment):**

| Scenario               | Base + extensions                                                       | Timeline     | Outcome                                             |
| ---------------------- | ----------------------------------------------------------------------- | ------------ | --------------------------------------------------- |
| **Floor only**         | USD 2.0M                                                                | 24 months    | Platform complete; 1 pilot + 1 country config pilot |
| **Moderate success**   | USD 2.0M + EXT-01 (3 countries) + EXT-03 (1 yr MSO) ≈ **$2.6M – $3.1M** | 24–30 months | 4 countries live; vendor-supported ops              |
| **Full group mandate** | USD 2.0M + EXT-01 (8 countries) + EXT-03 + EXT-07 ≈ **$3.5M – $4.8M**   | 36 months    | Pan-African rollout path; year-3 sustainment        |

This structure **protects the bank's downside** (firm USD 2.0M floor for defined delivery) and **aligns vendor incentive** with measurable success — we grow when the platform proves itself in production.

***

## 8. Risk Management & Quality

| Risk                             | Mitigation                                                         |
| -------------------------------- | ------------------------------------------------------------------ |
| Finacle access delayed           | Mock `CoreBankingIntegration` from Month 1; parallel sandbox track |
| Scope creep (unpriced)           | Base floor fixed; extensions via Section 7.2 only                  |
| Partner UAT slip                 | Sandbox from Month 6; dedicated BA from Month 4                    |
| Security gate delay              | Security architect engaged Month 1; align to doc 09                |
| Production incident post go-live | 8-week hypercare; runbooks per doc 34                              |

**Quality gates:** Unit + integration tests in CI; ArchUnit architecture rules; SonarQube quality gate; milestone acceptance scripts derived from [22 Use Cases](/docs/22-use-cases-and-solutions.md).

***

## 9. Why This Proposal Is Credible at USD 2.0M Floor

1. **Architecture is already done.** Forty-eight signed-off documents eliminate months of design churn. Build starts immediately.
2. **Composable JAR model.** Update one module — not the monolith — reducing long-term cost of change.
3. **Configuration over code.** Partner onboarding is analyst work, not developer sprints — the economic model scales across 20+ countries.
4. **Month 8 is achievable.** Phases 1–2 are explicitly scoped in [10 Implementation Roadmap](/docs/10-implementation-roadmap.md); MVP range in [44 Program Cost](/docs/44-program-cost-and-staffing.md) supports this timeline at disciplined staffing.
5. **USD 2.0M is a firm floor, not a cap.** The base program delivers production-grade capability; the **extension clause** lets both parties scale investment in line with proven ROI — without reopening the core platform procurement.
6. **Aligned incentives.** We succeed when M2 goes live and partners onboard; extension options reward that outcome for both sides.

## 10. Acceptance & Sign-Off

| Milestone | Signatory                               | Evidence                                             |
| --------- | --------------------------------------- | ---------------------------------------------------- |
| M1        | Platform Lead + Solution Architect      | Foundation exit criteria (doc 10 §3)                 |
| M2        | Business Owner + Integration Supervisor | Pilot UAT sign-off, production traffic sample        |
| M3        | Head of Operations                      | API channel live, ops dashboard operational          |
| M4        | Reconciliation / Product Owner          | Collections + recon UAT                              |
| M5        | Country Integration Admin               | 2nd country pack imported and tested                 |
| M6        | Program Sponsor                         | Training complete, hypercare exit, final RAID closed |

***

## 11. Proposal Acceptance

|                          |                                                                    |
| ------------------------ | ------------------------------------------------------------------ |
| **Vendor**               | \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ |
| **Authorized signatory** | \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ |
| **Date**                 | \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ |

|                                 |                                                                    |
| ------------------------------- | ------------------------------------------------------------------ |
| **Client — Heirs Technologies** | \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ |
| **Authorized signatory**        | \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ |
| **Date**                        | \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ |

***

## 12. References

| Document                                                              | Relevance              |
| --------------------------------------------------------------------- | ---------------------- |
| [01 Architecture Overview](/docs/01-architecture-overview.md)         | Strategic scope        |
| [10 Implementation Roadmap](/docs/10-implementation-roadmap.md)       | Phase deliverables     |
| [22 Use Cases and Solutions](/docs/22-use-cases-and-solutions.md)     | Acceptance scenarios   |
| [42 Architecture Sign-Off](/docs/42-architecture-sign-off.md)         | Completeness gate      |
| [44 Program Cost and Staffing](/docs/44-program-cost-and-staffing.md) | Planning baseline      |
| [Repository](https://github.com/Onibonje-Solution/docs)               | Published architecture |

***

*This proposal is based on the Heirs H2H Platform architecture documentation set. Technical detail for any deliverable is traceable to the numbered design documents in this repository.*


---

# 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://host2host.onibonje.com/docs/49-bid-proposal.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.