Skip to main content
The paper anchors five companion documents, each with a different job:

​
From contracts to standards

The paper identifies several possible open contracts. A contract is ready for standards work when two or more independent implementations need the same stable boundary. The likely order is:
  1. Agent Application conformance and package contract. This would define the minimum portable declaration of programs, capabilities, permissions, evaluations, and workspace requirements.
  2. Agent Artifact contract. This would cover identity, content and state, provenance, permissions, versions, rendering, and actions. See Agent Artifact for the two-layer model.
  3. Workspace and lineage export. This would carry portable state and its release and overlay history, using secret references instead of credentials.
  4. Agent identity and delegated authority. This work comes later, after principal and cross-system authority models are mature enough to support a shared abstraction.
When the first contract is ready, it will appear here as a versioned specification with its own change process, following the model established by the Model Context Protocol.