







We are a group focused on converging and working on pre-standardization of OCapN. OCapN stands for "Object Capability Network" and provides:
ocapn/draft-specifications/CapTP Specification.md at main · ocapn/ocapn
General planning and documentation repository for the OCapN protocol suite for distributed networked objects - ocapn/ocapn
ocapn/draft-specifications/Locators.md at main · ocapn/ocapn
General planning and documentation repository for the OCapN protocol suite for distributed networked objects - ocapn/ocapn
Introducing OCapN, interoperable capabilities over the network — Spritely Institute
OCapN (Object Capability Network) is a new protocol to add support for secure, seamless, and distributed (often peer-to-peer) communication for networked applications.
ocapn/draft-specifications/Netlayers.md at main · ocapn/ocapn
General planning and documentation repository for the OCapN protocol suite for distributed networked objects - ocapn/ocapn
You See a Spec, I See a Common Language, and a Common Understanding
Many engineers I’ve worked with over the years see OpenAPI and AsyncAPI as a configuration for whatever tooling outcome they desire. I see OpenAPI, AsyncAPI,...

Capability Trees: A Protocol-Level Extension of Object Capabilities, Draft 2
This draft addresses questions and feedback from the ATProto community, in particular from Zicklag (@zicklag.dev) and Brooklyn Zelenka (@expede.wtf). Draft 1 remains available for transparency.
Blog | Lexicon Community | Offprint
A working group that stewards a shared namespace for AT Protocol schemas: built in the open, governed collectively, and free for anyone to use.
Convergence Matrix — OpenHaven
Browse and filter the full convergence matrix of open tech tools. Sort by governance, capture risk, and more to surface capability overlaps across the landscape.
standards.group
standards.group — a forge for specs. Write, version, and publish specifications from your own AT Protocol account.
ATsense: ATproto-style Federation for Open Sensor Networks (Draft)
ATsense: ATproto-style Federation for Open Sensor Networks (Draft) · GitHub

How the Specifications Relate
OpenAPI, AsyncAPI, JSON Schema, Arazzo, Overlay, Spectral, APIs.json, MCP, A2A, GraphQL, gRPC, JSON-RPC, OAuth 2.0, OpenID Connect, Protected Resource Metadata, Dynamic Client Registration, Agent Skills, the AI Catalog, the RFC 9727 API Catalog, UCP and ORD — read from their published schemas, mapped by what each one points at, which property does which job, and how much vocabulary they share.

Architectures of Robust Openness -- Mark S. Miller keynote at ActivityPub 2019
[Proposal] WG for group/community standards and infrastructure in ATProto
TLDR: I’m proposing a working group to develop shared interoperable standards for community infrastructure within ATProto. Many teams are independently making foundational design decisions about group/community membership, governance, and infrastructure. Without coordination, a de facto standard will calcify from momentum rather than deliberate evaluation of the ranges of community needs. I provide initial questions and principles to start discussion. Many people, apps and projects in developme...

Capability Trees: A Protocol-Level Extension of Object Capabilities, Draft 3
This draft incorporates feedback from Brooklyn Zelenka (@expede.wtf), Daniel Holmgren (@dholms.at), and Zicklag (@zicklag.dev), and addresses questions raised in the ATProto Private Data Working Group. Draft 2 remains available for transparency.
Capability Trees: A Protocol-Level Extension of Object Capabilities, Draft 4
This draft incorporates feedback from Brooklyn Zelenka (@expede.wtf) and Daniel Holmgren (@dholms.at), and developments in the ATProto Private Data Working Group. Previous drafts remain available for transparency.