Upgrade + Recording¶

Upgrade guidance for Sorcery producers/consumers with minimum operational ceremony.

Upgrade contract¶

Before rollout, confirm:

• Consumers accept producer ring version
• Consumers accept message schema_ver
• Metadata readers accept metadata version

If any check fails, do not deploy mixed versions.

Upgrade sequence¶

1. Drain/disable strategy actions that depend on affected producers.
2. Upgrade binaries/configs (metad, feedd, orderd) in your standard rollout order.
3. Verify STATUS liveness (conn_state, last_rx_age_ns, reconnect trend).
4. Force reconciliation before re-enabling decisions:
5. Market data: snapshot recovery where needed
6. Order routing: QUERY_ORDERS + QUERY_BALANCES

Rollback trigger¶

Rollback immediately on:

• Parse/version mismatch
• Reconnect storm after deploy
• Repeated unresolved recovery failures

Recording / replay¶

If you capture sessions for diagnostics:

• Record raw ring frames (header + payload) with capture timestamp
• Preserve original ordering domains during replay
• Never treat replay outputs as live-trading signals