跳到正文
arXiv cs.CY· Amadeus Brandes·· 23 小时前AI 评分31

决策记录充分性:当未定结论变为生效状态时,记录必须保留什么

Record Sufficiency: What a Decision Record Must Preserve When an Unsettled Claim Becomes an Operative Status

AI 导读

研究提出“决策记录充分性”标准:记录须让仅凭记录及其引用条目的人能解释、界定、重新推导并质疑某一状态。作者据此提出记录应回答的十个问题,映射到其 DRK v0.1 JSON Schema,并定义四项机械检查。

正文 · 原文

View PDF HTML (experimental)

Abstract:Organisations keep evidence, logs and approvals, but often not the step by which an unsettled claim became an operative status, such as an accepted label or a released image, so later readers cannot tell what the status was allowed to mean. We call a decision record sufficient if it is true and a reader who has only the record and the items it cites can explain the status, bound it, re-derive it and challenge it. From these four uses we argue for ten questions a record must answer, map them onto the author's earlier JSON Schema for decision records (DRK v0.1), and define four mechanical checks. We separate conformance, which the checks decide; adequacy, whether the answers are specific enough to use, which needs a reader; fidelity, which no check on the record decides; and merits, which sufficiency does not require. On 164 single-defect variants of three synthetic records, schema validation, the only check DRK v0.1 implements, rejects every variant with a deleted required property and none of the others, and it accepts a record whose claim, rule, scope, limits and challenge route are empty. These are properties of the schema shown on defects we seeded, not estimates of performance on real records. A false record passes every check. The statement-of-reasons schema of the EU Digital Services Act Transparency Database answers 4 of the questions in full, 2 in part and 4 not at all: why the matter was unsettled, what the status depends on, whether it can be re-derived, and how to challenge it. In 25 real statements from 25 platforms, drawn by a seeded rule and coded by a language model and checked by the author, free text addressed any of those four in only 2, and in 18 (24 under a stricter reading adopted during coding) no free text said why the item fell under the rule. No deployment or legal claim is made.
Comments: 24 pages, 2 figures, 7 tables. Ancillary files: schema, records, checks, 25 real statements of reasons with protocol and coding, and a one-command reproduction script
Subjects: Software Engineering (cs.SE); Computers and Society (cs.CY)
Cite as: arXiv:2611.23422 [cs.SE]
  (or arXiv:2611.23422v1 [cs.SE] for this version)
  https://doi.org/10.48550/arXiv.2611.23422

arXiv-issued DOI via DataCite (pending registration)

Submission history

From: Amadeus Brandes [view email]
[v1] Tue, 17 Nov 2026 19:23:52 UTC (254 KB)

来源:arXiv cs.CY · arxiv.org