跳到正文
研踪PaperTrail
← 研踪 PaperTrail

arXiv:2611.19777 · v1

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

首次提交 2026-11-15 12:13
版本更新 2026-11-15 12:13
雷达观测 2026-11-17 12:06
arXiv ↗PDF ↗

摘要

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.

作者备注:Accepted for the 2026 AIM Pre-ICIS (FRAIS) Paper Development Workshop

AI 论文解读

基于摘要 · 非全文审阅

此版本尚未生成 AI 解读。解读由后台任务生成并按论文版本保存,登录后共享已有结果。

版本差异

目前只收录了一个版本。收录下一版后,可以对照标题、作者、分类和摘要。

观测到的版本

相邻记录可能跳过中间版本;首次发现 v2 及以上也会标为版本更新。

v1 · 2026-11-15 12:13 · 最新观测版本

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

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.

查看此版本解读 →查看此版本原文 ↗