betaFeedback

WorksComputer Science

Who May Release, Who Must Repair: Separating Authorization from Report Accountability in Personalized Services

Abstract

Personalized services often rely on different parties to compute results and decide whether data permissions and service policies allow delivery. The computing party's report may omit permitted inputs, leaving the delivery party to decide whether to wait for correction. Requiring correction first can delay service despite valid input permissions. Delivering first instead requires preserving responsibility for the incomplete report. We design an interface that checks input permissions separately from reporting requirements and records who must correct omissions and who may verify corrections. We evaluate three implementations on scripted histories and generated cases against a design treating omissions as authorization failures. When policy permits delivery before correction, our interface releases results that the alternative withholds while preserving repair assignments. These assignments remain in force through policy changes, so changing delivery rules does not erase earlier obligations. The interface makes the basis for release and outstanding repair responsibilities traceable across cooperating parties.

Paper details

vlnc:W_5mtc7d6u
Version
v1 · latest
Published
Fresh — added to the Hub within the last 30 days
Added
License
arXiv nonexclusive license
Usage

views · 0

downloads · 0

A view counts once per browser per day, a download each time the PDF is requested.

  • Computer Science

Not recorded for this paper

View statement
Looking for related papers…