ArchivePub 1.0 - the federation protocol is final
Cet article est en anglais.
Editor’s note, 2026-10-26: In the history below, v0.1 to v1.0 are revisions of the protocol document, not Artist Alley releases. Artist Alley delivers activities to one inbox per instance (
POST /federation/inbox), with one queued delivery per recipient, not to a separate inbox and outbox for each actor. The encryption steps describe the protocol and the work toward it. Today Artist Alley tries to encrypt an activity’s contents when the peer supports encryption and the recipient’s key is available. The outer envelope, which shows who sent the activity, its type and who it is addressed to, stays readable, and if the sender’s key is missing or unusable, or encryption fails, the activity is sent unencrypted instead. Artist Alley does not yet look up the tier of outgoing activities, so it treats them as public, and the refusal to send restricted or embargoed content is not in effect. On receipt, the check that rejects unencrypted activities about restricted or embargoed content covers assets only, and an envelope sealed with an older sender key does not decrypt. Pairing two instances does not by itself share anything or guarantee encryption. The conformance scenarios run Artist Alley against itself; no other implementation has shown interoperability yet.
Editor’s note, 2026-10-21: The v1.0 stamp recorded here was a project release designation, not an independent conformance certification. The normative specification is
docs/spec/federation/v1.mdin the source repo;docs/protocol/archivepub.md, named below, is an overview, and where the two disagree the specification governs. Artist Alley does not yet meet every requirement of the specification: per-actor envelope signatures are not yet created or verified (requests are authenticated per instance), unknown top-level fields are not yet rejected, and only likes and comments take effect between instances today; sharing assets, reviews, and workflow state is planned. The ArchivePub page lists what works today. The original post below is unchanged.
ArchivePub, the ActivityPub-shaped federation protocol that lets independently-operated DAM instances share assets, reviews, and workflow state, is now at v1.0 (final), stamped 2026-07-13.
v1.0 is a spec-only change: no new wire format, no code. It ratifies the exact protocol surface that shipped as v1.0-rc1, after the 7-day release-candidate soak window closed clean on 2026-06-22. The Appendix A conformance test vectors, locked at rc1, carry through unchanged.
How it got here
ArchivePub grew alongside Artist Alley’s federation arc, tracked in the spec’s own change log:
- v0.1 (2026-06-09) captured the protocol at the point per-actor
inbox/outbox delivery shipped: the signed JSON envelope, the
aa:activity/object vocabulary, and content-addressedcas://references. - v0.2 → v0.8 built out the encryption arc: per-user X25519 keypairs, encryption-key distribution, peer capability negotiation, the per-recipient NaCl-box envelope, receiver-side decryption with a retained-key rotation window, sender refusal for restricted/embargo tiers, and key-rotation lifecycle (see ADR 0049).
- v1.0-rc1 (2026-06-15) was the cap-stone (the receiver-side encryption gate activated) and locked the conformance vectors.
The aa: namespace prefix, reserved as “may change” during the draft window,
was finalised at rc1 and is now stable.
What “final” means for implementers
- The wire format is frozen. The envelope (
@context: https://artist-alley.org/protocol/v1, Ed25519 signature over RFC-8785 canonical JSON), theaa:vocabulary, the capability-negotiation handshake, and the NaCl-boxencryptionblock are stable at v1.0. Future revisions follow standardmajor.minor.patchsemantics: a breaking wire change would require a major bump. - Conformance is defined. An implementation claiming ArchivePub conformance MUST pass the locked Appendix A scenarios (01, 05, 06, 07, 08, 09, 11, 12) against a peer running the reference implementation.
- Pin your references. Implementers building against ArchivePub should pin
to a specific commit of the spec and of the reference implementation
(Artist Alley, see
app/internal/federation/).
The spec currently lives in the OSS repo (docs/protocol/archivepub.md) and
will move to a dedicated home when it settles into a versioned-changelog
cadence. For the protocol overview (envelope shape, trust model, and the
sharing lifecycle), see the ArchivePub page.