Update Project System.md

[pmoncada]

Note

Overhauls Project System to v8 with quarterly proposal/voting flow, updated roles/responsibilities, revised rewards calculation/payouts, and expanded FAQs.

• Docs/Governance:
  • Update Project System.md to v8.0 with revised terminology (e.g., Executive Branch Leads) and clearer mission phrasing.
• Proposal & Voting Process:
  • Introduce quarterly deadlines: submission by second Thursday; Senate review; townhall presentation; Member House vote with funding selection rules and 1/5 budget cap per proposal; 3/4 quarterly budget cap enforcement.
• Project Start & Operations:
  • Clarify payment streaming options for upfront payments.
  • Shift to monthly progress updates; require weekly townhall attendance with 5% penalty per miss; rename contributor update channel.
• Completion:
  • Add Executive Branch Leads review/grade of final reports; successful leads may join Senate for 6 months.
• Quarterly Rewards:
  • ETH reward now 5% of NMA minus total project budgets (excl. Executive Branch Budget); clarify vMOONEY geometric series formula.
  • Run rewards script per project; remove contributor-level reward formula; send ETH rewards to project multisig; clarify vMOONEY vesting.
• FAQs:
  • Add/clarify: contributor payments must be streamed (recommend llamapay); budget limits; multi-quarter milestones; DAO-created multisigs; amendment authority moved to Executive Branch Leads.

^{Written by Cursor Bugbot for commit 160582b. This will update automatically on new commits. Configure here.}

[cursor]

This is the final PR Bugbot will review for you during this billing cycle

Your free Bugbot reviews will reset on December 17

Details

You are on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle.

To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.

[jaderiverstokes]

Love the proposal. We should definitely be switching things up and seeing what works best. Whether this setup is successful or not is a matter of trying it out and getting some data. So I think we prioritize simplicity so that we feel liberated to run experiments.

I think the opening paragraph is pretty clear on the goal for projects:
"MoonDAO Projects are goal-oriented teams working on mission-aligned objectives. This document provides the framework to fund the team, support their progress, align their interests with the DAO, and provide retroactive incentives for projects that get us one step closer to a permanent human presence on the Moon."

However I think there's a lot of room for interpretation as to which projects support the mission, and how we determine if they are successful. Maybe we could make it more concrete with metrics. For example, we make a rubric and score each project across categories on a scale from 1-10. Categories could be: ROI, initiative, innovation, reach, etc. Without some sort of definite target, I fear that each project stays isolated. Maybe individually they look like they are mission focused, but after a long period of time we find we are no closer to our goal.

Overall tho, I think the update is good to go as is, just some thoughts on other additions.

[pmoncada]

Good thoughts Jade - maybe we could incorporate the rubric in the Senate review. We used to have a rubric, but ultimately people didn't really spend the time to fill it out. Although now with the separate Senate meeting it might be worth bringing that back in, that rubric can be more of an "implementation detail" though that doesn't need to live in this doc.