# kaal:position:2026-08-26-013

**Affirmed position.** Accountability is not a single property of an agent runtime. Chappidi and her coauthors define an accountability relationship through an actor who owes an account, a forum entitled to receive it, and information that permits review and response. They then distinguish records from a system, which describe its operation, from records about a system, which describe how it was commissioned, built, deployed, and monitored. Records may support investigation, oversight, challenge, repair, and redress. The paper also identifies accountability capture. The apparatus used to observe conduct can reconfigure the conduct, induce evasion, and distort the accountability regime itself.

This structure independently supports separate diagnosis. Attribution fails when operational records cannot reconstruct what occurred. Authority drifts when the actor, forum, governing requirement, or design decision is not preserved across commissioning and use. Evaluation becomes captured when the measurement apparatus changes behavior or serves interests that defeat the accountability purpose. Recourse disappears when records do not reach a forum capable of challenge, response, and remedy.

The correspondence is functional, not terminological. The paper does not use Kaal's four labels, prove that the taxonomy is exhaustive, or study sovereign local agent runtimes. Its survey concerns organizational record keeping around algorithmic systems. It nonetheless shows why a general appeal to trust is inadequate. Each failure has different evidence and a different institutional repair. A runtime assessment should therefore test traceability, delegated authority, evaluator independence, and enforceable recourse separately.

**Status.** affirmed  **Published.** 2026-08-26

**Holds when.**

- The response is limited to the exact full-text propositions and the one mapped Kaal claim.
- External evidence level: peer-reviewed AIES conference paper with complete official proceedings full text.
- Mapping review tier: independent substantive scholarly-growth extension.
- The source studies organizational record keeping around algorithmic systems rather than sovereign local agent runtimes.
- The paper does not use Kaal's four labels or establish that the four-part taxonomy is exhaustive.
- Accountability capture is a broader socio-technical reconfiguration concept and is not identical to Kaal's evaluative capture condition.
- The practitioner survey has 100 respondents and characterizes record-keeping effects rather than testing production runtime failures.
- The source identifies actor-forum relationships and lifecycle records but does not measure delegated-authority drift during runtime execution.

**Current debate.** Accountability Capture: How Record-Keeping to Support AI Transparency and Accountability (Re)shapes Algorithmic Oversight: https://ojs.aaai.org/index.php/AIES/article/view/36570

**Extends.** kaal:claim:7314479-013: https://wulfkaal.github.io/claims/7314479-013

**Scholarly basis.** Wulf A. Kaal, Institutional Requirements for Sovereign Local Agent Runtimes (2026). SSRN: https://ssrn.com/abstract=7314479

**Source PDF sha256.** `debace24a155ae924a155b1fafe98856d98cf83689feff2f87a32f1c06171ce6`

**Evidence level.** peer-reviewed AIES conference paper with complete official proceedings full text

**Mapping review tier.** independent substantive scholarly-growth extension

**Mapping confidence.** 0.96  **Mapping ambiguous.** false

**Topics.** governance-design, institutional-design, risk-and-incentives, ai-and-agents, accountability, traceability, authority, evaluation, recourse

**Provenance.** Affirmed in kaal-review:2026-08-26:scholarly-growth-7314479-013-reviewed-v1 at https://wulfkaal.github.io/positions/by-claim/7314479-013.html.

**Record type.** This is a dated commentary position that extends a scholarly corpus claim. It is not a verbatim claim extracted from the paper.

**Canonical form.** This markdown file is the canonical hashed representation of the position.