Cloud portal and migration scope
The source application uses Next.js 16.3.6 with a Node.js 22.13 or later runtime requirement. The documented migration prepares the portal for Render with a separate Supabase database schema and private profile-image storage. The migration records state that database infrastructure was prepared, while final hosting, existing login configuration and image transfer remain part of cutover verification. A successful software build is not evidence that school hardware has been commissioned.
Optional Compass ACB-004 relay interface
The remote-open path sends an authenticated request through the portal server to a dedicated Raspberry Pi service, which pulses one configured relay channel. The ACB-004’s Ethernet capability is not treated as an established controller API. The implementation does not assume a proprietary packet format or synchronise the school’s access cards. Only approved, configured gate mappings may receive requests.
Electrical and local-control boundaries
The proposed interface uses electrically isolated contacts for the Roger Technology F70/IPU36 command circuit and the magnetic-lock power circuit. The local controller or approved interface must establish the lock-release and movement sequence. Public project copy is not a wiring instruction: the installed board revision, ratings, relay isolation, emergency behaviour and mechanical operation must be confirmed during on-site commissioning.
Authentication and command handling
The documented server route checks the operator session, permissions, request origin and operating priority before forwarding a request. Device credentials remain on the server. Ambiguous network failures do not cause automatic command retries. Operators need the agreed local inspection and recovery procedure before issuing a fresh request.
Acknowledgement is separate from gate position
A relay-pulse acknowledgement confirms the software request outcome; it does not establish that the gate opened, the lock released or the entrance is safe. This optional path does not provide live position, closing, safety or emergency feedback. Independently commissioned sensors and control arrangements are required where the operational scope needs those signals.
Commissioning and handover
Before operational use, the project requires verification of real operator login, approved field mappings, physical access controls, safety devices, emergency behaviour and recovery after power or communications failure. The school and RJL must agree the operating and maintenance procedures for the delivered system. These boundaries define the work still required rather than imply automatic legal protection.