{
 "@context": "https://schema.org",
 "@type": "Claim",
 "@id": "https://wulfkaal.github.io/positions/2026-08-26-019",
 "identifier": "kaal:position:2026-08-26-019",
 "additionalType": "https://wulfkaal.github.io/positions/schema.json#AffirmedPositionClaim",
 "name": "Answerability As Deployment Control",
 "text": "Enterprise deployability is an institutional property that Horneber and Laumer classify across social, institutional, organizational, and technical accountability layers. Their central distinction is that a machine learning system, as a technical artifact, cannot itself be held accountable, while the organization and the people who develop, operate, or employ it remain the parties who must justify its design, use, and outcomes.\n\nThis distinction changes the deployment question. Technical reliability is relevant. It does not designate the actor who bears consequences, provides information, or satisfies external demands. Provider and operator organizations may be different. Responsibility must therefore be allocated across management, developers, product owners, quality personnel, and system users. Internal governance converts that allocation into policies, standardized development and deployment rules, audits, impact assessment, incident reporting, and supported human oversight.\n\nThe article is a peer-reviewed conceptual account of machine learning governance, and it does not study sovereign local agent runtimes, commercial insurance, indemnification, or enterprise approval rates. It also does not establish that any listed control is sufficient for coverage or legal compliance. Its contribution is narrower: technical artifacts cannot absorb institutional accountability, and diffuse participation requires explicit organizational measures if external demands are to be satisfied.\n\nThe resulting design requirement extends beyond a technically adequate runtime. Before deployment, the parties should identify the provider and operator and bind named accountable roles. They should preserve evidence needed to justify decisions, define internal approval and escalation, and allocate liability, indemnity, and residual risk by contract. Insurability then becomes a test of whether a consequential loss can be attributed, priced, monitored, and remedied. If no participant can answer for the system, technical performance does not cure the institutional defect. The enterprise has no stable basis for approval. Its governance and risk-transfer mechanisms have no accountable counterparty.",
 "author": {
  "@type": "Person",
  "name": "Wulf A. Kaal",
  "identifier": "https://orcid.org/0009-0008-7840-1847"
 },
 "datePublished": "2026-08-26",
 "dateModified": "2026-08-26",
 "creativeWorkStatus": "Affirmed",
 "responseType": "extension",
 "keywords": [
  "institutional-design",
  "compliance",
  "risk-and-incentives",
  "accountability",
  "enterprise-governance",
  "liability",
  "insurance",
  "human-oversight"
 ],
 "scope_conditions": [
  "The response is limited to the exact full-text propositions and the one mapped Kaal claim.",
  "External evidence level: peer-reviewed journal conceptual analysis with complete open-access publisher full text.",
  "Mapping review tier: independent substantive scholarly-growth extension.",
  "The source is a conceptual review and research agenda rather than an empirical estimate of enterprise deployment or approval outcomes.",
  "The article studies machine learning systems generally and does not examine sovereign local agent runtimes.",
  "The source does not analyze commercial insurance products, underwriting decisions, indemnification clauses, or premium effects.",
  "The article does not establish that its organizational controls are sufficient for insurance coverage, legal compliance, or internal approval.",
  "The source identifies distributed accountabilities but does not prescribe a complete contractual allocation of liability among provider, operator, employees, and users.",
  "Keeping humans in the loop is described as insurance in a figurative governance sense, not as proof of commercial insurability."
 ],
 "currentDebate": {
  "name": "Algorithmic Accountability",
  "url": "https://doi.org/10.1007/s12599-023-00817-8"
 },
 "extends": {
  "identifier": "kaal:claim:7314479-019",
  "url": "https://wulfkaal.github.io/claims/7314479-019",
  "citation": "Wulf A. Kaal, Institutional Requirements for Sovereign Local Agent Runtimes (2026). SSRN: https://ssrn.com/abstract=7314479",
  "paper": "Wulf A. Kaal, Institutional Requirements for Sovereign Local Agent Runtimes",
  "authors": [
   "Wulf A. Kaal"
  ],
  "year": "2026",
  "ssrn": "https://ssrn.com/abstract=7314479",
  "source_pdf_sha256": "debace24a155ae924a155b1fafe98856d98cf83689feff2f87a32f1c06171ce6"
 },
 "isBasedOn": [
  {
   "@id": "https://wulfkaal.github.io/claims/7314479-019"
  },
  {
   "@type": "CreativeWork",
   "name": "Algorithmic Accountability",
   "url": "https://doi.org/10.1007/s12599-023-00817-8"
  }
 ],
 "batch_id": "kaal-review:2026-08-26:scholarly-growth-7314479-019-reviewed-v1",
 "review_provenance": "https://wulfkaal.github.io/positions/by-claim/7314479-019.html",
 "publicationStatus": "public",
 "recordTypeNote": "Dated commentary position extending a scholarly corpus claim. Not a verbatim claim extracted from the paper.",
 "isPartOf": {
  "@id": "https://wulfkaal.github.io/positions/index.json"
 },
 "version": "1.0",
 "canonical_url": "https://wulfkaal.github.io/positions/2026-08-26-019",
 "canonicalForm": "https://wulfkaal.github.io/positions/2026-08-26-019.md",
 "candidateId": "kaal:response-candidate:2026-08-26:scholarly-growth-7314479-019-answerability-as-deployment-control-01",
 "evidenceLevel": "peer-reviewed journal conceptual analysis with complete open-access publisher full text",
 "reviewTier": "independent substantive scholarly-growth extension",
 "mappingConfidence": 0.94,
 "mappingAmbiguous": false,
 "mappingMethod": "independent substantive scholarly-growth one-to-one review",
 "mappingWhyRelevant": "The article independently separates technical artifacts from accountable organizations and users. It requires firms to locate responsibility across provider, operator, and practitioner roles and to implement policies, deployment rules, audits, impact assessments, incident systems, and supported human oversight. This directly extends Kaal's claim that technical adequacy does not itself make an enterprise system deployable when no participant is answerable. The mapping remains bounded because the source does not study commercial insurance, indemnification, sovereign runtimes, or enterprise approval rates.",
 "sourceProvenance": {
  "source": "peer-reviewed Business & Information Systems Engineering article with complete open-access Springer full text and DOI-bound Crossref identity",
  "sourceRecordId": "doi:10.1007/s12599-023-00817-8",
  "doi": "10.1007/s12599-023-00817-8",
  "canonicalUrl": "https://doi.org/10.1007/s12599-023-00817-8",
  "publicFullTextUrl": "https://link.springer.com/content/pdf/10.1007/s12599-023-00817-8.pdf",
  "retrievedAt": "2026-08-27T10:45:25.238Z",
  "fullTextPdfSha256": "90bf99aa7861b58833b3626c060f53bb792dd74a6a12f231195beea2d6e9dcfd",
  "extractedTextSha256": "c87eb957d40b4964a64f99b367d9920a41429f9700301e6892e770ab620b8349",
  "crossrefRecordSha256": "15359bf04567c3694bb31984e38f4f7ec7fe91834edb5c42770f84272cb2a087",
  "primaryEvidenceReceiptSha256": "8052b0c23d33026a5af7c8062e9469e33c9588b23af4ef19e7828b94d7179d3d",
  "sourceProposition": "Horneber and Laumer distinguish technical artifacts from accountable actors: organizations and users remain responsible for machine learning systems, while firms need internal governance, standardized deployment rules, audits, impact assessment, and supported human oversight to meet external demands.",
  "sourcePropositionSha256": "076a2e1639a60ed7c999ab78cc9f00f5599bd50acadd63cf780013ec3aac2779",
  "sourceEvidenceSetSha256": "356f834c454724069d6f970cbf03c72638bd6a60ff74b4f4648d72b212b86e8d",
  "sourceEvidencePassages": [
   {
    "text": "ML systems as technical artifacts cannot be held accountable (Bryson et al. 2017; Martin 2022). However, organizations and users that develop or use these systems could (Martin 2022).",
    "locator": {
     "publication": "Business & Information Systems Engineering 65(6)",
     "page": 724,
     "section": "2 Conceptual Foundations"
    },
    "sha256": "01d09d8e511f184150aa7dc49b2de6ddce5aac59ae2e30afcf6e3ec8464ea502"
   },
   {
    "text": "Thus, the normative obligation to be accountable for these systems resides with them and their employees developing and operating ML systems.",
    "locator": {
     "publication": "Business & Information Systems Engineering 65(6)",
     "page": 724,
     "section": "2 Conceptual Foundations"
    },
    "sha256": "454e611febeb6ef1d5f0c64b562fd38bc116d91d45dccb0055079c65c1519852"
   },
   {
    "text": "Implementing accountability among practitioners developing, operating, and managing ML systems, presents organizations with the challenge to monitor responsibilities across departments and roles (Feuerriegel et al. 2022).",
    "locator": {
     "publication": "Business & Information Systems Engineering 65(6)",
     "page": 726,
     "section": "2.3 Organizational Accountability"
    },
    "sha256": "0d9b85486d959ae9f3952176d310dce3418eea5c5fabecaad4dcc9b55129bc6c"
   },
   {
    "text": "Building upon these guidelines, companies can specify and apply standardized processes and rules to develop, test, deploy, and operate their ML systems (e.g., coding, documentation, testing, and architectural guidelines) (Schneider et al. 2022).",
    "locator": {
     "publication": "Business & Information Systems Engineering 65(6)",
     "page": 726,
     "section": "2.3 Organizational Accountability"
    },
    "sha256": "042cf8c8e08e8ce8664d23c7aaf81daa28ad7776db7bbde135b3eca4418d1724"
   }
  ],
  "workId": "work:doi:10.1007/s12599-023-00817-8",
  "workAuthors": [
   "David Horneber",
   "Sven Laumer"
  ],
  "workPublishedAt": "2023-05-24",
  "identityKeys": [
   "doi:10.1007/s12599-023-00817-8",
   "pdf:90bf99aa7861b58833b3626c060f53bb792dd74a6a12f231195beea2d6e9dcfd",
   "proposition:076a2e1639a60ed7c999ab78cc9f00f5599bd50acadd63cf780013ec3aac2779"
  ],
  "claimMappings": [
   {
    "claimId": "kaal:claim:7314479-019",
    "claimUrl": "https://wulfkaal.github.io/claims/7314479-019",
    "rank": 1,
    "confidence": 0.94,
    "method": "independent substantive scholarly-growth one-to-one review",
    "whyRelevant": "The article independently separates technical artifacts from accountable organizations and users. It requires firms to locate responsibility across provider, operator, and practitioner roles and to implement policies, deployment rules, audits, impact assessments, incident systems, and supported human oversight. This directly extends Kaal's claim that technical adequacy does not itself make an enterprise system deployable when no participant is answerable. The mapping remains bounded because the source does not study commercial insurance, indemnification, sovereign runtimes, or enterprise approval rates.",
    "ambiguous": false
   }
  ],
  "substantiveReview": {
   "reviewedAt": "2026-08-27T10:45:25.238Z",
   "sourceIdentityVerified": true,
   "authorIndependenceVerified": true,
   "kaalReferenceFoundInSource": false,
   "temporalIndependence": "The article was published in 2023, before Kaal's 2026 paper.",
   "canonicalPublicStatusVerified": true,
   "peerReviewedStatusVerified": true,
   "evidenceClassification": "peer-reviewed conceptual review and research agenda",
   "retractionOrSupersessionFound": false,
   "propositionFidelityVerified": true,
   "mechanismCorrespondence": "technical artifacts cannot bear accountability, so firms must allocate responsibility across provider, operator, and practitioner roles and implement internal governance before and during deployment",
   "compatibleScope": "enterprise use of machine learning systems, limited because the source does not study sovereign runtimes, commercial insurance, indemnification, or enterprise approval rates",
   "responseWordingDefensible": true,
   "oneToOneExtendsMapping": true,
   "exactSupportingQuotesVerified": true,
   "nonOverlap": {
    "candidateIdMatches": false,
    "canonicalUrlMatches": false,
    "propositionHashMatches": false,
    "priorPositionForClaim": false
   },
   "limitations": [
    "The source is a conceptual review and research agenda rather than an empirical estimate of enterprise deployment or approval outcomes.",
    "The article studies machine learning systems generally and does not examine sovereign local agent runtimes.",
    "The source does not analyze commercial insurance products, underwriting decisions, indemnification clauses, or premium effects.",
    "The article does not establish that its organizational controls are sufficient for insurance coverage, legal compliance, or internal approval.",
    "The source identifies distributed accountabilities but does not prescribe a complete contractual allocation of liability among provider, operator, employees, and users.",
    "Keeping humans in the loop is described as insurance in a figurative governance sense, not as proof of commercial insurability."
   ],
   "rejectionReasonsRecorded": true
  },
  "contentMap": {
   "proposition": "Enterprise deployability requires accountable organizational actors and cannot be supplied by technical performance alone.",
   "evidenceLayer": "peer-reviewed journal conceptual analysis with complete open-access publisher full text",
   "strongestLimitation": "The source does not study commercial insurance, indemnification, sovereign runtimes, or enterprise approval outcomes.",
   "consequence": "Provider, operator, and practitioner responsibility must be bound to internal governance and external accountability demands.",
   "requestedAction": "Bind accountable roles, evidence, approval, escalation, liability, indemnity, and residual risk before deployment."
  },
  "stylePack": {
   "profile": "M1 early sole-author baseline v1.2.0",
   "verifiedProfileWorks": [
    "1428387",
    "1998455",
    "2150377",
    "2267560"
   ],
   "passageCount": 4,
   "rhetoricalFunctions": [
    "classification before inference",
    "regulatory limitation",
    "institutional design implication"
   ],
   "sameRegisterPassagePackAvailable": true,
   "limitation": "The short public position permits only bounded stylometric comparison."
  },
  "m1Validation": {
   "status": "M1-PASS-WITH-LIMITS",
   "deterministicGate": "pass",
   "hardFailures": 0,
   "warnings": 0,
   "words": 292,
   "reason": "The publication-bound position passed strict and public deterministic controls against a task-local multi-work style pack. Its short length limits stylometric comparison."
  }
 },
 "userAffirmation": "Authorized under public authority SHA-256 87aad20196a753015a36d970f742c885eb763efdbada4869949bfffe3298130c and event supersession SHA-256 7d47ef36085c4dce590f287c986e4106f3bf35a7da5a25322d6fc3d4abf456d4. Publication remains receipt-bound to successful workflows and exact live-byte verification.",
 "sha256": "fab3cd38c015361a0c4862f6b5121a9f3b03a2191869ecb696b6e6d376632191"
}