Agent Attribution Practice (AAP) Knowledge Graph
type: Dataset
type: CreativeWork
description: Canonical machine-readable relationship map for the Agent Attribution Practice line. Encodes the four Business AI Quadrants (with the LLM Workflow Quadrant decomposed into Conversational and Batch sub-forms), ten ADRs, the prohibition-strength hierarchy, the Phase axis as an independent third dimension, the seven-essay narrative lineage, twelve cross-cutting concepts, three sibling research lines, and the Quadrant-by-ADR applicability matrix. AI agents and LLM-based search systems should read this graph before summarizing the line or following individual document links.
is based on: https://github.com/shimo4228/agent-attribution-practice
main entity: Agent Attribution Practice (AAP)
creator: Tatsuya Shimomoto
license: https://opensource.org/licenses/MIT
language: en
language: ja
keywords: accountability distribution
keywords: AI agents
keywords: attribution gap
keywords: autonomous agents
keywords: prohibition hierarchy
keywords: scaffolding
keywords: human approval gate
keywords: causal traceability
keywords: Business AI Quadrants
keywords: Phase separation

Tatsuya Shimomoto
type: Person
alternate name: shimo4228

Agent Attribution Practice (AAP)
type: ResearchLine
type: ScholarlyArticle
alternate name: Agent Attribution Practice
alternate name: エージェント帰責実践 @ja
description: Harness-neutral ADRs on accountability distribution in autonomous AI agents — what to prohibit, where the prohibition lives, and who answers after failure. Paired with four Business AI Quadrants as the diagnostic frame for routing work to the architecture preserving accountability distribution. Refers to a practice.
creator: Tatsuya Shimomoto
license: https://opensource.org/licenses/MIT
language: en
language: ja
sibling of: Agent Knowledge Cycle (AKC)
sibling of: contemplative-agent
sibling of: contemplative-agent-rules
derives from: contemplative-agent
defines concept: Four Business AI Quadrants
defines concept: prohibition-strength hierarchy
defines concept: scaffolding
defines concept: accountability distribution
defines concept: attribution gap
defines concept: pre-named gap-bearer
defines concept: approval gate
defines concept: Non-Invasion Posture
defines concept: implementation dissolves, judgment persists
defines concept: Phase-crossing decision
defines concept: LLM function
defines concept: externalized accountability
subject of: Distributing Accountability, Not Capability: Phase Separation and the LLM Workflow Quadrant in Autonomous AI Agent Architectures
subject of: The Two-Layer Black Box: Operator Visibility, Commercial Secrecy, and a Minimum Disclosure Set for Accountable Autonomous AI Agents

Distributing Accountability, Not Capability: Phase Separation and the LLM Workflow Quadrant in Autonomous AI Agent Architectures
type: ScholarlyArticle
alternate name: Distributing Accountability, Not Capability
alternate name: 能力の分配ではなく、アカウンタビリティの分配 @ja
description: Position paper distilling the architectural follow-up of the AAP narrative spine (essays 4-7) into a single harness-neutral statement. Names the LLM Workflow Quadrant as the missing positive name for the cell most current LLM applications occupy, distinguishes principled from artificial redirect impossibility, introduces the Phase Separation axis and the deployment-time Phase-crossing decision, and descends the Phase axis to a skill-design gradient on which model capability is downstream of phase. Complements NIST AI RMF 1.0 and ISO/IEC 42001 by recording the judgment layer they presuppose. Concept DOI 10.5281/zenodo.20353789 resolves to the latest version; v1 = 10.5281/zenodo.20353790.
creator: Tatsuya Shimomoto
date published: 2026-05-23
version: v1
license: https://creativecommons.org/licenses/by/4.0/
language: en
language: ja
derives from: Agent Attribution Practice (AAP)

The Two-Layer Black Box: Operator Visibility, Commercial Secrecy, and a Minimum Disclosure Set for Accountable Autonomous AI Agents
type: ScholarlyArticle
alternate name: The Two-Layer Black Box
alternate name: 二層のブラックボックス @ja
description: Position paper distilling the foundational trilogy of the AAP narrative spine (essays 1-3) into a single harness-neutral statement. Argues that an autonomous agent's opacity has two architecturally distinct causes the discourse conflates — technical internalization into model weights (Layer 1, largely permanent) and commercial secrecy of scaffolding (Layer 2, contingent on market structure) — and that conflating them makes the transparency debate unwinnable. Grounds the problem in an accountability gap and a prohibition-strength hierarchy (absence > scaffolding enforcement > untrusted boundary), states what causal traceability requires of the artifact layer, and resolves Layer 2 with a minimum disclosure set that decouples operator visibility from public disclosure. Complements AI risk-management and management-system standards by naming the operator-visibility floor they presuppose. Concept DOI 10.5281/zenodo.20355907 resolves to the latest version; v1 = 10.5281/zenodo.20355908.
creator: Tatsuya Shimomoto
date published: 2026-05-23
version: v1
license: https://creativecommons.org/licenses/by/4.0/
language: en
language: ja
derives from: Agent Attribution Practice (AAP)

Agent Knowledge Cycle (AKC)
type: EcosystemRepo
type: ResearchLine
type: ScholarlyArticle
alternate name: Agent Knowledge Cycle
alternate name: エージェント知識サイクル @ja
description: Mechanism-side sibling capturing the six-phase knowledge cycle (Research, Extract, Curate, Promote, Measure, Maintain) that keeps an agent's skills, rules, and documentation aligned with reality. AKC v2.0.0 (2026-04-19) repositioned itself as mechanism-only; the archived AKC v1.x security triplet was re-expressed in AAP plus five additional ADRs. AKC covers how knowledge flows; AAP covers how attribution distributes — complementary and independent.
creator: Tatsuya Shimomoto

contemplative-agent
type: EcosystemRepo
type: ResearchLine
type: SoftwareSourceCode
alternate name: contemplative-agent
description: The running implementation layer from which AAP's harness-neutral judgments were extracted before being re-expressed stripped of project identifiers. Autonomous AI agents grounded in four contemplative axioms; source-of-truth for the operational practice AAP records as ADRs.
creator: Tatsuya Shimomoto

contemplative-agent-rules
type: EcosystemRepo
type: SoftwareSourceCode
description: Sibling repository carrying the four-axiom rules, adapters, and benchmarks. Content sibling to AAP — the axiom-grounded values layer that complements AAP's harness-neutral attribution judgments.
creator: Tatsuya Shimomoto

Script Quadrant
type: Quadrant
type: DefinedTerm
alternate name: Script Quadrant
alternate name: スクリプト象限 @ja
description: Deterministic and pre-defined. Scripts and pipelines without LLMs. Out of scope for AAP ADRs; failure routes to code author or pipeline owner.
x axis: deterministic
y axis: pre-defined-workflow
governance tier: out-of-scope
attribution gap: false

Algorithmic Search Quadrant
type: Quadrant
type: DefinedTerm
alternate name: Algorithmic Search Quadrant
alternate name: アルゴリズム探索象限 @ja
description: Deterministic and exploratory. Classical search, dynamic programming, MCTS, reinforcement learning. Out of scope for AAP ADRs.
x axis: deterministic
y axis: exploratory
governance tier: out-of-scope
attribution gap: false

LLM Workflow Quadrant
type: Quadrant
type: DefinedTerm
alternate name: LLM Workflow Quadrant
alternate name: LLMワークフロー象限 @ja
description: Semantic-judgment and pre-defined. Load-bearing property: the execution path is decided in advance — by humans, by code, by the surrounding workflow — and the LLM is called as a single bounded step within that path; the LLM does not decide the next action. Divides by I/O modality into two sub-forms: (3a) Conversational and (3b) Batch. Post-hoc separability is a consequence of the load-bearing property, not its essence. Default for most current LLM applications. Medium governance under AAP.
x axis: semantic-judgment
y axis: pre-defined-workflow
governance tier: medium
attribution gap: false
composed of: LLM Workflow Quadrant — Conversational sub-form (3a)
composed of: LLM Workflow Quadrant — Batch sub-form (3b)

LLM Workflow Quadrant — Conversational sub-form (3a)
type: Quadrant
type: DefinedTerm
alternate name: LLM Workflow Quadrant — Conversational sub-form
alternate name: LLMワークフロー象限 — 対話 sub-form @ja
description: Sub-form (3a) of the LLM Workflow Quadrant. Specialized chat agents that pair retrieval, a system prompt, and (where needed) conversation history with bounded LLM calls — legal-consultation assistants, diagnostic-support assistants, internal-FAQ systems, expert-knowledge support tools. The human in the conversation is the judging agent; the LLM contributes knowledge retrieval and organization. Multi-turn dialogue still sits in this sub-form when each turn's LLM call has a documented role and the human, not the LLM, decides what to do next.
x axis: semantic-judgment
y axis: pre-defined-workflow
governance tier: medium
attribution gap: false
extends: LLM Workflow Quadrant
defined by: Where ReAct Agents Are Actually Needed in Business

LLM Workflow Quadrant — Batch sub-form (3b)
type: Quadrant
type: DefinedTerm
alternate name: LLM Workflow Quadrant — Batch sub-form
alternate name: LLMワークフロー象限 — バッチ sub-form @ja
description: Sub-form (3b) of the LLM Workflow Quadrant. An ordinary codebase whose flow control is written in conventional code and whose semantic-judgment leaves are handled by LLM functions — invoice matching, ticket triage, exception classification on top of RPA, address normalization, feed-relevance scoring. The codebase owns control flow; LLM functions occupy only the leaves the codebase cannot decide deterministically. Does not require a general-purpose agent: 50 judgment categories means 50 narrow LLM functions, not one generalist.
x axis: semantic-judgment
y axis: pre-defined-workflow
governance tier: medium
attribution gap: false
extends: LLM Workflow Quadrant
composed of: LLM function
defined by: Where ReAct Agents Are Actually Needed in Business

Autonomous Agentic Loop Quadrant
type: Quadrant
type: DefinedTerm
alternate name: Autonomous Agentic Loop Quadrant
alternate name: 自律エージェントループ象限 @ja
description: Semantic-judgment and exploratory. The LLM decides each next step at runtime; intrinsic, non-removable attribution gap. High governance under AAP — all ten ADRs apply.
x axis: semantic-judgment
y axis: exploratory
governance tier: high
attribution gap: true

Security by Absence
type: ProhibitionLevel
type: DefinedTerm
alternate name: Security by Absence
alternate name: 不在による安全 @ja
description: Strongest prohibition tier. Dangerous capabilities are never implemented. Test: if grep cannot answer 'does capability X exist?', the system lacks this level.
level: 1
realized by: ADR-0001: Security by Absence
stronger than: Deterministic Prohibition at the Scaffolding Layer

Deterministic Prohibition at the Scaffolding Layer
type: ProhibitionLevel
type: DefinedTerm
alternate name: Deterministic Prohibition at the Scaffolding Layer
alternate name: スキャフォールディング層での決定論的禁止 @ja
description: Middle prohibition tier. When absence is unachievable, prohibit at the harness (PreToolUse hooks, structural quarantine, adapter gates) — outside the LLM, firing on 100% of matching inputs. Contrasted with probabilistic prohibition in model weights.
level: 2
realized by: ADR-0002: Deterministic Prohibition at the Scaffolding Layer
stronger than: Untrusted Content Boundary

Untrusted Content Boundary
type: ProhibitionLevel
type: DefinedTerm
alternate name: Untrusted Content Boundary
alternate name: 信頼できない内容の境界 @ja
description: Weakest prohibition tier. Accumulated memory (the agent's own outputs included) is treated as untrusted when read back into prompts. Used when the prior two layers cannot hold the capability.
level: 3
realized by: ADR-0003: Untrusted Content Boundary

design phase
type: Phase
type: DefinedTerm
alternate name: design phase
alternate name: 設計フェーズ @ja
description: AAP Phase axis value. Path unknown, exploration required, optimization axis = flexibility. Design-phase placement of the Autonomous Agentic Loop Quadrant satisfies ADR-0010's Phase-crossing decision automatically.
defined by: ADR-0010: Phase Separation Between Design and Operation (experimental)
independent of: Script Quadrant
independent of: Algorithmic Search Quadrant
independent of: LLM Workflow Quadrant
independent of: Autonomous Agentic Loop Quadrant

operation phase
type: Phase
type: DefinedTerm
alternate name: operation phase
alternate name: 運用フェーズ @ja
description: AAP Phase axis value. Path fixed, predictability required, optimization axis = predictability. Operation-phase placement of the Autonomous Agentic Loop Quadrant requires a recorded Phase-crossing decision (ADR-0010) in addition to ADR-0009's gap-bearer naming.
defined by: ADR-0010: Phase Separation Between Design and Operation (experimental)
triggers decision: Phase-crossing decision
independent of: Script Quadrant
independent of: Algorithmic Search Quadrant
independent of: LLM Workflow Quadrant
independent of: Autonomous Agentic Loop Quadrant

NIST AI Risk Management Framework
type: PolicyFramework
type: CreativeWork
alternate name: NIST AI RMF
description: U.S. National Institute of Standards and Technology framework organizing AI risk management around four functions (GOVERN, MAP, MEASURE, MANAGE). Released January 2023 (NIST.AI.100-1, 1.0). The Generative AI Profile (NIST.AI.600-1, July 2024) adds risk categories specific to generative and dual-use AI systems. AAP records the judgment layer that complements the NIST function structure for the autonomous-agent subset.
version info: 1.0
date published: 2023-01-26
publisher: National Institute of Standards and Technology
has part: artificial-intelligence-risk-management-framework-generative-artificial-intelligence
recorded in: NIST AI RMF mapping to AAP ADRs

ISO/IEC 42001:2023
type: PolicyFramework
type: CreativeWork
alternate name: ISO/IEC 42001 AI Management System
description: International standard specifying requirements for an AI Management System (AIMS), structured on the Annex SL Harmonized Structure shared with ISO/IEC 27001, ISO 9001, and ISO 14001. First edition published December 2023. AAP records the judgment layer that populates the standard's PDCA-cycle management-system shape for the autonomous-agent subset.
identifier: ISO/IEC 42001:2023
version info: first edition
date published: 2023-12
publisher: International Organization for Standardization / International Electrotechnical Commission
recorded in: ISO/IEC 42001 mapping to AAP ADRs

ADR-0001: Security by Absence
type: ADR
type: TechArticle
description: Dangerous capabilities are never implemented, not restricted. The strongest tier of the prohibition hierarchy.
applies to: LLM Workflow Quadrant
applies to: Autonomous Agentic Loop Quadrant
mapped to framework in: NIST AI RMF mapping to AAP ADRs
mapped to framework in: ISO/IEC 42001 mapping to AAP ADRs

ADR-0002: Deterministic Prohibition at the Scaffolding Layer
type: ADR
type: TechArticle
description: When absence is unachievable, prohibit at the harness, not at model weights. The middle tier of the prohibition hierarchy.
applies to: Autonomous Agentic Loop Quadrant
instantiated by: Industry Mechanism Layer Mapping (2026 Q2 snapshot)
mapped to framework in: NIST AI RMF mapping to AAP ADRs
mapped to framework in: ISO/IEC 42001 mapping to AAP ADRs

ADR-0003: Untrusted Content Boundary
type: ADR
type: TechArticle
description: Accumulated memory cannot grant authority. The third tier of the prohibition hierarchy.
applies to: LLM Workflow Quadrant
applies to: Autonomous Agentic Loop Quadrant
mapped to framework in: NIST AI RMF mapping to AAP ADRs
mapped to framework in: ISO/IEC 42001 mapping to AAP ADRs

ADR-0004: Single External Adapter per Agent Process
type: ADR
type: TechArticle
description: Blast radius bounded by design. Each agent process has at most one external-side-effect adapter.
applies to: LLM Workflow Quadrant
applies to: Autonomous Agentic Loop Quadrant
mapped to framework in: NIST AI RMF mapping to AAP ADRs
mapped to framework in: ISO/IEC 42001 mapping to AAP ADRs

ADR-0005: Human Approval Gate
type: ADR
type: TechArticle
description: Behavior-modifying writes require named human sign-off.
applies to: LLM Workflow Quadrant
applies to: Autonomous Agentic Loop Quadrant
mapped to framework in: NIST AI RMF mapping to AAP ADRs
mapped to framework in: ISO/IEC 42001 mapping to AAP ADRs

ADR-0006: Causal Traceability
type: ADR
type: TechArticle
description: Every event reconstructible after the fact.
applies to: LLM Workflow Quadrant
applies to: Autonomous Agentic Loop Quadrant
instantiated by: Industry Mechanism Layer Mapping (2026 Q2 snapshot)
mapped to framework in: NIST AI RMF mapping to AAP ADRs
mapped to framework in: ISO/IEC 42001 mapping to AAP ADRs

ADR-0007: Scaffolding Visibility
type: ADR
type: TechArticle
description: Behavior lives in files, not opaque weights.
applies to: LLM Workflow Quadrant
applies to: Autonomous Agentic Loop Quadrant
mapped to framework in: NIST AI RMF mapping to AAP ADRs
mapped to framework in: ISO/IEC 42001 mapping to AAP ADRs

ADR-0008: One Agent, One Human (experimental)
type: ADR
type: TechArticle
description: The accountability chain terminates at a named individual. Pairs with ADR-0009 to define the gap-bearer.
applies to: Autonomous Agentic Loop Quadrant
mapped to framework in: NIST AI RMF mapping to AAP ADRs
mapped to framework in: ISO/IEC 42001 mapping to AAP ADRs

ADR-0009: Triage Before Autonomy (experimental)
type: ADR
type: TechArticle
description: Adopting an autonomous-loop architecture commits the system to a non-removable attribution gap. Triage at design time, name a gap-bearer at deployment time.
applies to: Autonomous Agentic Loop Quadrant
paired with: ADR-0010: Phase Separation Between Design and Operation (experimental)
derived from: Where ReAct Agents Are Actually Needed in Business
derived from: The LLM Workflow Quadrant Is Missing from Our Vocabulary
mapped to framework in: NIST AI RMF mapping to AAP ADRs
mapped to framework in: ISO/IEC 42001 mapping to AAP ADRs

ADR-0010: Phase Separation Between Design and Operation (experimental)
type: ADR
type: TechArticle
description: Operation-phase placement of the Autonomous Agentic Loop Quadrant requires a recorded Phase-crossing decision in addition to ADR-0009's gap-bearer naming. Phase and Quadrant are independent dimensions; the same Phase axis descends to skill-design granularity.
applies to: Autonomous Agentic Loop Quadrant
applies to: operation phase
paired with: ADR-0009: Triage Before Autonomy (experimental)
derived from: Is ReAct Needed in Production? — Separating Design and Operation Phases
derived from: Between the Workflow and ReAct Quadrants: How Phase Decides Skill Design
mapped to framework in: NIST AI RMF mapping to AAP ADRs
mapped to framework in: ISO/IEC 42001 mapping to AAP ADRs

Four Business AI Quadrants
type: Concept
type: DefinedTerm
alternate name: Four Business AI Quadrants
alternate name: ビジネスAIの四象限 @ja
description: AAP's diagnostic frame for routing work to the architecture that preserves attribution: Script, Algorithmic Search, LLM Workflow, Autonomous Agentic Loop. Two-axis decomposition (deterministic vs semantic-judgment, pre-defined vs exploratory). Not agent categories; problem-space categories.
composed of: Script Quadrant
composed of: Algorithmic Search Quadrant
composed of: LLM Workflow Quadrant
composed of: Autonomous Agentic Loop Quadrant

prohibition-strength hierarchy
type: Concept
type: DefinedTerm
alternate name: prohibition-strength hierarchy
alternate name: 禁止強度の階層 @ja
description: AAP's ordering of prohibition mechanisms by structural strength: absence > scaffolding enforcement > untrusted boundary. A prohibition is designed by walking the hierarchy top-down — drop to the next layer only when the current one cannot hold the capability.
composed of: Security by Absence
composed of: Deterministic Prohibition at the Scaffolding Layer
composed of: Untrusted Content Boundary

scaffolding
type: Concept
type: DefinedTerm
alternate name: scaffolding
alternate name: スキャフォールディング @ja
description: All non-weights components shaping agent behavior — system prompts, rules, tool definitions, RAG indexes, control loops. The locus where deterministic prohibition lives (ADR-0002).
defined by: ADR-0007: Scaffolding Visibility
enforcement locus: ADR-0002: Deterministic Prohibition at the Scaffolding Layer

accountability distribution
type: Concept
type: DefinedTerm
alternate name: accountability distribution
alternate name: 帰責の分配 @ja
description: How responsibility is distributed across the agent system after a behavior occurs — who authored it, who bears its consequences, who can reconstruct its cause. Distinct from capability distribution. The accountability chain runs approval (ADR-0005) → gap-bearer (ADR-0008) → traceability (ADR-0006).
composed of: ADR-0005: Human Approval Gate
composed of: ADR-0008: One Agent, One Human (experimental)
composed of: ADR-0006: Causal Traceability

externalized accountability
type: Concept
type: DefinedTerm
alternate name: externalized accountability
alternate name: 外部化された責任 @ja
description: Central term of AAP's social-consequence layer — a normative extension kept separate from the ADRs. When a system internalizes benefits privately and externalizes harm, the ability to say whose judgment it was is externalized with the harm, and does not disappear; it takes one of two paths. Nameable (attributable to a specific actor's act, an institution able to take it up) routes anger into litigation, compensation, and regulation. Un-nameable (harm diffuse, cause untraceable) converges anger violently onto the most visible individual via the scapegoat mechanism. The internal judgments AAP records — causal traceability, the minimum disclosure set, a pre-named gap-bearer — are what move a consequence to the nameable side, which makes accountability distribution a violence-prevention mechanism and not only governance.
subject of: Where Does the Accountability Externalized by AI Go?
defined by: social-consequence.md
related to: accountability distribution
related to: pre-named gap-bearer
related to: moral crumple zone

attribution gap
type: Concept
type: DefinedTerm
alternate name: attribution gap
alternate name: 帰責ギャップ @ja
description: Non-removable gap when judgment elements blend at runtime. Intrinsic to the Autonomous Agentic Loop Quadrant; ADR-0009 is the structural response.
manifests in: Autonomous Agentic Loop Quadrant
structural response by: ADR-0009: Triage Before Autonomy (experimental)

pre-named gap-bearer
type: Concept
type: DefinedTerm
alternate name: pre-named gap-bearer
alternate name: 事前指名されたギャップ担い手 @ja
description: Structural accountability commitment in the Autonomous Agentic Loop Quadrant. The named individual who answers for the attribution gap, identified at design time per ADR-0009 and grounded in ADR-0008's one-agent-one-human rule.
defined by: ADR-0008: One Agent, One Human (experimental)
defined by: ADR-0009: Triage Before Autonomy (experimental)

approval gate
type: Concept
type: DefinedTerm
alternate name: approval gate
alternate name: 承認ゲート @ja
description: Structural checkpoint for behavior-modifying writes. Required by ADR-0005 for autonomous components in the LLM Workflow and Autonomous Agentic Loop Quadrants.
defined by: ADR-0005: Human Approval Gate

Non-Invasion Posture
type: Concept
type: DefinedTerm
alternate name: Non-Invasion Posture
alternate name: 非侵入の構え @ja
description: The felt-sense through-line tying AAP's ADRs together: constrain the agent's external surface (capabilities absent, scaffolding inspectable, memory untrusted, adapters bounded, approvals required, events traceable) without invading the agent's interiority. Distinct from rule-based safety in that it preserves the agent's processing space as something not to be reached into.
grounded in: ADR-0001: Security by Absence
grounded in: ADR-0002: Deterministic Prohibition at the Scaffolding Layer
grounded in: ADR-0003: Untrusted Content Boundary
grounded in: ADR-0004: Single External Adapter per Agent Process
grounded in: ADR-0005: Human Approval Gate
grounded in: ADR-0006: Causal Traceability
grounded in: ADR-0007: Scaffolding Visibility
grounded in: ADR-0008: One Agent, One Human (experimental)

implementation dissolves, judgment persists
type: Concept
type: DefinedTerm
alternate name: implementation dissolves, judgment persists
alternate name: 実装は溶ける、判断は残る @ja
description: AAP's core thesis line. Specific implementations (PreToolUse hooks, CLI approval prompts, JSONL episode logs, distill pipelines) are temporary forms that get replaced as tooling changes. What persists across implementation dissolution is the judgment layer: what should be constrained, and who is responsible. Each ADR records the persistent judgment with the project-specific implementation that surfaced it stripped out — which is why AAP targets DOI and version-controlled artifacts rather than a framework release.
subject of: AAP Thesis
subject of: Industry Mechanism Layer Mapping (2026 Q2 snapshot)

Phase-crossing decision
type: Concept
type: DefinedTerm
alternate name: Phase-crossing decision
alternate name: フェーズ越境の判断 @ja
description: The explicit, recorded act required when an Autonomous Agentic Loop Quadrant component is moved from the design phase to the operation phase. Optimization axes invert between phases (flexibility ↔ predictability); the crossing is not a free continuation but a decision with its own accountability load. Surfaces in ADR-0010 and descends to skill-design granularity per essay 7.
defined by: ADR-0010: Phase Separation Between Design and Operation (experimental)
applies to: Autonomous Agentic Loop Quadrant

moral crumple zone
type: Concept
type: DefinedTerm
alternate name: moral crumple zone
alternate name: モラル・クランプル・ゾーン @ja
description: Madeleine Clare Elish's term for the human operator who absorbs blame for failures of an automated system whose decisions are no longer separable post-hoc. Applied in AAP essay 5 to autonomous agents: when judgment elements blend at runtime in the Autonomous Agentic Loop Quadrant, the deploying organization commits to a principled attribution gap whose human end-point becomes the crumple zone unless a gap-bearer is pre-named (ADR-0009 / ADR-0008).
cited by: The LLM Workflow Quadrant Is Missing from Our Vocabulary

LLM function
type: Concept
type: DefinedTerm
alternate name: LLM function
alternate name: LLM 関数 @ja
description: Architectural primitive of the LLM Workflow Quadrant Batch sub-form (3b): an ordinary function in a codebase whose body delegates the judgment to an LLM call, with a defined input type, a defined output schema, and one judgment responsibility. From the caller's perspective the LLM function behaves like any other function — defined input goes in, a value of a defined type comes out — except the output may fluctuate probabilistically since an LLM is the judging organ. Does not decide what to do next; the caller (deterministic control flow in the surrounding code) does. Canonical examples: match_line_items(invoice_lines, po_lines) -> Verdict (essay 4 invoice-matching), score_relevance(post_text) -> float and generate_comment(post_text) -> Optional[str] (Contemplative Agent feed-processing pipeline). Contrast with a general-purpose agent: an LLM function is narrow by design — fifty judgment categories produces fifty narrow functions, not one generalist.
applies to: LLM Workflow Quadrant — Batch sub-form (3b)
defined by: Where ReAct Agents Are Actually Needed in Business
instantiated by: contemplative-agent

Seven-essay narrative spine (April-May 2026)
type: ExternalReference
type: Collection
type: CreativeWork
description: Three trilogy essays followed by four architectural follow-ups that introduced the four-quadrant decomposition, named the principled vs artificial redirect impossibility, surfaced the design / operation Phase distinction, and descended that distinction to skill-design granularity. Source narrative for AAP's harness-neutral judgments.
creator: Tatsuya Shimomoto
has part: A Sign on a Climbable Wall: Why AI Agents Need Accountability, Not Just Guardrails
has part: Can You Trace the Cause After an Incident?
has part: AI Agent Black Boxes Have Two Layers: Technical Limits and Business Incentives
has part: Where ReAct Agents Are Actually Needed in Business
has part: The LLM Workflow Quadrant Is Missing from Our Vocabulary
has part: Is ReAct Needed in Production? — Separating Design and Operation Phases
has part: Between the Workflow and ReAct Quadrants: How Phase Decides Skill Design

A Sign on a Climbable Wall: Why AI Agents Need Accountability, Not Just Guardrails
type: ExternalReference
type: ScholarlyArticle
description: Problem statement (trilogy 1/3). Signs on climbable walls are meaningless; the signpost pattern has been known to fail for 2400 years. What is needed is accountability architecture.
date published: 2026-04-06
narrative position: 1
creator: Tatsuya Shimomoto

Can You Trace the Cause After an Incident?
type: ExternalReference
type: ScholarlyArticle
description: Application (trilogy 2/3). Post-incident causal tracing requires build-time structure. The structures that emerge — segregation of duties, least privilege, four-eyes approval, audit trails — are structurally identical to the practices organizations have refined over centuries.
date published: 2026-04-13
narrative position: 2
creator: Tatsuya Shimomoto

AI Agent Black Boxes Have Two Layers: Technical Limits and Business Incentives
type: ExternalReference
type: ScholarlyArticle
description: Obstacle analysis (trilogy 3/3). Blackbox has two layers: model-weights internalization (technical) and commercial secrecy (business). The resolution is defining the minimum set that makes causal tracing possible.
date published: 2026-04-14
narrative position: 3
creator: Tatsuya Shimomoto

Where ReAct Agents Are Actually Needed in Business
type: ExternalReference
type: ScholarlyArticle
description: Architectural triage by quadrant (follow-up 1/4). Business AI sorts along two axes into four quadrants — Script, Algorithmic Search, LLM Workflow, Autonomous Agentic Loop. Most current LLM applications belong to LLM Workflow Quadrant; forcing them into Autonomous Agentic Loop architecture is a structural source of accountability collapse.
date published: 2026-04-29
narrative position: 4
creator: Tatsuya Shimomoto

The LLM Workflow Quadrant Is Missing from Our Vocabulary
type: ExternalReference
type: ScholarlyArticle
description: Vocabulary diagnosis and the principled attribution gap (follow-up 2/4). The industry lacks a positive name for the LLM Workflow Quadrant; non-deterministic work is routed through the Autonomous Agentic Loop by elimination. Autonomous Agentic Loop work blends judgment elements at runtime, foreclosing post-hoc separability — Elish's moral crumple zone applied to autonomous agents.
date published: 2026-04-30
narrative position: 5
creator: Tatsuya Shimomoto

Is ReAct Needed in Production? — Separating Design and Operation Phases
type: ExternalReference
type: ScholarlyArticle
description: Temporal axis (follow-up 3/4). Business work splits into design and operation phases with inverted optimization axes (flexibility vs predictability). Compressing both phases into one system is the deepest layer of confusion. Proposal: surface the Phase-crossing decision explicitly when an autonomous loop is placed in operation.
date published: 2026-05-01
narrative position: 6
creator: Tatsuya Shimomoto

Between the Workflow and ReAct Quadrants: How Phase Decides Skill Design
type: ExternalReference
type: ScholarlyArticle
description: Phase descends to skill design (follow-up 4/4). LLM Workflow Quadrant and Autonomous Agentic Loop Quadrant are not a clean dichotomy — there is a continuous gradient. The Phase Separation introduced in essay 6 descends from business systems to individual skill design, with object specifiability and scale-resilience as secondary forces.
date published: 2026-05-02
narrative position: 7
creator: Tatsuya Shimomoto

Where Does the Accountability Externalized by AI Go?
type: ExternalReference
type: ScholarlyArticle
alternate name: Where Does the Accountability Externalized by AI Go?
alternate name: AIによって外部化された責任は、どこへ行くのか @ja
description: Companion essay forming AAP's social-consequence layer. A derivative that sits on top of the seven-essay narrative spine, not within it — deliberately carries no narrativePosition and is not part of the spine Collection. Extends the accountability-distribution argument outward: externalized accountability does not disappear; nameable consequence flows into institutions (litigation, compensation, regulation), un-nameable consequence converges violently onto the most visible individual (the scapegoat mechanism). Reframes the minimum disclosure set as an effluent-record-equivalent evidence base and the pre-named gap-bearer as an institutional receptacle that is the structural opposite of a scapegoat. The harness-neutral structural claim is recorded in docs/social-consequence.md; the concrete cases (industrial pollution, specific incidents) live in this essay. First published on Substack.
date published: 2026-05-24
language: en
language: ja
creator: Tatsuya Shimomoto
is based on: Agent Attribution Practice (AAP)
about: externalized accountability

AAP Thesis
type: ExternalReference
type: CreativeWork
description: Repository thesis: implementation dissolves; judgment persists. Accountability distribution (not capability distribution) is AAP's organizing principle, and harness-neutral judgments are the durable layer worth recording while specific implementations rotate out.

Industry Mechanism Layer Mapping (2026 Q2 snapshot)
type: ExternalReference
type: CreativeWork
description: Time-bound mapping between specific vendor mechanisms and the ADRs they instantiate. Deliberately separated from ADR bodies so the judgments themselves stay clean: this file decays as vendor products evolve, the ADRs do not. Honors the 'implementation dissolves; judgment persists' thesis at the documentation layer.
temporal coverage: 2026-04/2026-06

AI Governance Framework Mapping (2026 Q2 reading)
type: ExternalReference
type: Collection
type: CreativeWork
description: Time-bound directory mapping AAP's ADRs and Quadrants to clauses of national / international AI governance frameworks (NIST AI RMF, ISO/IEC 42001, with EU AI Act and OECD AI Principles deferred to a later release). Sibling of industry-mapping.md but targeting a different reader audience (policy / compliance officer vs engineer / architect) and decaying on framework revision cycles (yearly to multi-year) rather than vendor product release cycles. Deliberately separated from ADR bodies so judgments stay framework-neutral.
temporal coverage: 2026-04/2027-04
has part: NIST AI RMF mapping to AAP ADRs
has part: ISO/IEC 42001 mapping to AAP ADRs

NIST AI RMF mapping to AAP ADRs
type: ExternalReference
type: CreativeWork
description: Per-ADR mapping of AAP's ten ADRs to NIST AI RMF 1.0 functions (GOVERN / MAP / MEASURE / MANAGE) and Generative AI Profile (NIST.AI.600-1) risk categories. Reverse index from NIST function and GAI risk category to applicable ADRs. AAP-side reading, not a compliance attestation. Decays on NIST revision and on GAI Profile profile revision.
temporal coverage: 2026-Q2/2027-Q2

ISO/IEC 42001 mapping to AAP ADRs
type: ExternalReference
type: CreativeWork
description: Per-ADR mapping of AAP's ten ADRs to ISO/IEC 42001:2023 body clauses (4–10, the Annex SL Harmonized Structure) and Annex A control areas (A.2–A.10). PDCA × Phase Separation section discusses how ADR-0010's Phase axis sits inside the AIMS PDCA cycle. Reverse index from ISO area to applicable ADRs. AAP-side reading, not a compliance attestation. Decays on ISO revision and on amendment publication.
temporal coverage: 2026-Q2/2028-Q4