> For the complete documentation index, see [llms.txt](https://www.aicontrolarchitecture.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.aicontrolarchitecture.org/the-ten-pillars/13-pillar-human-accountability.md).

# 13 · Human Accountability

**Control question:** *Who is accountable?* **Surface:** spans all three, See, Decide, Do.

***

## Purpose

This pillar ensures that a **named human owns every consequential outcome** of an AI use case. AI can inform, draft, recommend, and act, but it cannot be accountable. It cannot accept risk, answer to a regulator, or be held responsible when something goes wrong. This pillar assigns and records the humans who can: the owner of the use case, the approver of consequential decisions, the acceptor of risk, and the owner of recovery.

***

## Why it matters

Accountability is the control that cannot be automated, and the one most easily lost. As AI produces more of the work, the human role thins to a signature, and then to nothing, as the output flows straight through. When a failure happens, the organization discovers there is no one who owned the decision, no one who accepted the risk, no one responsible for recovery. "The AI did it" is not an answer a board, a regulator, or a court accepts. This pillar exists to make sure that answer never has to be given, that for anything consequential, a person chose, and can say why.

***

## Control objectives

* Assign a **named accountable human** to each consequential outcome, decision, approval, and exception.
* **Record** risk acceptance for a use case, attributably.
* Assign **recovery ownership** before a use case goes live at elevated tier.

***

## Requirements

From the [Requirements Catalogue](/foundation/06-requirements-catalogue.md):

| ID        | Requirement                                                                       | From | Boundary  |
| --------- | --------------------------------------------------------------------------------- | ---- | --------- |
| ACA-13-01 | A named human owns each consequential outcome, decision, approval, and exception. | T1   | Declared  |
| ACA-13-02 | Risk acceptance for a use case is recorded and attributable.                      | T2   | Evidenced |
| ACA-13-03 | Recovery ownership is assigned before go-live at tier ≥ T2.                       | T2   | Declared  |

***

## Key controls

* **Use-case ownership**: every AI use case has a single accountable owner from intake ([pillar 07](/the-ten-pillars/07-pillar-ai-inventory-and-classification.md)), through changes, to retirement.
* **Decision accountability**: the human who confirms or corrects a consequential AI-influenced decision is the accountable party for it ([pillar 11](/the-ten-pillars/11-pillar-output-and-decision-control.md)); that act is recorded.
* **Risk acceptance**: where a use case runs with a known, accepted residual risk (or an exception to a control), a named human of appropriate authority records that acceptance.
* **Exception ownership**: deviations from required controls are owned, time-bound, and reviewed, not permanent silent gaps.
* **Recovery ownership**: before an elevated-tier use case goes live, someone owns "if this fails, I make it right" ([pillar 16](/the-ten-pillars/16-pillar-containment-and-recovery.md)).
* **Judgement, not delegation**: the architecture's stance ([Core Thesis](/foundation/03-core-thesis.md)): you can use AI to inform a judgement, but you cannot outsource the judgement itself.

***

## Tier guidance

|                                  | T1            | T2       | T3                        |
| -------------------------------- | ------------- | -------- | ------------------------- |
| Named use-case owner             | Required      | Required | Required                  |
| Decision accountability recorded | As applicable | Required | Required                  |
| Risk acceptance recorded         | Recommended   | Required | Required                  |
| Recovery owner assigned          | -             | Required | Required (before go-live) |

***

## Evidence

The [AI Human Accountability template](https://github.com/ai-ankqush/ai-control-architecture/tree/main/templates/ai-human-accountability-template.md) and [AI Exception Record template](https://github.com/ai-ankqush/ai-control-architecture/tree/main/templates/ai-exception-record-template.md) capture the owners, the risk acceptances, and the exceptions. Boundary source is *Declared* when owners are named, and *Evidenced* when risk acceptances and exceptions are recorded with authority and date.

***

## Standards crosswalk

Maps to NIST AI RMF **Govern**, ISO/IEC 42001 (roles, responsibilities, and human oversight), EU AI Act (human oversight and provider/deployer obligations), and SR 11-7 (model risk ownership and governance). See [`mappings/`](/standards-crosswalks/mappings-readme.md).

***

## Failure modes

* A consequential decision with no accountable human, "the AI decided."
* Residual risk running with no one who accepted it.
* A control exception that quietly became permanent, owned by no one.
* A live high-impact use case with no assigned recovery owner.

***

**Next:** [14 · Assurance & Testing](/the-ten-pillars/14-pillar-assurance-and-testing.md)

*Version 0.1.0 · Licensed under the terms in* [*LICENSE.md*](https://github.com/ai-ankqush/ai-control-architecture/tree/main/LICENSE.md)*.*


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://www.aicontrolarchitecture.org/the-ten-pillars/13-pillar-human-accountability.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.