eatp-reference

Explains EATP trust lineage, attestation, verification gradients, and trust postures for AI agents.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/Hamza-Haadi/disease-risk-classifier-hamza --skill eatp-reference-hamza-haadi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: eatp-reference
Source: https://github.com/Hamza-Haadi/disease-risk-classifier-hamza/tree/main/.claude/skills/26-eatp-reference
Command: npx skills add https://github.com/Hamza-Haadi/disease-risk-classifier-hamza --skill eatp-reference-hamza-haadi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Enterprise AI agents need verifiable trust chains linking every action back to human authority, but concepts like trust lineage, delegation constraints, and posture management are complex and easy to misapply. This Skill provides the complete EATP (Enterprise Agent Trust Protocol) technical reference so you can explain, design, and implement agent trust correctly. ## Core Features & Use Cases - EATP Concept Reference: Covers the five trust lineage elements (Genesis Record, Delegation Record, Constraint Envelope, Capability Attestation, Audit Anchor), the four-level verification gradient, and five graduated trust postures. - SDK Implementation Guides: Companion files document the kailash trust module API, quickstart lifecycle (ESTABLISH, DELEGATE, VERIFY, AUDIT), budget tracking with integer microdollars, posture persistence with SQLite, reasoning traces, and red-team-validated security patterns. - Standards Comparison: Explains how EATP differs from OAuth/OIDC, SPIFFE/SPIRE, Zero-Trust, and PKI by adding agent trust delegation and action-to-human traceability. - Use Case: When asked to explain how an agent's spending authority is constrained and audited, load this Skill to describe constraint envelopes, cascade revocation, and the BudgetTracker reserve/record lifecycle with working Python examples. ## Quick Start Ask the AI to explain how EATP verifies that an agent's action stays within human-delegated trust boundaries.

Frequently Asked Questions about eatp-reference

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the Enterprise Agent Trust Protocol (EATP)?▼

EATP is an open standard for establishing and verifying trust in enterprise AI agent systems. It separates trust establishment (human judgment, done once) from trust verification (machine-speed, continuous), tracing every action back to human authority through cryptographic chains.

How do I get started with the EATP Python SDK?▼

Install with pip install kailash, then follow the four-operation lifecycle: ESTABLISH creates an agent trust chain, VERIFY checks permissions before actions, DELEGATE transfers constrained authority, and AUDIT records actions in a tamper-evident trail.

How does EATP differ from OAuth or SPIFFE?▼

OAuth/OIDC handles user authentication and SPIFFE/SPIRE handles service identity, but neither governs agent autonomy. EATP adds agent trust delegation, constraint envelopes, and unbroken action-to-human traceability chains.

What are the five EATP trust postures?▼

The postures are Pseudo-Agent, Supervised, Shared Planning, Continuous Insight, and Delegated, representing graduated autonomy. Postures upgrade through demonstrated performance and downgrade instantly when conditions change, including emergency downgrade to Pseudo-Agent.

How does EATP budget tracking prevent overspending?▼

BudgetTracker uses integer microdollars with a two-phase reserve/record lifecycle and fail-closed semantics. Threshold callbacks fire at 80%, 95%, and exhaustion, and SQLiteBudgetStore provides crash-safe persistence with 0o600 file permissions.

What are common gotchas when implementing EATP?▼

Key pitfalls include generate_keypair returning private key first, signatures being base64 not hex, constraints living on CapabilityAttestation rather than GenesisRecord, and reasoning signature verification requiring the parent record's context_id.