Skip to main content

Forensic investigation, dispute resolution, and risk assessment for the agent economy — the accountability layer of the Agent Trust Stack

Project description

Agent Justice Protocol

License: Apache 2.0 Python 3.8+ Zero Dependencies

Forensic investigation, dispute resolution, and risk assessment for the agent economy. The accountability layer (Layer 4) of the Agent Trust Stack.

Quickstart

pip install agent-justice-protocol
from agent_justice_protocol import (
    ForensicInvestigation, IncidentReport, AgentReference,
    EvidenceRecord, JusticeStore,
)

# Investigate an incident
report = IncidentReport(
    reporter=AgentReference(agent_id="agent-monitor-01"),
    incident_type="service_failure",
    severity="high",
    description="Agent failed to deliver contracted output",
    subjects=[AgentReference(agent_id="agent-suspect-42")],
)
investigation = ForensicInvestigation(report)
investigation.add_evidence(EvidenceRecord(
    evidence_type="interaction_log",
    provenance_tier=2,
    source_agent_id="agent-monitor-01",
    content={"action": "request_sent", "status": "timeout"},
))
finding = investigation.produce_finding()

# Store results
store = JusticeStore()
store.append_finding(finding)

Three Modules

Module Purpose Key Classes
Forensics Engine Investigate incidents: collect evidence, reconstruct timelines, flag causal indicators ForensicInvestigation, IncidentReport, EvidenceRequest, PrivacyGuard
Dispute Resolution File claims, exchange evidence (commit-reveal), arbitrate with peer panels Dispute, DisputeClaim, ArbitratorPool, render_decision
Risk Assessment Score agent risk, compute actuarial outputs for insurance underwriting RiskEngine, RiskProfile, population_risk_summary

Each module ships independently. Module 1 requires only a provenance chain. Module 2 depends on Module 1 for evidence. Module 3 consumes output from both.

CLI

# Run a forensic investigation
agent-justice investigate --reporter agent-01 --type service_failure \
    --severity high --description "Output not delivered" --subject agent-02

# File a dispute
agent-justice file --claimant agent-01 --respondent agent-02 \
    --finding <finding-id> --harm-type financial \
    --harm-description "Failed delivery" --amount 500

# Check risk profile
agent-justice query agent-02

# Store statistics
agent-justice status

Architecture

Incident
    -> [Module 1: Forensics Engine]
        Evidence collection -> Timeline reconstruction -> Causal indicators
        Output: ForensicFinding
    -> [Module 2: Dispute Resolution]
        Claim filing -> Response -> Evidence exchange -> Arbitration
        Output: ArbitrationDecision
    -> [Module 3: Risk Assessment]
        Historical findings + decisions -> Risk scoring -> Actuarial outputs
        Output: RiskProfile

Key Features

  • Evidence-first: Every dispute must be grounded in a forensic investigation
  • Provenance-tiered: Evidence weight scales with quality (Tier 1 cryptographic > Tier 4 self-reported)
  • Privacy-protected: Anti-fishing rules prevent weaponization of investigations (Rules 5/5a)
  • Commit-reveal: Blind evidence exchange prevents strategic adaptation
  • Three resolution tiers: Automated (<$1K), peer arbitration ($1K-$50K), human escalation (>$50K)
  • Actuarial outputs: Expected loss rate, loss severity distribution, premium basis
  • Identity-agnostic: Works with CoC, ERC-8004, A2A, W3C VC/DID, or bare URIs

Optional Integration

pip install agent-justice-protocol[coc]  # Chain of Consciousness integration
pip install agent-justice-protocol[arp]  # Agent Rating Protocol integration

Security Disclaimer (VAM-SEC v1.0)

This software is provided as a reference implementation of the Agent Justice Protocol specification. It is intended for research, development, and integration testing.

This software does not provide legal advice, legal representation, or legally binding arbitration. Dispute decisions rendered by this software are structured data outputs, not legal judgments. For disputes exceeding $50,000 or involving regulatory compliance, human legal counsel is required.

Limitations:

  • Automated causal analysis (Phase 4a) produces advisory indicators only — not causal conclusions
  • Risk scores are statistical estimates, not guarantees of future behavior
  • Actuarial outputs are starting points for underwriters, not insurance quotes
  • The commit-reveal protocol assumes honest-majority arbitrator panels

No warranties. See LICENSE for full terms.

License

Apache 2.0 — see LICENSE.

Links

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

agent_justice_protocol-0.1.1.tar.gz (51.6 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

agent_justice_protocol-0.1.1-py3-none-any.whl (44.3 kB view details)

Uploaded Python 3

File details

Details for the file agent_justice_protocol-0.1.1.tar.gz.

File metadata

  • Download URL: agent_justice_protocol-0.1.1.tar.gz
  • Upload date:
  • Size: 51.6 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.12.10

File hashes

Hashes for agent_justice_protocol-0.1.1.tar.gz
Algorithm Hash digest
SHA256 be12a26b56b9480cec76533780d47619e51f5c19ae2ebdab38a76415c5a0578d
MD5 93ac14671c7ffb810f5f9350aa1bb0a0
BLAKE2b-256 a3cf3f39c2472d874670164ac0c05fe3cb905c9ff7e2e201b7a3dcf48703054d

See more details on using hashes here.

File details

Details for the file agent_justice_protocol-0.1.1-py3-none-any.whl.

File metadata

File hashes

Hashes for agent_justice_protocol-0.1.1-py3-none-any.whl
Algorithm Hash digest
SHA256 a8bc3e8aa228bc2ab99c957d56d4677d304bb27ca83058b1cd189077a76eca7c
MD5 00500a88c759699ae9e619d76a83a7c4
BLAKE2b-256 d31d8895cd8a55e0715e9ecf3430cd85a13dd7c4e4b3372abce0695c7d837dc0

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page