# Fast config convergence for unit-backed apps (issue #44). The agent's
# configGenLoop touches this file when a config write moves the generation
# object of an app with carlos-app@ routes on this box: the agent renders
# exec-backed instances itself, but it cannot write /etc/carlos/apps or
# restart units, so it asks a root pass to do both. It starts
# carlos-config-sync.service — the CONFIG half alone, deliberately NOT
# carlos-adopt.service: a per-config-write trigger must never run release
# adoption or the canary-TTL nag, which stay on carlos-adopt.timer's hourly
# cadence. /data is hardcoded like every path in these unit files — a box
# with a nonstandard data dir simply never fast-triggers and keeps that
# hourly floor.
[Unit]
Description=CARLOS config sync on agent request (config fast convergence)

[Path]
PathChanged=/data/config-sync-requested
Unit=carlos-config-sync.service

[Install]
WantedBy=multi-user.target