AI-Safe Handover & Change Tracking System

Every page, section, module and component gets its own handover so any AI can safely modify the system later.

RegistriesMap

Module, route, database, file and component registries tell future AI where things live and what they affect.

HandoversExplain

Each module, page and component has a handover covering purpose, files, dependencies, impacts and danger zones.

Change manifestsTrack

Every patch must record what changed, why, what was tested and which handovers were updated.

Required AI change process

1. Read AI entrypoint

2. Find affected areas

3. Read handovers

4. Check impact map

5. Plan change

6. Back up files

7. Patch safely

8. Validate

9. Update handovers

10. Update registries

11. Create manifest

12. Run audit

Hard rules

No backend page without a page handover.
No shared component without a component handover.
No route change without updating the route registry.
No database migration without updating the database registry.
No booking logic change without checking resident, retail, panel, service, payment and meeting-record impacts.
No payment change without checking bookings, service orders, refunds, receipts and owner reporting.
Every patch must update relevant handovers, registries and changelog.

Current documentation root

/var/www/ssbookings/docs

/opt/jfmsrv01/scripts/SSBOOKINGS-AI-HANDOVER-SYSTEM.md

/opt/jfmsrv01/scripts/ssbookings-handover-audit.sh