Current-record owner activation review
Pending owner-building reviews follow the applicant, approved owner, existing building and reviewer authority actually checked. Changed records require an explicit affected review before private activation.
- Improvements and fixes
Current review evidence: Changes to the saved applicant, canonical owner or matched existing building invalidate affected pending reviews. Revoked, relinked or reassigned reviewers cannot leave their old review valid. Earlier evidence and review history are retained; repeating one affected review does not invalidate an independent current review.
- New
Actionable review flags: The authorised Accountant or CEO sees a red warning identifying the changed binding or review. The activation control stays disabled until both current reviews pass. Internal binding hashes are not exposed in browser projections; applicants and assigned Operations retain their existing limited view.
- Improvements and fixes
Agreement validity dates: Review display and server activation use the same Saudi start-of-day and inclusive end-of-day boundary. An agreement outside its recorded validity dates produces an explicit review warning.
The existing company decision, applicant isolation, private inventory, billing and access controls remain. No production building is activated and no account, role, fee, invitation or message is created by this release. Earlier pending reviews without current-record bindings require explicit review; their stored evidence is preserved. Synthetic workflow verification and native read-only production verification are labelled separately. Broader independent-role and gateway reliability acceptance remain open.