Publish the operation catalog at deploy
What It Does
Engineers change declared prices and routing; deployment validates their complete catalogue before any append.
The Flow
Rates are appended first, then operation versions. Matching digests retain their existing number.
When Something Fails
A persistence failure stops publication but preserves earlier committed appends. Those prices can already affect requests for existing routing.
Open Design Questions
Catalogue-wide atomicity and warm-cache convergence are not implemented guarantees.