UI pattern for eventually-consistent systems: instead of synchronously rejecting invalid input, accept the command, record the submission as an event, and let aggregators produce different views per audience. Example: a user submits an offensive video title; viewers continue seeing the previously valid name while the uploader sees a 'please fix this' view. Validations are elevated from the persistence layer into the domain as first-class service logic, and the UI polls by command ID to know when processing is complete.