Proposals

Proposal ID: 0000001

Submitted By: Nick Milburn

Date Submitted: 2025-10-07

Category: Membership / Platform Features

Summary: This proposal seeks to define a transparent, privacy-respecting, and equitable verification process for Refugia.social’s Verified Edition in contrast to Pseudonymous Edition. The goal is to enable trust, accountability, and credibility within the network while preserving autonomy and privacy for members.

User Stories

• As a member, I want to verify my identity so others can trust that I am a real person acting in good faith.

• As a creator or organization, I want my verified status to signal legitimacy and accountabilty.

• As a moderator, I want clear, auditable verification standards to ensure fairness.

• As a pseudonymous or privacy-conscious user, I want the option to remain unverified while still participating meaningfully.

Objectives

• Define the verification criteria for individuals and organizations.

• Establish who administers verification and how it is governed.

• Outline benefits and responsibilities of verified members.

• Ensure privacy-first data handling, minimizing collection and centralization.

• Provide transparent processes for appeal, revocation, and updates.

Potential Approaches

• Web-of-Trust Verification: Members vouch for one another.

• Proof-of-Organization: Cooperatives, collectives, or institutions verify through domain or documents.

• Third-Party Privacy-Preserving Verification: Integrate protocols like BrightID, Ceramic, or Idena.

• DAO Verification Committee: Rotating members review applications transparently.

Benefits

• Strengthens trust and safety in federated networks.

• Enables verified collaboration between individuals and organizations.

• Supports higher-tier editions (Amplifier, Materializer) and DAO governance participation.

• Provides a decentralized, non-extractive alternative to centralized “real-name” systems.

Open Questions

• Should verification cover individuals, organizations, or both?

• Should it be free, require a stake, or labor contribution?

• How to include members without traditional IDs or institutional ties?

• What level of transparency should members choose for verification?

Proposed Next Steps

• Form a Verification Working Group under the Membership Committee.

• Conduct research and member feedback on privacy, accessibility, and feasibility.

• Draft an implementation plan with mechanisms, governance, and resource needs.

• Return the plan to the DAO for ratification.

Resources Needed

• Developer and technical staff for API integration and federation.

• Security & privacy audit for profile linking.

• Minimal storage and server resources for imported content.

Timeline / Milestones

• Formation of Working Group – [TBD]

• Research & Member Feedback – [TBD]

• Draft Implementation Plan – [TBD]

• DAO Ratification Vote – [TBD]

Deliverables

• Verified Edition governance rules and criteria

• Verification workflow & technical implementation plan

• Privacy policy for identity data

• DAO-approved operational procedures for verification

• Updates to DAO Constitution, as required

Proposal ID: 0000002

Submitted By: Nick Milburn

Date Submitted: 2025-10-07

Category: Membership / Platform Features

Summary: Define the process, permissions, and benefits for Amplifier Edition accounts, enabling creators and organizations to integrate existing “root profiles” from other platforms while participating fully in Refugia’s federated ecosystem.

User Stories

• Creators want their work to reach cooperative and federated audiences without rebuilding from scratch.

• Organizations want to ensure integrity and trust when entering a new ecosystem.

• Communities benefit from curated content aligned with cooperative principles.

Objectives

• Amplifier Edition extends Pseudonymous Edition features.

• Users can link their external profiles to Refugia, bringing content and credibility across federated networks.

• Designed for creators and organizations who already maintain a digital presence.

• Encourages collaboration, collective curation, and circulation in communities that prioritize integrity over algorithmic amplification.

Potential Approaches

• Profile Linking: Securely connect external accounts without exposing sensitive credentials.

• Content Import & Amplification: Synchronize selected posts, projects, or media streams into Refugia.

• Curation Participation: Amplifier members can contribute to DAO-driven content curation and community recommendation systems.

• Optional Verification: Amplifier Edition members may opt to combine with Verified Edition for additional credibility.

Open Questions

• Should Amplifier Edition accounts be monetized or subscription-based (e.g., $10/month)?

• How do we verify that external profiles are legitimately owned without compromising privacy?

• What limits, if any, should exist on content syncing and amplification?

• Should Amplifier Edition members gain voting rights or curation privileges?

Proposed Next Steps

• Form Amplifier Working Group.

• Define technical workflow for secure profile linking and content amplification.

• Draft user guidelines and governance rules for Amplifier Edition.

• Return to DAO for approval of workflow and fee/subscription model.

Resources Needed

• Developer and technical staff for API integration and federation.

• Security & privacy audit for profile linking.

• Minimal storage and server resources for imported content.

Timeline / Milestones

• Formation of Working Group – TBD

• Research & Member Feedback – TBD

• Draft Implementation Plan – TBD

• DAO Ratification Vote – TBD

Deliverables

Proposal ID: 0000003

Submitted By: Nick Milburn

Date Submitted: 2025-10-07

Category: Membership / Platform Features

Summary: Define the process, permissions, and benefits for Materializer Edition accounts, enabling creators and organizations to operate sustainable creative and professional practices within the Refugia ecosystem. Members can manage storefronts, commissions, workshops, and cooperative project, all integrated into a transparent, ethical infrastructure that supports mutual aid and creative independence.

User Stories

• Creators want to monetize their work directly within Refugia without relying on external platforms.

• Organizations wish to coordinate cooperative projects, workshops, and services in a fully federated environment.

• Communities benefit from the availability of ethically managed services and creative offerings.

• Members want tools to translate participation and collaboration into sustainable livelihoods.

Objectives

• Materializer Edition provides all Pseudonymous and Verified Edition features.

• Enables monetization and management of creative and professional projects directly within Refugia.

• Supports cooperative commerce, community workshops, and service offerings in a transparent and federated system.

• Encourages sustainable participation and mutual aid while preserving creative independence.

Potential Approaches

• Storefront Setup: Provide secure, federated tools for members to sell goods, offer services, and host workshops.

• Commission & Project Management Tools to coordinate individual and cooperative projects with accountability and transparency.

• Payment Integration: Support for cooperative-compatible payment and revenue-sharing mechanisms.

• Community Governance Integration: Participation in DAO-driven moderation, curation, and project oversight.

Open Questions

• What subscription or fee structure (e.g., $20/month) optimally balances accessibility with sustainability ?

• Should there be limits on the types or volume of monetized offerings per member?

• How will escrow, dispute resolution, and cooperative revenue-sharing be implemented?

• What permissions or privileges are granted in governance or moderation to Materializer Edition members?

Proposed Next Steps

• Form Materializer Working Group.

• Define technical workflow for storefronts, project management, and monetization tools.

• Draft user guidelines, governance policies, and revenue-sharing models.

• Return to DAO for ratification of workflow, permissions, and subscription/fee model.

Resources Needed

• Developer and technical staff for platform features, payment integration, and federation support.

• Security, privacy, and payment compliance audit.

• Storage and server resources for content, project data, and media hosting.

Timeline / Milestones

• Formation of Working Group – [TBD]

• Research & Member Feedback – [TBD]

• Draft Implementation Plan – [TBD]

• DAO Ratification Vote – [TBD]

Deliverables

• Verified Edition governance rules and criteria

• Verification workflow & technical implementation plan

• Privacy policy for identity data

• DAO-approved operational procedures for verification

• Updates to DAO Constitution, as required

Proposal ID: 0000004

Submitted By: Nick Milburn

Date Submitted: 2025-10-07

Category: Platform Governance / Moderation

Summary: Define structured moderation policies, processes, and mechanisms for the Refugia Social Network. Establish four distinct “jury” pathways corresponding to account levels, Pseudonymous, Verified, Amplifier, and Materializer, ensuring that moderation and appeals are handled by peers of equal or higher status. This structure balances fairness, accountability, and transparency while respecting the hierarchical privileges of each edition.

User Stories

• Members want clear and transparent processes for resolving conflicts and violations.

• Verified, Amplifier, and Materializer accounts require peer-level moderation to maintain trust and accountability.

• Communities benefit from predictable, fair, and tiered moderation processes that scale with user engagement.

• The DAO wants to maintain transparency, oversight, and alignment with cooperative principles.

Objectives

• Implement tiered moderation systems that match the privileges and responsibilities of each account level.

• Define processes for initial review, trial, and appeals at each tier.

• Ensure that peer juries are composed of members at the same or higher account level.

• Integrate moderation outcomes into the DAO governance framework for oversight and transparency.

Potential Approaches

• Jury-Based Trials:  Peers at the same or higher account level review alleged violations.

• Moderator-Led Trials: For lower-tier accounts or minor infractions, staff moderators may adjudicate directly.

• Appeal Mechanisms:

  • Pseudonymous accounts may appeal to Verified, Amplifier, or Materializer peers.

  • Verified accounts may appeal to Amplifier or Materializer peers.

  • Amplifier accounts may appeal to Materializer peers.

  • Materializer accounts may appeal to the named stewards of the DAO.

• Documentation & Transparency Record all decisions, rationales, and appeals in a verifiable, auditable ledger accessible to members.

Open Questions

• How should severity of infractions influence whether jury or moderator trials are used?

• What thresholds of peer agreement constitute a verdict?

• How do we integrate automated notifications and timelines for appeals?

• Should certain account tiers have specific limits or privileges in raising appeals?

• How do we protect anonymity and privacy while maintaining peer accountability?

• How should we handle frivolous moderation requests?

Proposed Next Steps

• Form Moderation Working Group with representatives from each account tier.

• Define technical workflow for jury trials, moderator interventions, and appeal escalations.

• Draft detailed policy documentation, including timelines, thresholds, and reporting requirements.

• Return to DAO for ratification of moderation processes, jury composition rules, and appeal mechanisms.

Resources Needed

• Legal and governance expertise to ensure compliance and fairness.

• Developers for implementing moderation tools, tracking, and appeal mechanisms.

• Storage and logging infrastructure for auditable records of moderation activity.

• Training and onboarding materials for peer jurors and moderators.

Timeline / Milestones

• Formation of Moderation Working Group – [TBD]

• Research & Member Feedback – [TBD]

• Draft Policy & Technical Implementation Plan – [TBD]

• DAO Ratification Vote – [TDB]

Deliverables