Open questions

These are recognized problems. Missionism v0.1 does not claim to have solved them. Prefer evidence and experiments over premature doctrine.

Missionism Protocol v0.1 · Draft · September 2026 · source: spec/RIGHTS_AND_CONSTRAINTS.md

Active research

  1. How should missions measure value?Open
  2. How should Mission Units (Mishys product language) relate to MCU (protocol language)?Open
  3. How much ownership should past contributors retain?Open
  4. Can ownership cascade across generations?Open
  5. How should child missions participate in parent governance?Open
  6. Should missions receive equal representation or contribution-weighted representation?Open
  7. How do we prevent large missions from capturing federations?Open
  8. How do we prevent thousands of tiny missions from overwhelming governance?Open
  9. How should trademarks and certification work with open-source forks?Open
  10. What rights should always remain individual rather than contribution-weighted?Open
  11. How should missions resolve disagreement?Open
  12. When should a mission fork instead of voting?Open
  13. Who may set reference values and multipliers without recreating founder capture (the oracle problem)?Open
  14. Can Missionism measure whether a mechanism removes more coordination complexity than it adds—without recreating the bureaucracy it claims to compress?Proposed
  15. How do we keep mission objectives legible enough to guide ownership without collapsing into thirty ambiguous scores worse than a single financial signal?Open

Where ideas go

Preferred directions that are not yet canonical belong in docs/proposals/. Things we want implementations to test belong in docs/experiments/. Solved items move into spec/ with a /changes entry—not silently into website copy.