AgenticAF Community
Official@agenticaf-community · United Kingdom
A community project to define what good vendor agnostic agentic architecture looks like
Agent Skills by AgenticAF Community
Showing 7 vetted skills indexed across 1 GitHub repositories.
aaf-acc-implementation
Implement Agent Control Contracts with a YAML template for workflow governance.
aaf-architecture-review
Apply the Agentic Architecture Framework to design and review agentic systems.
aaf-orchestration-occ
Enforce the Orchestrator Capability Contract for non-bypassable agent governance.
aaf-cross-cutting
Define agent context budgets and autonomy levels for governed operations.
aaf-security
Apply the AAF Security pillar to design secure agentic systems.
aaf-epistemic-gates
Guide risk-based epistemic gate placement across Generation, Validation, and Authority phases.
aaf-cost-context
Enforce token budgets and route models to control costs in agentic AI systems.
Frequently Asked Questions About AgenticAF Community
FAQPage SchemaWhat specific tasks does the AgenticAF framework enable?▼
The framework enables the implementation of Agent Control Contracts, enforcement of Orchestrator Capability Contracts, and the placement of epistemic gates. It provides structured methodologies for defining autonomy levels, managing context budgets, and conducting formal architecture reviews to ensure system-wide governance and security compliance.
Which technical personas benefit from these governance standards?▼
System architects, security engineers, and technical leads responsible for designing autonomous systems benefit from these standards. The framework is specifically intended for professionals tasked with implementing vendor-agnostic governance, managing operational risk, and enforcing strict control boundaries within complex, multi-component distributed environments.
What are the prerequisites for implementing these governance contracts?▼
Implementation requires an existing system architecture and the adoption of YAML-based templates for defining control contracts. Users must identify specific autonomy levels and context budgets for their components before applying the AAF Security pillar and epistemic gate placement to their existing infrastructure.