# Signed Checklist Delivery Mapping

This file maps the signed handover checklist items to the handover package. The signed PDF remains the controlling checklist record supplied in this directory.

## Additional V1 inclusion
Although the signed checklist is titled RBE V2, V1 is also included in the delivery by subsequent agreement because V1 remains part of the current operating flow and contains the bridge into V2.

## Checklist mapping

1. **RBE V2 application files**
   - `application/v2/`
   - V1 companion application additionally supplied at `application/v1/`

2. **RBE V2 database export**
   - Final delivery: `database/` final RBE SQL export
   - RC1 carries `database/rbe_handover_RC1_VALIDATION.sql`, a shortened validation export only; see `database/README_DATABASE.md`. The final delivery will replace it with the final full RBE export.

3. **Configuration files/templates**
   - `application/v1/config/app.php`
   - `application/v2/core/config.php`
   - `config/ENVIRONMENT_VARIABLES.example`
   - `docs/CONFIGURATION_NOTES.md`

4. **Environment requirements**
   - `docs/ENVIRONMENT_REQUIREMENTS.md`

5. **Scheduled/cron jobs**
   - `docs/CRON_JOBS.md`

6. **API documentation/details**
   - `docs/API_AND_FLECTO_NOTES.md`
   - `application/v2/TL300 Flecto Sense Rest API V1.6 Doc v1.6.pdf`

7. **Deployment instructions**
   - `docs/DEPLOYMENT_NOTES.md`

8. **Handover checklist**
   - signed checklist PDF in `handover-checklist/`
   - this delivery mapping

9. **Current RBE V2 configuration**
   - `docs/CONFIGURATION_NOTES.md`
   - `docs/V1_V2_OPERATION_NOTES.md`
   - central config files in V1/V2

10. **Data necessary for RBE V2 to operate independently**
   - standalone V1/V2 application copy
   - final standalone RBE database export
   - config templates
   - cron/API/setup notes
   - V1/V2 session/bridge notes

11. **Technical documentation**
   - documents under `docs/`
   - API PDF retained in V2
   - database notes
   - checklist/delivery mapping

## Acceptance boundary
This mapping confirms package contents only. It does not represent installation, migration, successful testing, security hardening or production operation in RBE's destination environment.