Don't bend event schemas to accommodate UI needs. Adding UI-derived fields (e.g. a category_id computed from a heuristic) inverts the dependency direction, couples core events to presentation, and introduces new reasons for event schemas to change — which, in an immutable store, invalidates historical events. Compose views by projecting from multiple streams and using aggregation techniques instead.