







Community Specification 1.0
[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...

[Proposal] WG for group/community standards and infrastructure in ATProto
Interested in contributing — specifically to Phase 1 (shared ontology and community archetypes). I’m a cognitive linguist and university researcher. My work on the AT Protocol side includes Mezzanine, an information networking system using opaque cashtag connectors as a routing layer, and two Leaflet pieces on community infrastructure as a gradient — from permissionless tag-based commons to credentialed spaces. The reason I’m flagging my disciplinary background: Phase 1 is where this WG will e...

When Does a Specification Become a Program? · The Phoenix Architecture
A spec can contain prose, tests, schemas, formal models, even executable code. The useful boundary is not the syntax but, rather, what survives: if you throw the implementation away, what has to remain so you can build the next one?
When Does a Specification Become a Program? - The Phoenix Architecture
A spec can contain prose, tests, schemas, formal models, even executable code. The useful boundary is not the syntax but, rather, what survives: if you throw the implementation away, what has to remain so you can build the next one?
When Does a Specification Become a Program? - The Phoenix Architecture
A spec can contain prose, tests, schemas, formal models, even executable code. The useful boundary is not the syntax but, rather, what survives: if you throw the implementation away, what has to remain so you can build the next one?
Governing Together: Toward Infrastructure for Community-Run Social Media
Decentralizing the governance of social computing systems to communities promises to empower them to make independent decisions, with nuance and in accordance with their values. Yet, communities do not govern in isolation. Many problems communities face are common, or move across their boundaries. We therefore propose designing for "inter-community governance:" mechanisms that support relationships and interactions between communities to coordinate on governance issues. Drawing from workshops with 24 individuals on decentralized, community-run social media, we present six challenges in designing for inter-community governance surfaced through ideas proposed in workshops. Together, these ideas come together as an ecosystem of resources, infrastructures, and tools that highlight three key principles for designing for inter-community governance: modularity, forkability, and polycentricity. We end with a discussion of how the ideas proposed in workshops might be implemented in future work aiming to support community governance in social computing systems broadly.

Where Does Community Live?
ActivityPub and ATProto both promise to rebuild social life online, but they answer the question of where community actually forms in fundamentally different ways. Protocol design is institutional design, and right now those institutions are being built.

The Specification Is Not a Document - The Phoenix Architecture
Imagine joining a software project a few years from now. It is a large, mature system. It has thousands of business rules, years of operational experience,…
LLMs as Collaborators in Language Specification and Design (PLSS 2026) - SPLASH/ISSTA 2026
Workshop on Programming Language Standardization and Specification This workshop aims to foster cross-pollination between researchers and industry professionals with experience in programming language specification and standardization. It provides a forum where participants can share insights, case studies, and best practices, and collaboratively explore solutions to current challenges. The goal of the workshop is to improve the collective understanding of how programming languages are specified, standardized, and evolved in practice. The workshop examines specifications as the foundation ...

communitycheck/design at main · rosestt/communitycheck
A design specification for attaching representative public opinion data to viral social media posts — correcting the gap between what people think and what they think others think. - rosestt/commun...
Proposal: standard.site.declaration
Proposal: standard.site.declaration Draft for Discussion Abstract AT Protocol provides portable identity, portable content, and portable social graphs. What it currently lacks is a standard mechanism for discovering machine-readable declarations associated with digital content. Today, creators and organisations publish declarations about digital assets through websites, registries, the C2PA provenance framework, and other systems. These declarations may describe provenance, copyright ownership...

What ATProto Needs to Support Consentful Distributed Community Governance
Focusing on community technology A waterwheel, a protocol, and the case for technology that communities can own.
Focusing on community technology
eskahlay.comOn March 29th, we held an in-person meeting to check in with the community and discuss potential updates to the standard.site spec. A huge thank you to @cozylittle.house for putting together a detailed summary of everything we discussed. leaflet.pub/p/did:plc:kydzcmnywraao2srchq…
Standard Site Working Group Meeting Notes 3/29/26
leaflet.pub