







What if a PDS became more than a repository for posts? We propose using AT Protocol as a creator-controlled publication layer for declaration metadata describing digital works, making rights, provenance, and other trusted metadata independently verifiable and easier to discover.
From Personal Data Server to Personal Metadata Server
liccium.leaflet.pubJul 26, 2026 at 8:03 PM
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...

Publications
Rudy is adding permissioned posts to the AT Protocol. He will publish an open permissioned data specification, technical documentation, and a reference implementation so other AT Protocol communities can build community-governed spaces of their own.
Understanding AT Protocol
I’ve been playing around with AT Protocol. The posts on this site are now published to standard.site, and I’ve written a (very basic) WordPress plugin to display posts from my PDS on the Now page of this site.

science.latha.org
A permissioned appview for scientific documents on AT Protocol. True data ownership with optional monetization.
From Personal Data Server to Personal Metadata Server - Liccium
Liccium builds the fundamental infrastructure that enables creators and rightsholders to publish machine-readable declarations about their digital works that…
Drafts, private data, and obscurity.
The at:// protocol currently lacks any real means to have data which is both 'on-protocol', i.e. stored on your PDS in a way that you can guarantee access to...

Drafts, private data, and obscurity.
The at:// protocol currently lacks any real means to have data which is both 'on-protocol', i.e. stored on your PDS in a way that you can guarantee access to...
research.latha.org
A permissioned appview for research documents on AT Protocol. True data ownership with optional monetization.
CCFS cryptographically curated file system
The Internet was originally designed to be a next-generation phone system that could withstand a Soviet attack. Today, we ask the Internet to perform tasks that no longer resemble phone calls in the face of threats that no longer resemble Soviet bombardment. However, we have come to rely on names that can be subverted at every level of the stack or simply be allowed to rot by their original creators. It is possible for us to build networks of content that serve the content distribution needs of today while withstanding the hostile environment that all modern systems face. This dissertation presents the Cryptographically Curated File System (CCFS), which offers five properties that we feel a modern content distribution system should provide. The first property is Strong Links, which maintains that only the owner of a link can change the content to which it points. The second property, Permissionless Distribution, allows anyone to become a curator without dependence on a naming or numbering authority. Third, Independent Validation arises from the fact that the object seeking affirmation need not choose the source of trust. Connectivity, the fourth property, allows any curator to delegate and curate the right to alter links. Each curator can delegate the control of a link and that designee can do the same, leaving a chain of trust from the original curator to the one who assigned the content. Lastly, with the property of Collective Confidence, trust does not need to come from a single source, but can instead be an aggregate affirmation. Since CCFS embodies all five of these properties, it can serve as the foundational technology for a more robust Web. CCFS can serve as the base of a web that performs the tasks of today’s Web, but also may outperform it. In the third chapter, we present a number of scenarios that demonstrate the capacity and potential of CCFS. The system can be used as a publication platform that has been re-optimized within the constraints of the modern Internet, but not the constraints of decades past. The curated links can still be organized into a hierarchical namespace (e.g., a Domain Naming System (DNS)) and de jure verifications (e.g., a Certificate Authority (CA) system), but also support social, professional, and reputational graphs. This data can be distributed, versioned, and archived more efficiently. Although communication systems were not designed for such a content-centric system, the combination of broadcasts and point-to-point communications are perfectly suited for scaling the distribution, while allowing communities to share the burdens of hosting and maintenance. CCFS even supports the privacy of friend-to-friend networks without sacrificing the ability to interoperate with the wider world. Finally, CCFS does all of this without damaging the ability to operate search engines or alert systems, providing a discovery mechanism, which is vital to a usable, useful web. To demonstrate the viability of this model, we built a research prototype. The results of these tests demonstrate that while the CCFS prototype is not ready to be used as a drop-in replacement for all file system use cases, the system is feasible. CCFS is fast enough to be usable and can be used to publish, version, archive, and search data. Even in this crude form, CCFS already demonstrates advantages over previous state-of-the-art systems. When the Internet was designed, there were relatively fewer computers that were far weaker than the computers we have now. They were largely connected to each other over reliable connections. When the Internet was first created, computing was expensive and propagation delay was negligible. Since then, the propagation delay has not improved on a Moore’s Law Curve. Now, latency has come to dominate all other costs of retrieving content; specifically, the propagation time has come to dominate the latency. In order to improve the latency, we are paying more for storage, processing, and bandwidth. The only way to improve propagation delay is to move the content closer to the destination. In order to have the content close to the demand, we store multiple copies and search multiple locations, thus trading off storage, bandwidth, and processing for lower propagation delay. The computing world should re-evaluate these trade-offs because the situation has changed. We need an Internet that is designed for the technologies used today, rather than the tools of the 20th century. CCFS, which regards the trade-off for lower propagation delay, will be better suited for 21st-century technologies. Although CCFS is not preferable in all situations, it can still offer tremendous value. Better robustness, performance, and democracy make CCFS a contribution to the field. Robustness comes from the cryptographic assurances provided by the five properties of CCFS. Performance comes from the locality of content. Democracy arises from the lack of a centralized authority that may grant the right of Free Speech only to those who espouse rhetoric compatible with their ideals. Combined, this model for a cryptographically secure, content-centric system provides a novel contribution to the state of communications technology and information security.
Steps Towards an Infrastructure for Scholarly Synthesis
Sharing, reusing, and synthesizing knowledge is central to the research process, both individually, and with others. These core functions are not supported by our formal scholarly publishing infrastructure: instead of the smooth functioning of functional infrastructure, researchers resort to laborious "hacks" and workarounds to "mine" publications for what they need, and struggle to efficiently share the resulting information with others. Information scientists have proposed an alternative infrastructure based on the more appropriately granular model of a discourse graph of claims, and evidence, along with key rhetorical relationships between them. However, despite significant technical progress on standards and platforms, the predominant infrastructure remains steadfastly document-based. Drawing from infrastructure studies, we locate the current infrastructural bottlenecks in the lack of local systems that integrate discourse-centric models to augment synthesis work, from which an infrastructure for synthesis can be grown. Through 3 years of research through design and field deployment in a distributed community of hypertext notebook users, we elaborate a design vision of what can and should be built in order to grow a discourse-centric synthesis infrastructure: a thriving "installed base" of researchers authoring local, shareable discourse graphs to improve synthesis work, enhance primary research and research training, and augment collaborative research. We discuss how this design vision -- and our empirical work -- contributes steps towards a new infrastructure for synthesis, and increases HCI's capacity to advance collective intelligence and solve infrastructure-level problems.

Underlay
Publish structured data as versioned, permanent collections with schemas, provenance, and content addressing built in. Whether you're a research lab, a newsroom, a community archive, or a single developer, Underlay makes the knowledge you hold discoverable, verifiable, and easy to build on.
Protocols for Publishers
A series bringing together publishers, developers, and researchers to explore open protocols for a sustainable agentic web.
Steps Towards an Infrastructure for Scholarly Synthesis
Sharing, reusing, and synthesizing knowledge is central to the research process, both individually, and with others. These core functions are not supported by our formal scholarly publishing infrastructure: instead of the smooth functioning of functional infrastructure, researchers resort to laborious ”hacks” and workarounds to ”mine” publications for what they need, and struggle to efficiently share the resulting information with others. Information scientists have proposed an alternative infrastructure based on the more appropriately granular model of a discourse graph of claims, and evidence, along with key rhetorical relationships between them. However, despite significant technical progress on standards and platforms, the predominant infrastructure remains steadfastly document-based. Drawing from infrastructure studies, we locate the current infrastructural bottlenecks in the lack of local systems that integrate discourse-centric models to augment synthesis work, from which an infrastructure for synthesis can be grown. Through 3 years of research through design and field deployment in a distributed community of hypertext notebook users, we elaborate a design vision of what can and should be built in order to grow a discourse-centric synthesis infrastructure: a thriving “installed base” of researchers authoring local, shareable discourse graphs to improve synthesis work, enhance primary research and research training, and augment collaborative research. We discuss how this design vision — and our empirical work — contributes steps towards a new infrastructure for synthesis, and increases HCI’s capacity to advance collective intelligence and solve infrastructure-level problems.
Composing capability security and conflict-free replicated data types — Spritely Institute
In August, I attended the DWeb Seminar where a small group of builders gathered to discuss the state-of-the-art and open problems in the distributed web space. Some in the group are primarily concerned with distributed data and focus on sync algorithms and local-first use cases. I am mainly concerned with distributed behavior and focus on the object capability security model. Both areas of study are steeped in their own lore and research papers, which makes it difficult for the two camps to communicate effectively with each other.
I've been working on an "at protocol notion". One of the things that has been holding it up has been coming to terms with the oddities of putting this data on a PDS. A document is a collection of edits, whose edits we collect will change that document pretty substantially. This is a feature
Who is writing this idea up? I think we’re going to need it. There are a lot of objects out there being created as regular database entries or associated with the PDS of person who first entered them, but ideally we want to allow the creator or publisher to claim them and redirect without recreating
Paul Rohr
Ah, you're brute forcing this without asking @bnewbold.net + @dholms.at for the AT equivalent of an HTTP 301 or 308 response Mad respect