docs(prd): consolidate to OpenPRD spec + add 0004 Moshpit Bridge - #65
Merged
Conversation
Remove stale artifacts and keep the Moshpit DNS/P2P family as the
canonical, conflict-free OpenPRD 0.2 set.
- Delete openprd-domain-messenger.md (ODM): a real-DNS ("Internet 2")
federation protocol that is out of scope now that we are P2P-only. It
also carried a conflicting id "0001" and an off-convention filename,
and was duplicated at docs/ root and docs/prd/.
- Delete docs/prd/plan.md: a scratch working plan, not a PRD.
Messaging is covered natively by 0003-moshpit-chat (P2P namespace).
Remaining set: 0001-namespace, 0002-hosting, 0003-chat.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
vu1nz Security Review0 finding(s) in PR #? No security issues found. |
New OpenPRD 0.2 spec for an optional, non-authoritative bridge: - inbound resolution gateway so extension-less visitors reach Moshpit sites over real DNS (operationalizes 0001 R11 + 0002 R7) - bidirectional legacy<->Moshpit identity attestation (DNS TXT / .well-known, mutual signing), salvaged from the old ODM DNS-proof mechanics without its real-DNS messaging stack - federated/self-hostable gateways; P2P directory stays source of truth Cross-linked from 0001 R11 and 0002 R7. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
ralyodio
changed the title
ralyodio
marked this pull request as ready for review
July 28, 2026 19:32
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
1 participant
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.
What
Cleans up
docs/prd/into a coherent OpenPRD 0.2 set for the Moshpit DNS/P2P direction, and adds a new bridge spec.Removed (stale)
docs/openprd-domain-messenger.mdanddocs/prd/openprd-domain-messenger.md— two identical copies of the "Open Domain Messenger (ODM)" spec. ODM was a real-DNS ("Internet 2") federation messaging protocol; out of scope now that we're P2P-only. It also carried a conflictingid: "0001"and an off-convention filename.docs/prd/plan.md— a scratch working plan, not a PRD.Added
0004-moshpit-bridge.md— an optional, non-authoritative gateway between the Moshpit namespace and legacy DNS:0001R11 +0002R7)..well-known, mutually signed) — salvaged from ODM's DNS-proof mechanics without its real-DNS messaging stack.Canonical set (OpenPRD 0.2, sequential ids, no collisions)
0001-moshpit-namespace.md0002-moshpit-hosting.md.anythingcompute grid0003-moshpit-chat.md0004-moshpit-bridge.mdCross-linked from
0001R11 and0002R7. Messaging stays P2P-native (0003); the bridge moves names and web traffic, not chat.Generated with Claude Code