# RBE Handover RC1 - Start Here

This is **Release Candidate 1 (RC1)** for independent deployment validation. It is intended to be tested on a clean server before the final delivery package is sealed.

## What is included

- `application/v1/` - RBE V1 companion/entry application.
- `application/v2/` - RBE V2 application.
- `database/rbe_handover_RC1_VALIDATION.sql` - current corrected **shortened validation database**.
- `config/` - configuration examples and server templates.
- `docs/` - deployment, environment, integration, cron and V1/V2 operating notes.
- `handover-checklist/` - signed handover checklist and package mapping.

## Important RC1 limitation

The database in RC1 is the shortened handover-preparation database used to validate the standalone application and deployment process. It is **not the final full historical RBE database export**. The final package will replace it with a fresh full RBE operational export after the clean-server dry run has passed.

RC1 also retains the current working administrative test credential state so the package can be validated. That credential state must be rotated/neutralised before final delivery.

## Recommended reading order

1. `docs/DEPLOYMENT_NOTES.md`
2. `docs/ENVIRONMENT_REQUIREMENTS.md`
3. `docs/CONFIGURATION_NOTES.md`
4. `docs/V1_V2_OPERATION_NOTES.md`
5. `docs/CRON_JOBS.md`
6. `docs/API_AND_FLECTO_NOTES.md`
7. `database/README_DATABASE.md`
8. `docs/RC1_VALIDATION_CHECKLIST.md`
9. `handover-checklist/DELIVERY_MAPPING.md`

## Core deployment concept

V1 and V2 are separate companion applications using the **same standalone RBE database** and, when hosted below a shared parent domain, the **same PHP session cookie**. V1 remains the normal entry application and contains the bridge into V2.

Example:

- V1: `https://legacy.rbe-example.co.za`
- V2: `https://app.rbe-example.co.za`
- shared cookie domain: `.rbe-example.co.za`

Do not merge the two application trees during handover deployment.