The operator problem
Route-server configuration grows beyond the script that started it.
As an exchange grows, peer data, IRR policy, RPKI state, templates, generated sidecars, deployment and public visibility must agree. A render script alone cannot explain desired state, host drift or partial rollout.
- Input data changes independently across multiple systems
- Push deployment increases blast radius and host coupling
- Policy changes need preview, validation and stable identity
