Use a matched development installation
This guide describes the September 8 Hagency/Palpo admin integration. It requires the companion web-admin service, the matching Hagency bridge, and Palpo application-service support. Published releases alone do not establish this workflow.
Authorize and pair
A Palpo administrator authorizes a fleet for an identified local owner using outbound transport. The companion service installs a scoped Appservice registration pointing to its server-side relay. The fleet owner downloads only that fleet’s configuration and imports it into Hagency, which initiates HTTPS polling and state publication.
Import the configuration into the corresponding Hagency instance. Keep service credentials in the intended private store. Installation and credential delivery leave the fleet pending until the connection itself is verified.
Prove the event round trip
Use the connection verification action. The bridge must prove receipt of the exact probe event through the application-service path, with the expected reception-room membership. A simple HTTP response or reading the event back is not sufficient.
In the current outbound transport, the exact current-generation probe establishes the connection and background heartbeats maintain liveness. Request observations have separate freshness checks. Preserve request identity during recovery. Earlier callback deployments retain their explicit verification-expiry rules until migrated.