Skip to main content
The overview is the short public argument. The paper introduces further documents, each with a different job:

​
From contracts to standards

The paper points to several areas where an open contract may eventually help. Standards work should start when two or more independent implementations need to exchange the same information across a stable boundary. The capability model lists the parts of an Agent Application so developers can compare frameworks and framework authors can see what developers may need. Each framework retains its own project files, APIs, build process, and release artifacts. Likely candidates for future standards include:
  • An Agent Artifact contract covering identity, content and state, provenance, permissions, versions, rendering, and actions
  • A workspace and lineage export contract carrying portable state and its release and overlay history, using secret references instead of credentials
  • An agent identity and delegated authority contract, once principal and cross-system authority models can support a shared abstraction
A proposal should identify the independent implementations that need to exchange information and the exact problem they face. Its scope should stop at that boundary. Each framework keeps its own project model.