docs: surface swarm progress + add promo video#94
Merged
Conversation
The cryptographic foundation of the swarm (SWARM_SPEC v1, Ed25519 signing, JCS canonicalization, wire-validator, .well-known discovery, peer/signed-record storage — PRs #78,#79,#81,#82,#85,#89,#91,#92) was landing on main while the README/MANIFESTO still claimed "pairing/swarm/federation deferred". This commit fixes that mismatch. README (EN+DE): - new "Swarm — federation in flight" section with merged-PR table and a "what is next" subsection pointing to the swarm label - Roadmap rewritten: phase 4-5 from "deferred" to "Phase 1 shipped" - existing /.well-known/mycelium-node block folded into the new section - promo video as a clickable poster near the top, served from a v0.4-swarm-phase-1 GitHub release asset (14 MB H.264 1080p) MANIFESTO (EN+DE): - "What is built today" split into brain core + Swarm Phase 1 - aspirational Tailscale+mTLS / mutual-pairing claims removed; those pieces remain on archive/swarm-deferred as historical reference - "What is not built yet" sharpened to the social layer (verification, reputation, banishment-by-consensus, Sybil resistance) plus micro-transactions Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🇬🇧 English · 🇩🇪 Deutsch unten
Summary
archive/swarm-deferred, and sharpens What is not built yet to the remaining social layer (verification, reputation, banishment-by-consensus, Sybil resistance) plus micro-transactions.docs/images/promo-poster.png.Why this matters
The cryptographic foundation of the swarm (SWARM_SPEC v1, Ed25519 signing, JCS canonicalization, wire-validator,
.well-knowndiscovery, peer / signed-record storage) was landing onmainover 2026-04-27 → 2026-04-28 while the README and MANIFESTO still claimed the swarm was deferred. The repo's outward presentation lagged behind reality. This PR realigns the docs with what actually ships onmain.Test plan
[swarm]label link goes to the issue list🇩🇪 Deutsch
Zusammenfassung
archive/swarm-deferredals historische Referenz), und schärft Was noch nicht gebaut ist auf die soziale Schicht (Verifikation, Reputation, Bann-durch-Konsens, Sybil-Resistenz) plus Mikrotransaktionen.docs/images/promo-poster.png.Warum das wichtig ist
Das kryptografische Fundament des Schwarms (SWARM_SPEC v1, Ed25519-Signatur, JCS-Canonicalize, Wire-Validator,
.well-known-Discovery, Peer-/Signed-Record-Storage) ist zwischen 2026-04-27 und 2026-04-28 aufmaingelandet — während README und MANIFESTO noch behaupteten, der Schwarm sei deferred. Die Außendarstellung des Repos hing hinter der Realität zurück. Dieser PR bringt die Dokumente mit dem tatsächlichen Stand aufmainin Deckung.Testplan
[swarm]-Label-Link zeigt auf die Issue-Liste🤖 Generated with Claude Code