Cross-surface requests need one explicit owner

A request can fall between tickets when one surface stores original and replacement evidence while another shows audit history without evidence access. Do not call the request complete by combining assumptions across tickets. Assign one owner for persistence, canonical history presentation, read authorization distinct from mutation authority, redaction, and multiple-retry coverage. Verify a real case before choosing the proportional fix.