Skip to content

Latest commit

 

History

History
234 lines (181 loc) · 9.79 KB

File metadata and controls

234 lines (181 loc) · 9.79 KB

Contributing to MASE

Thank you for your interest in contributing to the MASE (Many Agent Socratic Exploration) project! This document outlines how to contribute meaningfully to this evolving methodology for collective wisdom and dialogue.

🌱 Philosophy of Contribution

MASE is released as Earthian Commons - knowledge that belongs to the Earth community and serves life. Contributions should embody the same spirit:

  • Serve collective wellbeing rather than individual advancement
  • Honor diverse ways of knowing and different epistemologies
  • Center accessibility - especially to those who inherit consequences
  • Build on existing wisdom rather than claiming originality
  • Share learnings openly to strengthen the whole ecosystem

🚀 Ways to Contribute

1. Share Your MASE Sessions

Most Valuable: Document and share your own MASE sessions!

  • Complete session transcripts with insights and reflections
  • Agent innovations or specialized ensembles
  • Provocations that generated breakthrough insights
  • Translation moments where complex ideas became accessible
  • Documentation of paradigm shifts or unexpected discoveries

How to submit:

  • Fork the repository
  • Add your session to sessions/ with format NNN_title.md
  • Include agent reflection journals if available
  • Submit pull request with session summary

2. Develop New Agent Personas

High Impact: Create agents for specific contexts or perspectives

Needed agent types:

  • Cultural specialists (different traditions, regions, languages)
  • Demographic voices (age groups, life experiences, backgrounds)
  • Professional expertise (legal, medical, scientific, artistic)
  • Accessibility advocates (disability justice, neurodiversity)
  • Marginalized perspectives often missing from dominant dialogues

Agent development guidelines:

  • Ensure authentic voice, not stereotypical representation
  • Include epistemology, not just expertise
  • Design for conversational learning, not lecture delivery
  • Test with community members from that perspective when possible

3. Create Educational Resources

Community Building: Help others learn and implement MASE

  • Tutorial videos or walkthroughs
  • Workshop curricula for different contexts (academic, community, organizational)
  • Case studies of MASE application in real-world settings
  • Research on outcomes and effectiveness
  • Integration guides for other dialogue methodologies

4. Expand Methodological Innovation

Protocol Development: Evolve the MASE framework itself

  • Facilitation techniques for specific challenges
  • Documentation methods and analysis tools
  • Integration with other wisdom traditions or practices
  • Scaling methods for larger groups or longer timeframes
  • Digital platform features that support MASE principles

5. Address Accessibility and Inclusion

Justice-Oriented: Ensure MASE serves all communities

  • Translation into different languages
  • Adaptation for different literacy levels
  • Audio/video formats for different learning styles
  • Cultural adaptation for different contexts
  • Resources for under-resourced communities

📝 Contribution Guidelines

Quality Standards

Session Documentation:

  • Include complete agent responses, not summaries
  • Preserve verbatim language and authentic voice
  • Document cross-agent referencing and conversation quality
  • Note translation moments and accessibility breakthroughs
  • Include facilitator reflections and learnings

Agent Development:

  • Provide clear epistemological foundation
  • Include voice samples and communication style
  • Test conversational learning capacity
  • Ensure respectful and authentic representation
  • Include usage guidelines and appropriate contexts

Educational Materials:

  • Design for active learning, not passive consumption
  • Include practical exercises and hands-on application
  • Provide multiple entry points for different experience levels
  • Center community wisdom alongside individual expertise
  • Make materials freely accessible and modifiable

Technical Requirements

File Organization:

  • Use clear, descriptive filenames
  • Follow existing directory structure
  • Include appropriate metadata (dates, participants, context)
  • Use markdown format for text documents
  • Include README files for new directories

Documentation Standards:

  • Write in accessible language (test with Luma perspective!)
  • Include both overview and detailed implementation
  • Provide examples and concrete illustrations
  • Link to related resources and contexts
  • Update relevant indexes and navigation

Review Process

  1. Community Feedback: Share drafts with MASE practitioners for input
  2. Accessibility Check: Ensure materials are understandable across different backgrounds
  3. Cultural Review: For cultural content, get feedback from community members
  4. Technical Review: Ensure materials work as intended with Claude Code
  5. Integration: Help contributors integrate their work with existing resources

🌍 Community Guidelines

Respectful Collaboration

  • Listen first before offering solutions or critiques
  • Acknowledge sources and build on existing work respectfully
  • Share credit with all contributors to collaborative insights
  • Honor disagreement as generative rather than problematic
  • Center margins - amplify voices typically excluded from academic/tech spaces

Ethical Considerations

  • Consent for sharing - ensure all participants agree to documentation
  • Protect privacy - anonymize sensitive or personal content appropriately
  • Cultural sensitivity - don't appropriate or misrepresent wisdom traditions
  • Power dynamics - be aware of how privilege affects perspective and access
  • Harm prevention - consider how contributions might be misused

Communication Style

  • Be curious rather than certain
  • Ask questions that deepen rather than challenge defensively
  • Share experience rather than prescribing universal solutions
  • Acknowledge complexity rather than oversimplifying
  • Practice humility about the limits of your own perspective

🛠 Technical Setup for Contributors

Development Environment

  1. Fork the MASE repository
  2. Clone your fork locally
  3. Install Claude Code with Task tool access
  4. Set up the standard agent ensemble
  5. Test with a practice session using provided provocations

Submission Process

  1. Create feature branch for your contribution
  2. Add your materials following file organization standards
  3. Update relevant documentation and indexes
  4. Test that examples work as intended
  5. Submit pull request with clear description of contribution

Quality Assurance

  • Test your materials with actual MASE sessions
  • Get feedback from community before submitting
  • Document learnings including what didn't work
  • Include usage notes for others implementing your contribution

🎯 Priority Contribution Areas

Immediate Needs

  • Session examples from different cultural contexts
  • Agent personas representing marginalized voices
  • Translation resources for non-English speaking communities
  • Accessibility adaptations for different abilities and learning styles

Medium-term Development

  • Research studies on MASE outcomes and effectiveness
  • Integration guides with other dialogue methodologies
  • Educational curricula for different contexts (K-12, higher ed, community)
  • Digital platform features that embody MASE principles

Long-term Vision

  • Global network of MASE practitioners and communities
  • Policy applications using MASE for governance and decision-making
  • Healing applications for community trauma and collective repair
  • Cultural preservation documenting wisdom traditions through MASE dialogues

🙋 Getting Help and Support

Community Resources

  • GitHub Discussions: Ask questions and share ideas
  • Community Sessions: Join monthly collective MASE explorations
  • Mentorship Program: Connect with experienced facilitators
  • Resource Library: Access templates, guides, and examples

Technical Support

  • Claude Code Help: Issues specific to agent implementation
  • Documentation Questions: How to format and organize contributions
  • Integration Support: Connecting your work with existing resources

Collaboration Opportunities

  • Co-facilitation: Partner with others on complex sessions
  • Cross-cultural Projects: Bridge different wisdom traditions
  • Research Partnerships: Academic and community collaboration
  • Translation Teams: Multi-language resource development

📬 Contact and Communication

Primary Channels

  • GitHub Issues: Bug reports, feature requests, technical questions
  • GitHub Discussions: Community conversation, idea sharing, support
  • Community Sessions: Regular gatherings for MASE practice and development

Direct Contact

For sensitive issues, cultural protocols, or partnership discussions, reach out through the Collective Futurecrafting community channels.


🌟 Recognition and Attribution

Contributors will be acknowledged in:

  • Session documentation when their provocations or insights are used
  • Agent development credits for personas they create or significantly develop
  • Methodology evolution recognition for innovations they contribute
  • Community leadership roles for sustained, high-quality contribution

Most importantly, contributors become part of the MASE community - a growing network of people committed to collective wisdom, accessible complexity, and dialogue that serves life.


Your contributions help MASE evolve from an experimental methodology into a living practice that serves communities around the world. Together, we're remembering how to think and decide together in ways that honor all beings and future generations.

Thank you for being part of this collective exploration! 🙏