Accountability Governance Architecture (AGA™)

Official Operational Protocol for Accountability Reconstruction,
Responsibility Analysis, Authority Validation, Oversight Assessment
and Consequence Attribution

CAP™ (Chain of Accountability Protocol) is the operational protocol
of the Accountability Governance Architecture (AGA™).

While AGA™ defines the governance architecture and the governable
accountability spaces, CAP™ defines the operational methodology used
to reconstruct, analyze, validate, and attribute accountability
across complex operational environments.

CAP™ provides a structured process for identifying where
accountability originates, how it moves through operational
structures, how governance obligations are transferred or retained,
where failures occur, and who remains accountable for outcomes.

The protocol applies to:

• organizations
• institutions
• contractor networks
• subcontractor chains
• staffing agencies
• compliance investigations
• incident investigations
• operational failures
• governance failures
• AI systems
• autonomous agents
• structured agent systems
• orchestrated agent systems
• robotics environments
• Human-AI ecosystems
• future intelligent operational systems

Why CAP™ Exists

Modern operational environments rarely involve a single actor.

Most activities occur through multiple layers of:

• organizations
• managers
• contractors
• subcontractors
• agencies
• service providers
• AI agents
• autonomous systems
• robotic systems

As complexity increases, accountability becomes increasingly
difficult to identify.

Organizations often know:

• what happened

but struggle to determine:

• who authorized it
• who was responsible
• who controlled it
• who should have supervised it
• who remains accountable

CAP™ exists to systematically reconstruct that chain.

Core Protocol Question

How did accountability move through the operational system from
origin to consequence?

CAP™ Reconstruction Flow

Phase 1 — Relationship Analysis

Core Question:

What operational relationships existed between the actors?

The protocol identifies:

• direct relationships
• indirect relationships
• contractual relationships
• supervisory relationships
• delegated relationships
• Human-AI relationships
• agent-to-agent relationships

Output:

Relationship Map

Phase 2 — Authority Analysis

Core Question:

Who possessed authority and how was it obtained?

The protocol identifies:

• authority origin
• authority legitimacy
• authority delegation
• authority escalation
• authority limitations

Output:

Authority Map

Phase 3 — Responsibility Analysis

Core Question:

Who had the duty to act?

The protocol identifies:

• responsibility origin
• responsibility assignment
• responsibility continuity
• responsibility transfer
• responsibility traceability

Output:

Responsibility Map

Phase 4 — Capability Readiness Analysis

Core Question:

Was the actor capable and prepared to perform the activity?

The protocol evaluates:

• human qualification
• training
• competence
• tools
• machines
• documentation
• operational environment
• readiness conditions

Output:

Capability Readiness Assessment

Phase 5 — Control Analysis

Core Question:

Who actually controlled the activity?

The protocol identifies:

• operational control
• practical influence
• hidden control
• indirect control
• decision influence

Output:

Control Chain

Phase 6 — Oversight Analysis

Core Question:

Who had the obligation to supervise?

The protocol identifies:

• oversight obligations
• review obligations
• audit obligations
• certification oversight
• governance supervision

Output:

Oversight Map

Phase 7 — Execution Analysis

Core Question:

What activity was actually performed?

The protocol reconstructs:

• actions
• decisions
• interventions
• operational events
• execution history

Output:

Execution Timeline

Phase 8 — Evidence Analysis

Core Question:

What evidence supports the governance chain?

The protocol evaluates:

• documents
• records
• contracts
• emails
• logs
• certifications
• operational records
• witness statements
• digital evidence

Output:

Evidence Matrix

Phase 9 — Accountability Analysis

Core Question:

Who remains answerable for the outcome?

The protocol identifies:

• accountability holders
• accountability continuity
• accountability chains
• accountability conflicts
• accountability gaps

Output:

Accountability Attribution Report

Phase 10 — Consequence Attribution

Core Question:

How should consequences be attributed?

The protocol determines:

• governance failures
• accountability failures
• responsibility failures
• oversight failures
• authority failures
• capability failures
• control failures

Output:

Consequence Attribution Assessment

CAP™ Outputs

CAP™ may produce:

• Relationship Maps
• Authority Maps
• Responsibility Maps
• Capability Readiness Assessments
• Control Chains
• Oversight Maps
• Execution Timelines
• Evidence Matrices
• Accountability Attribution Reports
• Consequence Attribution Assessments

Relationship to AGA™

AGA™ defines the governance architecture.

CAP™ operationalizes the architecture.

AGA™ identifies the governable spaces.

CAP™ investigates those spaces.

AGA™ defines what must remain governable.

CAP™ reconstructs whether governance remained valid.

Canonical Principle

Accountability cannot be assumed. Accountability must
be reconstructed.

Canonical Closing Statement

CAP™ (Chain of Accountability Protocol) is the operational protocol
of the Accountability Governance Architecture (AGA™), providing a
structured methodology for reconstructing accountability across
relationships, authority structures, responsibility chains,
capability environments, operational control systems, oversight
mechanisms, evidence layers, and consequence attribution processes.

As operational environments become increasingly distributed,
autonomous, orchestrated, and complex, accountability reconstruction
becomes a foundational governance capability. CAP™ provides the
protocol for that capability.

→ Chain Accountability Protocol - (CAP)