Weigh in on the Desirable Properties
If you represent Davids Legacy, confirm the source URLs, then open the Desirable Properties tab and leave a patch idea where the property text misses what your public work already argues.
These directions are generated from Davids Legacy'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.
DP8 · hypothesis
Collaborative Environment and Meta-Communities
Your stated mission ("At 16, David took his life after months of being continually harassed, humiliated and threatened by a group of students through text messages and social media.") sits next to DP8's human issue: Online communities constantly restart. Guiding question: How do communities persist beyond platforms?
Direction to explore
How do Alliance members share a collaboration space without collapsing into one platform community?
Candidate patch idea
Define meta-communities as optional shared rooms with explicit consent, not an ambient social network that harvests the Alliance listserv.
DP20 · hypothesis
Community Ownership
Your stated mission ("At 16, David took his life after months of being continually harassed, humiliated and threatened by a group of students through text messages and social media.") sits next to DP20's human issue: Platforms own everything users create. Guiding question: Who should own the next layer of the Internet?
Direction to explore
This is the anti-capture test: can Davids Legacy's coordination space stay owned by people if commercial players arrive later?
Candidate patch idea
Strengthen anti-capture language: community rules and exit rights are written before large commercial platforms are invited to play.
DP3 · hypothesis
Adaptive Governance Supporting an Exponentially Growing Community
Your stated mission ("At 16, David took his life after months of being continually harassed, humiliated and threatened by a group of students through text messages and social media.") sits next to DP3's human issue: Big Tech making all the rules. Guiding question: How can communities govern themselves without recreating Big Tech rulebooks?
Direction to explore
How should Alliance-scale governance grow without unifying everyone into one feed?
Candidate patch idea
State that adaptive governance may remain plural across Alliance members so long as interoperability and exit remain intact.
DP12 · hypothesis
Community-based AI Governance
Your stated mission ("At 16, David took his life after months of being continually harassed, humiliated and threatened by a group of students through text messages and social media.") sits next to DP12's human issue: AI rules decided by companies. Guiding question: Who should decide how AI behaves in our communities?
Direction to explore
Who ratifies AI-assisted policy when Institute, Labs, and Alliance members disagree?
Candidate patch idea
Bound AI assistance so communities can reject a draft without losing the human deliberation record.
DP4 · hypothesis
Data Sovereignty and Privacy
Your stated mission ("At 16, David took his life after months of being continually harassed, humiliated and threatened by a group of students through text messages and social media.") sits next to DP4's human issue: Companies own your data. Guiding question: Who should own your data?
Direction to explore
Where does Davids Legacy'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.
DP13 · hypothesis
AI Containment
Your stated mission ("At 16, David took his life after months of being continually harassed, humiliated and threatened by a group of students through text messages and social media.") 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.
