# AI integration project brief

A working template from PlatformBridge. Complete this with the process owner,
system owners, and proposed delivery team. Mark unknowns explicitly; a blank
answer is not an approved assumption.

Companion guide: https://www.platformbridge.ai/guides/ai-integration-services

## 1. The business transaction

- Process and accountable owner:
- Trigger and representative input:
- Confirmed business outcome that counts as complete:
- Current volume, handling time, delay, and rework (include measurement period):
- Why a model is needed; simpler alternatives considered:
- Cases excluded from this release:

## 2. Systems and data access

| System / owner | Supported interface | Identity used | Allowed records and fields | Freshness requirement | Access evidence |
| -------------- | ------------------- | ------------- | -------------------------- | --------------------- | --------------- |
|                |                     |               |                            |                       |                 |

- Data sent to approved external services:
- Hosting account, retention settings, and credential owner:
- Required access still unavailable; person responsible and target date:

## 3. Proposed and permitted changes

| Action | Fields that may change | Required validation | Approver | Approval expiry / invalidation | Completion receipt |
| ------ | ---------------------- | ------------------- | -------- | ------------------------------ | ------------------ |
|        |                        |                     |          |                                |                    |

- How changes after approval are detected:
- Duplicate protection and its documented limits:
- Behavior when a write's outcome is unknown:
- Operator reconciliation procedure and owner:

## 4. Acceptance evidence

| Case                                      | Expected destination state | Expected operator action | Evidence / test result | Accepted by |
| ----------------------------------------- | -------------------------- | ------------------------ | ---------------------- | ----------- |
| Normal request                            |                            |                          |                        |             |
| Duplicate delivery                        |                            |                          |                        |             |
| Ambiguous record match                    |                            |                          |                        |             |
| Response lost after a write               |                            |                          |                        |             |
| Record changes after approval             |                            |                          |                        |             |
| Access revoked                            |                            |                          |                        |             |
| Dependency unavailable beyond retry limit |                            |                          |                        |             |

Set acceptance criteria before testing. Document unresolved limits and the
decision to narrow, fix, or stop the release.

## 5. Delivery, cost, and operation

- Build milestones and client dependencies:
- Implementation fee and exclusions:
- Recurring platform / model / infrastructure costs and assumptions:
- Review, correction, and support effort:
- Named owner for monitoring, credential rotation, and upstream API changes:
- Support hours and escalation arrangement:
- Pause, recovery, and rollback procedure (including actions that cannot be undone):
- Handover: access, source or usage rights, deployment instructions, tests, runbook:
- Release decision, owner, date, and evidence version: