eatp-reference
Skill0 starsChanged 7 months agoApache-2.0View on GitHub
EATP SDK implementation reference — TrustPlane, BudgetTracker, PostureStore, security patterns, store backends, enterprise features. Use when implementing trust code, not when asking about EATP concepts (use co-reference for specs).
In this repository37 other files it gives its agents.
- .claude/rules/agents.mdAGENTS.md
- .claude/guides/claude-code/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- core-sdkSkill
- dataflowSkill
- nexusSkill
- kaizenSkill
- kailash-mcpSkill
- cheatsheetsSkill
- development-guidesSkill
- nodes-referenceSkill
- workflow-patternsSkill
- deployment-gitSkill
- frontend-integrationSkill
- testing-strategiesSkill
- architecture-decisionsSkill
- code-templatesSkill
- enterprise-infrastructureSkill
- validation-patternsSkill
- gold-standardsSkill
- security-patternsSkill
- flutter-patternsSkill
- interactive-widgetsSkill
- enterprise-ai-uxSkill
- conversation-uxSkill
- uiux-design-principlesSkill
- value-auditSkill
- ai-interaction-patternsSkill
- coc-referenceSkill
- 29-pactSkill
- claude-code-patternsSkill
- error-troubleshootingSkill
- kailash-mlSkill
- kailash-alignSkill
- co-referenceSkill
- managementSkill
- projectSkill
The file
Files
EATP SDK Implementation Reference
Implementation reference for the EATP trust module in the Kailash SDK. For EATP spec/concepts (5 elements, verification gradient, trust postures), see co-reference/eatp-spec.md.
TrustPlane Reference Implementation
Production-grade Python library implementing the full EATP trust chain.
- 3 store backends: SQLite (default), Filesystem, PostgreSQL
- Key managers: LocalFileKeyManager (Ed25519), AWS KMS (ECDSA P-256), Azure Key Vault, HashiCorp Vault
- 11 hardened security patterns validated through 14 rounds of red teaming
- 22-class exception hierarchy, all tracing to
TrustPlaneError - 1473 tests, zero CRITICAL/HIGH findings
Entry Points
- CLI:
attestcommand (Click-based) - MCP Server:
trustplane-mcpvia FastMCP - Python API:
from kailash.trust.plane.project import TrustProject
Enterprise Features
RBAC (4 roles), OIDC (JWKS auto-discovery), SIEM (CEF/OCSF/TLS syslog), Dashboard (bearer token auth), Archive (ZIP + SHA-256), Shadow mode (non-blocking evaluation)
Implementation Reference (load on demand)
- eatp-sdk-quickstart.md — Getting started, 4-operation lifecycle, store selection
- eatp-sdk-api-reference.md — Complete API surface, module reference, type signatures
- eatp-sdk-patterns.md — Implementation patterns, critical gotchas, architecture
- eatp-sdk-reasoning-traces.md — Reasoning trace extension, confidentiality, knowledge bridge
- eatp-budget-tracking.md — BudgetTracker API, SQLiteBudgetStore, integer microdollars, threshold callbacks
- eatp-posture-stores.md — PostureStore protocol, SQLitePostureStore, PostureEvidence
- eatp-security-patterns.md — Red team security patterns: lock ordering, integer arithmetic, symlink rejection
- eatp-store-backends.md — Adding new TrustPlaneStore backends (6-requirement security contract)
- eatp-trust-plane-security.md — 11 hardened security patterns (TrustPlane-specific)
- eatp-trust-plane-enterprise.md — RBAC, OIDC, SIEM, Dashboard, Archive, Shadow mode, Cloud KMS
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

