agent-capability-standard
Health Uyari
- License — License: Apache-2.0
- Description — Repository has a description
- Active repo — Last push 0 days ago
- Low visibility — Only 6 GitHub stars
Code Gecti
- Code scan — Scanned 12 files during light audit, no dangerous patterns found
Permissions Gecti
- Permissions — No dangerous permissions requested
Bu listing icin henuz AI raporu yok.
Agent Capability Standard is an open specification for composable AI agent capabilities. It defines 36 atomic capabilities across 9 cognitive layers, a type-safe workflow DSL, and grounded world modeling with trust-aware conflict resolution. Built on the Grounded Agency philosophy, it makes agent reliability structural—not optional.
Agent Capability Standard
Grounded Agency: A framework for building AI agents that know what they don't know.
Versioning: The spec version (v1.1.0, Candidate Standard; v1.0.0 still supported) tracks the standard itself. The plugin version (v2.0.0) tracks the Claude Code implementation. The Python package (
grounded-agency) uses its own SemVer. See GOVERNANCE.md for the versioning policy.
# Install as Claude Code plugin
claude plugin marketplace add synaptiai/synapti-marketplace
claude plugin install agent-capability-standard
What Is This?
Agent Capability Standard is the technical specification. Grounded Agency is the philosophy behind it.
Most AI agent systems fail in production because:
- Composition is implicit (no contracts between capabilities)
- State is ungrounded (no provenance for claims)
- Conflict resolution is undefined (no trust model)
- Safety is retrofitted (no checkpoints or rollback)
This standard fixes that by making reliability structural—not optional.
The Core Idea
Every agent action should be:
- Grounded — backed by evidence, not hallucination
- Auditable — with provenance and lineage
- Safe — mutations require checkpoints
- Composable — typed contracts between capabilities
The Periodic Table of Agent Capabilities
Just as chemistry has ~118 elements that compose into infinite molecules, this standard defines 36 atomic capabilities that compose into infinite workflows.
┌─────────────────────────────────────────────────────────────────────────┐
│ CAPABILITIES (atoms) → WORKFLOWS (molecules) │
│ │
│ observe + search + plan → debug_code_change │
│ + checkpoint + execute │
│ + verify + rollback │
│ │
│ receive + transform + integrate → digital_twin_sync_loop │
│ + detect + plan │
│ + checkpoint + mutate + audit │
└─────────────────────────────────────────────────────────────────────────┘
Capabilities are atoms: Irreducible primitives with defined I/O contracts.
Workflows are molecules: Compositions that solve real problems.
The goal isn't more atoms—it's better molecules.
Why 36?
The 36 capabilities were systematically derived from first principles:
- Cognitive architecture analysis (BDI, SOAR, ReAct patterns)
- Industry tool patterns (MCP, LangChain, Claude Skills)
- Rigorous atomicity testing (cannot be decomposed further)
Each capability:
- Performs exactly one irreducible cognitive operation
- Has a well-defined I/O contract with evidence anchors
- Maps to how agents actually work in production
Domain specializations become parameters, not separate capabilities. detect(domain: anomaly) rather than detect-anomaly.
For the full derivation methodology, see docs/methodology/FIRST_PRINCIPLES_REASSESSMENT.md.
Why This Matters
The Problem
AI agents in production fail silently. When a retrieval step hallucinates, downstream actions proceed with bad data. When conflicts arise between sources, there's no resolution strategy. When mutations fail, there's no rollback.
These aren't edge cases—they're the norm. Most agent systems lack structural safeguards, so failures are discovered after the damage is done.
The Cost
- Debug time: Hours tracing why an agent made a decision with no audit trail
- Data corruption: Unrecoverable state from failed mutations without checkpoints
- Trust erosion: Users lose confidence after unexplained failures
- Compliance risk: Auditors ask "why did the agent do X?" and you can't answer
The Solution
This standard makes failures visible and recoverable:
- Every claim traces to evidence (or explicitly marks uncertainty)
- Every mutation has a checkpoint (rollback is always possible)
- Every conflict has a resolution strategy (trust model decides)
- Every decision has lineage (audit answers "why")
When to Use This
| If you have... | This standard provides... |
|---|---|
| Agents that sometimes give wrong answers | Grounding with provenance trails |
| Workflows that fail mid-execution | Checkpoints and recovery loops |
| Multiple data sources that conflict | Trust-weighted conflict resolution |
| Compliance/audit requirements | Complete action lineage |
| Complex multi-step agent pipelines | Typed contracts between capabilities |
| Production systems where failures are costly | Safety by construction, not by hope |
Quick Start
Option 1: Claude Code Plugin (Recommended)
Install from the Synapti marketplace:
# Add the marketplace (one-time)
claude plugin marketplace add synaptiai/synapti-marketplace
# Install the plugin
claude plugin install agent-capability-standard
This gives you:
- 36 atomic capability skills organized by layer
- Workflow patterns that compose capabilities
- Safety hooks (checkpoint enforcement, audit logging)
Option 2: Standalone Validation
Use the validator independently:
# Clone the repository
git clone https://github.com/synaptiai/agent-capability-standard.git
cd agent-capability-standard
# Set up Python environment (Python >= 3.10; builds the Rust core, so Rust >= 1.86 is required)
python -m venv .venv && source .venv/bin/activate
pip install -e ".[dev]" -c constraints.txt
# Validate workflows (defaults to schemas/workflow_catalog.yaml; --catalog PATH for another file)
python tools/validate_workflows.py
# → VALIDATION PASS
# Run conformance tests
python scripts/run_conformance.py
# → Conformance PASSED
Next: See QUICKSTART.md for a guided walkthrough.
Choose Your Path
| I want to... | Start here |
|---|---|
| Evaluate if this fits my needs | FAQ → Whitepaper |
| Use this in Claude Code | Quickstart (10 min) |
| Build agents with the Python SDK | SDK Guide |
| Read the formal specification | STANDARD-v1.1.0.md |
| Create custom workflows | Tutorial (30 min) |
| Contribute to the standard | CONTRIBUTING.md |
| Deploy in a regulated industry | Compliance Suite |
What's Included
36 Atomic Capabilities
Organized across 9 cognitive layers with explicit input/output schemas:
| Layer | Count | Capabilities |
|---|---|---|
| PERCEIVE | 4 | retrieve, search, observe, receive |
| UNDERSTAND | 6 | detect, classify, measure, predict, compare, discover |
| REASON | 4 | plan, decompose, critique, explain |
| MODEL | 5 | state, transition, attribute, ground, simulate |
| SYNTHESIZE | 3 | generate, transform, integrate |
| EXECUTE | 3 | execute, mutate, send |
| VERIFY | 5 | verify, checkpoint, rollback, constrain, audit |
| REMEMBER | 2 | persist, recall |
| COORDINATE | 4 | delegate, synchronize, invoke, inquire |
Workflow Patterns
Capabilities compose into reusable workflow patterns:
| Pattern | Purpose | Key Capabilities |
|---|---|---|
| analyze | Examine data thoroughly | retrieve → detect → classify → explain |
| mitigate | Reduce identified risks | detect → measure → plan → execute → verify |
| optimize | Iteratively improve | observe → discover → compare → mutate → verify |
| orchestrate | Coordinate multiple agents | decompose → delegate → synchronize → integrate |
See WORKFLOW_PATTERNS.md for the complete pattern catalog.
12 Composed Workflows
Reference workflow compositions defined in the workflow catalog, with gates, failure modes that roll back on error, and typed bindings. Five of these are also available as composed skills for direct invocation:
| Workflow | Goal | Risk |
|---|---|---|
monitor_and_replan |
Detect world changes and trigger replanning | Medium |
clarify_intent |
Resolve ambiguous user requests | Low |
debug_code_change |
Safely diagnose and fix bugs | Medium |
world_model_build |
Construct grounded world model | Low |
capability_gap_analysis |
Identify missing capabilities | Low |
digital_twin_sync_loop |
Synchronize digital twin state | High |
digital_twin_bootstrap |
Initialize and run first sync | High |
rag_pipeline |
Retrieve and generate grounded response | Low |
security_assessment |
Assess vulnerabilities with risk scoring | Low |
multi_agent_orchestration |
Coordinate agents for complex tasks | Medium |
data_quality_pipeline |
Detect, classify, and clean data quality issues | Low |
model_deployment |
Safely deploy ML model to production | High |
Domain Profiles
Pre-configured trust weights, risk thresholds, and checkpoint policies for specific industries:
| Domain | Key Feature | Profile |
|---|---|---|
| Healthcare | Advisory-only, 7-year audit retention | Guide |
| Manufacturing | Sensor trust (0.92-0.95), human-required mutations | Guide |
| Data Analysis | Lineage grounding, statistical uncertainty | Guide |
| Personal Assistant | Highest user trust (0.98), never auto-send | Guide |
| Vision / Audio / Multimodal | Cross-modal consistency, spatial/temporal grounding | Guide |
Canonical Schemas
- Capability Ontology — 36 atomic capabilities with I/O contracts (ontology)
- Workflow DSL — Typed bindings, gates, failure modes and recovery loops (no reference workflow uses a loop; see STANDARD §5.12)
- World State — Observations with provenance and uncertainty
- Trust Model — Authority ranking with time decay
Safety Hooks
Hooks implementing SAFETY layer capabilities:
| Hook | Capability | Purpose |
|---|---|---|
pretooluse_require_checkpoint.sh |
checkpoint |
Enforce checkpoint before mutations |
posttooluse_log_tool.sh |
audit |
Maintain audit trail |
Documentation
For Users
| Document | Purpose |
|---|---|
| QUICKSTART.md | Validate a workflow in 10 minutes |
| TUTORIAL.md | Build your first workflow (30 min) |
| GLOSSARY.md | Key terms and definitions |
| FAQ.md | Common questions |
| MODALITY_HANDLING.md | Working with vision, audio, and multimodal domains |
| ORCHESTRATION_EXTENSIONS.md | Triggers, escalation, waiting, approval, delegation, quorum and sender identity (Standard v1.1) |
| RUNNING_WORKFLOWS.md | Running workflows on the reference executor with a host |
| PERSPECTIVE_VALIDATION_CHECKLIST.md | Socio-technical and governance review checklist (PVC) |
For Implementers
| Document | Purpose |
|---|---|
| STANDARD-v1.1.0.md | Formal specification (Candidate Standard, accepted by RFC-0003 and RFC-0004) |
| STANDARD-v1.0.0.md | Previous specification (still supported) |
| CONFORMANCE.md | Conformance levels and testing |
| SECURITY.md | Threat model and mitigations |
For Contributors
| Document | Purpose |
|---|---|
| CONTRIBUTING.md | How to contribute |
| GOVERNANCE.md | RFC process |
| ROADMAP.md | Future plans |
Methodology
| Document | Purpose |
|---|---|
| FIRST_PRINCIPLES_REASSESSMENT.md | How 36 capabilities were derived |
| AGENT_ARCHITECTURE_RESEARCH.md | Industry patterns research |
| SKILLS_ALIGNMENT_EVALUATION.md | Validation against Claude Skills |
| WORKFLOW_PATTERNS.md | Reusable composition patterns |
| EXTENSION_GOVERNANCE.md | When to add new capabilities |
| OASF_SAFETY_EXTENSIONS.md | OASF safety property integration proposal |
Background
| Document | Purpose |
|---|---|
| WHITEPAPER.md | Design rationale and philosophy |
| RFC-0001 | Original proposal |
Directory Structure
agent-capability-standard/
├── skills/ # 36 atomic capability skills (flat structure)
│ ├── retrieve/SKILL.md # PERCEIVE layer
│ ├── search/SKILL.md
│ ├── observe/SKILL.md
│ ├── detect/SKILL.md # UNDERSTAND layer
│ ├── classify/SKILL.md
│ ├── plan/SKILL.md # REASON layer
│ ├── state/SKILL.md # MODEL layer
│ ├── generate/SKILL.md # SYNTHESIZE layer
│ ├── mutate/SKILL.md # EXECUTE layer
│ ├── verify/SKILL.md # VERIFY layer
│ ├── checkpoint/SKILL.md
│ ├── persist/SKILL.md # REMEMBER layer
│ ├── delegate/SKILL.md # COORDINATE layer
│ └── ... # (36 total skills)
├── schemas/ # Ontology + workflow + world state schemas
│ ├── capability_ontology.yaml # 36-capability ontology
│ ├── workflow_catalog.yaml
│ ├── world_state_schema.yaml
│ ├── interop/ # Framework interoperability mappings
│ │ └── oasf_mapping.yaml # OASF skill code mapping
│ └── transforms/ # Type coercion mappings
├── core/ # Rust crate: validator and executor, compiled into grounded_agency._core
├── grounded_agency/ # Python package (SDK integration)
├── hooks/ # Safety hooks (checkpoint, audit)
├── tools/ # Validator CLI (thin wrapper over core/)
├── tests/ # Conformance fixtures
├── spec/ # Standard documentation
├── docs/ # User documentation + methodology
│ ├── guides/ # User guides
│ └── proposals/ # Extension proposals
├── examples/ # Usage examples
└── templates/ # Skill templates
Claude Agent SDK Integration
The Grounded Agency capability standard integrates with the Claude Agent SDK to provide safety-first agent execution:
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions
from grounded_agency import GroundedAgentAdapter, GroundedAgentConfig
# Create adapter with strict checkpoint enforcement
adapter = GroundedAgentAdapter(GroundedAgentConfig(strict_mode=True))
# Create checkpoint before mutations
adapter.create_checkpoint(scope=["src/*.py"], reason="Before refactoring")
# Wrap SDK options with safety layer
options = adapter.wrap_options(
ClaudeAgentOptions(allowed_tools=["Read", "Write", "Edit", "Bash"])
)
# Use SDK as normal - safety is enforced automatically
async with ClaudeSDKClient(options) as client:
await client.query("Refactor the authentication module")
Features:
- Permission callbacks that block mutations without checkpoints
- Evidence anchors that track provenance for grounded decisions
- Skill tracking that updates checkpoint state when
checkpointskill is invoked - Audit trails for compliance and debugging
See docs/integrations/claude_agent_sdk.md for the full integration guide.
Install the Python package:
pip install grounded-agency
# Or with SDK support:
pip install grounded-agency[sdk]
The package includes a compiled Rust extension; installing from a source distribution needs a Rust toolchain (>= 1.86).
Installation
Claude Code Plugin
Add the Synapti marketplace to your Claude Code setup.
# Add the Synapti marketplace (one-time)
claude plugin marketplace add synaptiai/synapti-marketplace
# Install the plugin
claude plugin install agent-capability-standard
What the plugin provides:
| Component | Description |
|---|---|
| 36 Skills | Atomic capability implementations organized by cognitive layer |
| Workflow Patterns | Reusable compositions (analyze, mitigate, optimize, orchestrate) |
| Safety Hooks | Pre-tool hooks that enforce checkpoints before mutations |
| Audit Hooks | Post-tool hooks that maintain action lineage |
| Validator | Design-time validation for custom workflows |
Local Development
git clone https://github.com/synaptiai/agent-capability-standard.git
cd agent-capability-standard
python -m venv .venv && source .venv/bin/activate
pip install -e ".[dev]" -c constraints.txt # needs Python >= 3.10 and Rust >= 1.86
Validation
# Validate workflow definitions (writes tools/validator_suggestions.json)
python tools/validate_workflows.py
# Validate another catalog; --strict makes warnings fail
python tools/validate_workflows.py --catalog path/to/catalog.yaml --strict
# Generate patch suggestions
python tools/validate_workflows.py --emit-patch
# Run conformance tests
python scripts/run_conformance.py
Design Philosophy
This standard embodies the Grounded Agency approach:
- Grounded Claims — Every claim is evidence-backed or explicitly inferred
- Auditable Transforms — Deterministic or documented loss
- Safety by Construction — Mutation requires checkpoints; actions require plans
- Composable Atoms — Workflows orchestrate; capabilities do one thing
- Explicit Contracts — I/O schemas are first-class
License
Apache License 2.0. See LICENSE for details.
Citation
If you use this standard in research, please cite:
@misc{agentcapabilitystandard2026,
title={Agent Capability Standard: A Framework for Grounded Agency},
author={Bentes, Daniel},
year={2026},
url={https://github.com/synaptiai/agent-capability-standard}
}
Contributing
See CONTRIBUTING.md for guidelines and spec/GOVERNANCE.md for the RFC process.
Status: Candidate Standard v1.1.0 (accepted by RFC-0003 and RFC-0004; v1.0.0, released 2026-01-24, still supported)
Yorumlar (0)
Yorum birakmak icin giris yap.
Yorum birakSonuc bulunamadi