Logo change: record to derived views Diagram

Authority first

The brands table with logo_v is the single authority
A logo change is one atomic UPDATE plus one outbox event
Products keep only brand_id, never a blind copy

Versioned propagation

The builder applies guarded writes with logo_v < new_v
Duplicates die on the version guard, order decides
The cursor (logo_v, product_id) is the resume point after death

Bounded staleness

Lag is observed against the 5 s teaching budget
Past the budget readers fall back to the authority table
Sync embedding has no cursor and no budget, only a blind window