Weigh in on the Desirable Properties
Confirm the public sources, then take one protocol concern into a DP and try a patch sentence. If the property would break Frequency or DSNP portability, that is exactly the comment we need.
These directions are generated from Project Liberty Labs's public corpus, not from private landing pads. Each one is a hypothesis. Follow the interest that feels like your work. The Hermes prompt and Discuss link are real contribution paths, not a brochure.
DP1 · hypothesis
Federated Authentication & Accountability
Your stated mission ("Develop decentralized technologies that promote self-sovereign digital identity, including Frequency and the Decentralized Social Networking Protocol (DSNP).") sits next to DP1's human issue: Fake accounts, scams, and impersonation. Guiding question: How can we know who we are interacting with without sacrificing privacy or decentralization?
Direction to explore
Can Labs's identity work sit beside federated authentication without becoming another platform login?
Candidate patch idea
Clarify in DP1 that self-sovereign or DSNP-class identifiers are valid accountability anchors, not second-class to platform accounts.
DP5 · hypothesis
Decentralized Namespace
Your stated mission ("Develop decentralized technologies that promote self-sovereign digital identity, including Frequency and the Decentralized Social Networking Protocol (DSNP).") sits next to DP5's human issue: Losing your identity when platforms change. Guiding question: How do names and identities persist when platforms change?
Direction to explore
Should Frequency / namespace work be named as an example of decentralized naming rather than a single mandated stack?
Candidate patch idea
Note that multiple naming systems may coexist if they remain user-portable and are not captured by one commercial resolver.
DP7 · hypothesis
Simplicity and Interoperability
Your stated mission ("Develop decentralized technologies that promote self-sovereign digital identity, including Frequency and the Decentralized Social Networking Protocol (DSNP).") sits next to DP7's human issue: Too many disconnected apps. Guiding question: How do we connect the web without forcing people into yet another app?
Direction to explore
What must stay simple so Labs's protocol work can interoperate with other Alliance layers?
Candidate patch idea
Require a documented bridge and export path between protocol identities and Overweb / layer identities.
DP4 · hypothesis
Data Sovereignty and Privacy
Your stated mission ("Develop decentralized technologies that promote self-sovereign digital identity, including Frequency and the Decentralized Social Networking Protocol (DSNP).") sits next to DP4's human issue: Companies own your data. Guiding question: Who should own your data?
Direction to explore
Where does Labs's “people own their data” language need to become an enforceable affordance?
Candidate patch idea
Require that personal data created in a layer can leave with the person, including social graph, without a platform petition.
DP11 · hypothesis
Safe and Ethical AI
Your stated mission ("Develop decentralized technologies that promote self-sovereign digital identity, including Frequency and the Decentralized Social Networking Protocol (DSNP).") sits next to DP11's human issue: AI hallucinations and harmful outputs. Guiding question: What does trustworthy AI actually look like?
Direction to explore
If Labs ships AI products, which safety claims belong in DP11 versus product policy?
Candidate patch idea
Require glass-box disclosure when AI drafts norms that later bind a community, including this briefing itself.
DP13 · hypothesis
AI Containment
Your stated mission ("Develop decentralized technologies that promote self-sovereign digital identity, including Frequency and the Decentralized Social Networking Protocol (DSNP).") sits next to DP13's human issue: AI manipulation and agent overreach. Guiding question: How do we keep AI helpful without letting agents overreach?
Direction to explore
What containment is needed before protocol-adjacent AI agents act in a shared layer?
Candidate patch idea
Sandbox agent write-access until a named human steward accepts the action against an ML-REQ.
