Publish Immutable Routing and Price History at Deployment

Context

Historical cost and prompt attribution must remain interpretable after configuration changes.

Decision

Validate declared model configuration before deployment appends numbered routing and price versions, and retain the references used by each request.

Alternatives Considered

Overwrite current routing and price settings: It removes the historical meaning needed to explain earlier requests.

Publish when the first request arrives: It adds configuration work and races to a customer-triggered execution.

Skip invalid declarations and publish the rest: It knowingly leaves a catalogue that cannot serve all declared operations.

Consequences

Routing, prompt, budget and price changes require deployment. Reverted content appends another number without discarding history. Declared rates are not reconciled with the provider invoice. Publication commits entries separately and warm caches can retain older resolved versions.