Answerability
The proactive, individually-held guarantee that a named person can explain why a specific decision was made — distinct from agent-governance's org-level IAM/audit machinery and from post-hoc organizational blame-attribution politics.
Also known as: answer for it, can i explain why, accountability contract, signature (accountability)
How authors use it
Oldest first (extraction date when no publication date is known).
| Author | Their term | Their meaning |
|---|---|---|
| Own the Outer Loop Addy Osmani · 2026-09-09 | Answerability | The guarantee that if someone asks, the accountable person can explain why a decision was made — the property that must survive even when a long-horizon agentic process's intermediate steps are not individually traceable. |
| Own the Outer Loop Addy Osmani · 2026-09-09 | accountability contract | A proposed explicit artifact attached to a codebase or change, recording the checklist understood at acceptance, the evidence behind the decision, who was accountable, and the system's status after the change. |
Documents (2)
- Own the Outer Loop Addy Osmani · 2026-09-09 source ↗ Reader 🖥️
Because agents supply capability but cannot inherit consequence, engineers must own the 'outer loop' of agentic systems — the boundary where Quality (checks/evidence), Verdict (the ship/block decision), and Answerability (the guarantee of being able to explain why) live — which means personal, attributable accountability, not code-writing skill, is what becomes scarce and valuable as harnesses, loops, fleets, and software factories absorb the inner work. - The Pulse #158: New Ways Of Coding With AI Tools Gergely Orosz · 2026-01-09 Reader 🖥️
As AI agents get capable enough that engineers can plausibly have 'the AI did it' as an excuse, human accountability for whether software actually works as expected becomes more valuable, not less — and this accountability gap is also what separates two genuinely new ways of coding gaining traction right now: supervised, interactive human-in-the-loop AI use (where an accountable expert directs and verifies) versus unsupervised autonomous loops like 'Ralph' (which trade away real-time human judgment for throughput, and only now work because the underlying models crossed a capability threshold since November).
Propositions touching this concept (4)
By publication month, oldest first (extraction month when no publication date is known).
2026-09
- explicitAnswerability is the guarantee that if someone asks, the accountable person can explain why a decision was made.
- explicitWith hour-scale, long-horizon agentic delegation, most of the individual decisions made along the way are not recorded and cannot be traced back to specific inputs, making after-the-fact reconstruction of the decision chain practically impossible — so answerability must be designed in proactively rather than assembled after the fact.
- explicitEvery codebase should carry an explicit accountability contract: the checklist understood when the change was accepted, the evidence behind the decision, who was accountable, and the system's status after the change.
- explicitAutomation does not eliminate engineering work; it relocates the bottleneck from 'can we build this' to 'should this exist, can we answer for it,' which itself creates new, real work designing new loops, new evidence, new backpressure mechanisms, and new agents.
Open gaps (3)
- incompleteThe accountability argument and the Tailwind DevOps anecdote sit in the same issue but are never connected: the CFO/payroll hypothetical argues non-experts can't safely rely on AI's confident output, while the Tailwind team (competent generalists, not dedicated DevOps specialists) successfully used Claude Code as an impromptu diagnostic expert. The piece doesn't examine what distinguishes the cases — plausibly, that Tailwind's engineers retained enough general engineering judgment to validate the AI's diagnosis even outside their specialty, which a true non-technical user (the CFO) would lack.The Pulse #158: New Ways Of Coding With AI Tools — read next: Material on what baseline expertise (not necessarily domain-specific) is sufficient to safely supervise AI output outside one's specialty — e.g. the 'expert-generalist' concept.
- incompleteThe essay proposes an 'accountability contract' (checklist understood, evidence, who's accountable, system status) but never specifies how any of these fields get populated from an actual hour-scale agentic run whose intermediate decisions are, by the essay's own admission, not fully recorded and cannot all be traced back to input tokens — leaving the central operational question (how do you produce the evidence you're claiming to own) unanswered.Own the Outer Loop — read next: Read Osmani's own 'Quality in the Harness' and 'Software Factories, Light and Dark' for the concrete evidence artifacts (tests, static analysis, review gates) he specifies elsewhere, and read agent-governance / decision-provenance literature for concrete audit-trail mechanisms.
- incompleteThe practical recommendation to respond with 'genuine accountability' rather than a 'defensive or evasive' posture is offered without any mechanism for what makes an accountability response read as credible to an internal (employee) audience specifically, as opposed to external audiences (regulators, media, customers) — a design problem the corpus already engages with in an AI-agent context but not yet in this general-management context.Research: The True Cost of Corporate Scandals? Talent. — read next: Connect to organizational-accountability design literature on what differentiates a credible apology/accountability signal from a performative one, and whether internal (employee) audiences require different signals than external ones.