Capability records
Typed records can represent observations, corrections, decisions, procedures, skills, policies, run results and evidence.
PUBLIC · AGENT SYSTEMS
Agent Capability Formation Standard
A governance-oriented standard for retaining, evaluating, revising and reusing durable records that allow agent systems to form reusable knowledge and abilities over time.
Public standardLifecycle governanceProvenanceScope control
The standard
Durable agent state should be governed as future capability.
ACFS defines the lifecycle and governance model for agent-contributed state. Implementations remain responsible for storage, execution and transport.
Defined capabilities
What the standard governs
Stable identity
Records carry identifiers, lifecycle state, scope, authority, provenance and relationship metadata.
Explicit scope
Consumers should not apply a record outside its declared scope without authorized broadening.
Lifecycle
Submitted, Validated, Rejected, Active, Superseded, Deprecated and Revoked states make behavior governable.
Retrieval governance
Retrieval can filter by type, scope, lifecycle state, authority, provenance, recency and relation.
MCP relationship
ACFS can be transported through MCP, while lifecycle and authority rules remain binding regardless of transport.
Capability model
Contributor → Capability Store → Reviewer → Consumer.
A single implementation may combine roles, but the standard keeps their responsibilities conceptually distinct.
Contributorcreates or proposes durable knowledge
↓
Capability Storeretains identity, provenance and lifecycle
↓
Reviewer / Authorityvalidates scope and promotion
↓
Consumerretrieves only applicable capability
Formation path: Observation → Correction → Procedure → Skill → Policy. Promotion preserves provenance and should retain supporting evidence.
Authority boundary: transport, retrieval or storage does not itself grant permission to broaden scope or promote a record.
Governance & security
Durable records can change future agent behavior.
Provenance
Implementations should preserve where a record came from and what evidence supports it.
Revocation
Revoked records must not guide future behavior, while remaining available for audit when appropriate.
Risk classification
Skills, policies, triggers and action-capable records require stronger review than ordinary observations.
Poisoning defense
The standard calls out unauthorized writes, unsafe promotion, stale records, sensitive persistence and cross-agent propagation risks.
Evidence & status
Public specification focused on lifecycle and governance.
The repository defines requirement language, capability records, lifecycle states, retrieval rules, MCP relationship and security/trust considerations. It does not claim to be a storage engine or complete agent framework.
ClassificationPublic standard
Primary evidenceRepository specification and implementation guidance
ScopeCapability lifecycle, authority and governance
BoundaryNot a storage engine or agent framework
Read the standard
The public repository contains the specification and implementation guidance.