OAP
RFCs

Request for Comments

OAP evolves through public, numbered Request for Comments. Each RFC is a substantive draft authored by a Working Group, reviewed in the open, and ratified into a future version of the specification. Anyone may submit an RFC.

RFC 0001Coordination SessionsCore Protocol WGv1.1Draft
RFC 0002Negotiation ProtocolCCC WGv1.1Draft
RFC 0003Standing PermissionsCCC WGv1.1Draft
RFC 0004Sub Agent DelegationCore Protocol WGv1.1Draft
RFC 0005Canonical Entity SchemasCore Protocol WGv1.1Draft
RFC 0006Persona and Scope LayerCCC WGv1.1Draft
RFC 0007Privacy Preserving ProjectionsCCC WGv1.1Draft
RFC 0008Workflow CompositionMarketplace and Discovery WGv1.1Draft
RFC 0009Reputation and Performance RecordsTrust and Reputation WGv1.2Draft
RFC 0010Memory Exchange ProtocolCore Protocol WGv1.2Draft
RFC 0011Sybil Resistance and Sub Agent Anti AbuseTrust and Reputation WGv1.1Draft
RFC 0012The Agent Native WebWeb Integration WGv1.2Draft
RFC 0013Commerce Models for the Agent EconomyCommercial Layer WGv1.2Draft
RFC 0014Commerce Primitives, A Generalized Commercial LayerCommercial Layer WGv1.2Draft
RFC 0015Composable Software PrimitivesMarketplace and Discovery WGv1.2Draft
RFC 0016User Sovereignty CharterPrivacy and Governance WGv1.2Draft
RFC 0017Irreversibility and Cooling Off PeriodsCCC WGv1.2Draft
RFC 0018The Right to a Human PathPrivacy and Governance WGv1.2Draft
RFC 0019Conformance Testing and ImplementabilityImplementation and Conformance WGvOAP-CORE 1.2Accepted
RFC 0020Agent Query LanguageData Plane WGv1.2Draft
RFC 0021Verifiable Indexes and Match Broker ConformanceData Plane WGv1.2Draft
RFC 0022Manifest Subscription ProtocolData Plane WGv1.2Draft
RFC 0023Agent Native Storage SubstrateData Plane WGv1.2Draft
RFC 0024Schema Negotiation and VersioningData Plane WGv1.2Draft
RFC 0025Non-Commercial Conformance ProfileAccepted
RFC 0026OAP Registry ProtocolAccepted
RFC lifecycle
  1. Draft: authored by anyone, opened as a PR against oap-spec.
  2. Review: public comment period of at least 14 days.
  3. Last Call: Working Group signals intent to ratify.
  4. Ratified: merged into a numbered specification release.
Submit an RFC →