Integration Scenarios:

systemd Persistent Service

• Shell Execution Context: Robot Administrator.
• Risk Level: High Risk. Writes system unit files, modifies boot behavior, and launches a persistent daemon process capable of invoking recording functions.
• Prerequisites: Reviewed examples/platform_bridge/realbot-record-bridge.service.example from the delivery package (obtained through delivery channels), backed up any existing unit with the same name, and verified installation directories, ROS 2 source paths, user permissions, rollback procedures, and token rotation plans.

The systemd template defaults to binding strictly to 127.0.0.1. Tokens MUST be loaded exclusively from /etc/realbot-record-bridge.env and NEVER written directly into unit files or ExecStart arguments. The credential file MUST be owned by root with strictly restricted read permissions. Modifying the token requires restarting the service and updating the platform key simultaneously.

This manual does NOT automatically execute systemctl enable --now. Upon authorized deployment, verify the copied unit using systemd-analyze verify, manually start the service, and complete authentication and closed-loop acceptance per the Recommended Loopback + SSH Tunnel Pathway before deciding whether to enable boot startup. Rollback consists of stopping and disabling the new unit, restoring the backup unit, and executing daemon-reload.