Handover, Deposit, And Final Settlement Release Requirements¶
Date: 2026-06-24
Status: Accepted for EP4-T1.
Launch Handover Requirements¶
The launch handover flow must support:
- move-in protocol
- move-out protocol
- protocol items
- item condition
- item notes
- item photo
- owner confirmation
- tenant confirmation
- tenant decline with reason
- replacement of a declined protocol without deleting the original
- audit records for create, update, delete, confirmation, decline, and replacement
- copy that frames confirmations as saved evidence or acknowledgement, not legal advice or a guaranteed legal result
Rooms, areas, meter readings, and keys may be represented as protocol items for the pilot. Dedicated structured fields are not required before the first paid pilot.
Deposit Ledger V1 Requirements¶
The launch backend must support one deposit ledger per lease with owner-only writes and participant reads. The ledger must track deposit due, collected, deductions, refundable amount, returned amount, disputed amount, vacated date, and derived refund due date.
Deduction rows must track category, amount, description, optional evidence asset, and creator.
Final Settlement Boundary¶
Final settlement can continue using the existing confirmation flow in this slice. EP4-T5 and EP4-T6 will harden settlement statement details and evidence export after the deposit ledger contract exists.
Legal Boundary¶
The app must not claim legal advice, guaranteed legal validity, automatic claim enforcement, or court-ready completeness. It stores structured evidence and acknowledgements for owner and tenant review.