Reconciliation compares the stored desired state with the actual RailDock model and builds targeted changes. It is not equivalent to redeploying every service on every edit.

Conceptually, changes fall into operational classes:

Use the manifest drift endpoint to surface divergence instead of silently treating the UI and repository as equally authoritative. Establish one operating rule for your team: either repository state is authoritative for managed fields, or UI changes must be folded back into the manifest before the next apply.

An apply can stop when the plan contains removals that need explicit confirmation. Automation should handle that state as a review gate, not bypass it generically.