01
Section 5.7Budget Alignment & Limits
Flags if the USDT/RBNT split is missing, if USDT requested is over the 100,000 annual cap or RBNT requested is over the 10,000,000 pool set in Section 5.7, or if the justification field is empty.
TASK-25 Proposal Evaluation Framework
This page holds the Proposal Evaluation Framework rubric for Redbelly DAO Task Board TASK-25. It automates the DAO's already-ratified 11-criterion checklist.
The rubric is built from the three official sources below. Each link opens the ratified original in a new tab.
Section 01
How Pre-Screening Works
This framework automates the DAO's already-ratified 11-criterion Proposal Review Checklist (Snapshot proposal #7, adopted 6 October 2025). A proposal is checked against all 11 criteria. Each one returns pass or flag, with the specific reason and the Constitution or Code of Conduct section it cites.
Pre-screening is not a decision. It runs before Guild and High Council review, not instead of it. A flagged criterion means a reviewer should look closer, not that the proposal is rejected.
Section 02
Known Discrepancies
Three working groups vs. the retired pod structure
Criterion 3 checks alignment with one of three working groups, Community, Marketing, Developers-Builders. Constitution v1.2 named five pods for this. The DAO Guild Structure Consolidation vote, passed 20 September 2025, merged two of those five into the other three. Constitution v1.3 then removed the pod structure from the Constitution entirely. The three groups the checklist names are still the ones in practice, but nothing in the current Constitution defines or anchors them. A flag on Criterion 3 is expected for any submission today, not a sign of a broken tool.
Criterion 11 has no ratified flag condition
Every other criterion in the ratified checklist pairs a pass condition with an explicit flag rule. Community Involvement does not. Any flag raised here is labelled informational only and never marks a proposal as failing pre-screening on its own.
Section 03
The 11 Criteria
Showing all 11. Each card is what the pre-screening tool checks and cites.
02
Section 6Payment & Payout Structure
Flags if Upfront is selected with no justification, or the milestone list is empty.
03
No Constitution anchor. Constitution v1.3 retired the pod structure entirely. See Known Discrepancies.Strategic Fit
Flags if the alignment explanation is empty, or the pod selected is not one of the three named in the ratified text: Community, Marketing, Developers-Builders.
04
No Constitution anchorFeasibility & Timeline
Flags if the timeline is empty or the resourcing note is empty.
05
Section 5.6Oversight & Accountability
Flags if the reviewer field or the monthly update plan is empty.
06
No Constitution anchorImpact & Measurement
Flags if KPIs are empty, or only short-term value is described with nothing under long-term or community value.
07
No Constitution anchorRisk & Mitigation
Flags if the risk list is empty or any risk has no paired mitigation.
08
No Constitution anchorCo-Funding & Leverage
Flags, informationally and non-blocking, if left empty.
09
Section 4Contribution Equity
Flags if one contributor's share of payout is disproportionate, or a listed contributor already holds another paid DAO role with no justification given.
10
Code of Conduct v1.0Compliance & Ethical Standards
Flags if the disclosure field is empty or the Code of Conduct acknowledgement is unchecked.
11
Section 7Community Involvement
Flags only if the evidence field is completely empty. The ratified checklist gives this criterion no flag condition at all, so this flag is always informational, never a failure.
Section 04
Full Report
The complete rubric document, embedded below.
Section 05
Run Pre-Screening
Fill in a proposal below, or load a real one from the archive. Pre-screening runs entirely in this page and returns a result for all 11 criteria, no submission is sent anywhere.
Section 06
Documentation
How Pre-Screening Works
Pre-screening checks a submitted proposal against the DAO's 11 ratified criteria and returns a pass or flag for each one, citing the specific Constitution or Code of Conduct section behind it. It runs entirely client-side in this page, nothing is stored or sent anywhere. It is not a decision. It runs before Guild and High Council review, not instead of it. A flag means a reviewer should look closer, not that a proposal is rejected. Criteria 08 and 11 are informational only and never contribute to a fail state, because the ratified checklist gives them no flag condition.
Proposals and Amendments That Already Supersede Prior Text
Constitution v1.3 is now the governing text, replacing v1.2. Every section number in this framework has been updated to match. The clearest change: Section 3, Working Groups, is gone from v1.3. The DAO Guild Structure Consolidation vote (20 September 2025) had already merged five pods into three; v1.3 completed that by removing the section outright. Criterion 3 of the ratified checklist still names three working groups by text, so pre-screening still checks against them, it just has no Constitution section left to cite.
Updating the Mapping When the Constitution Is Amended
When Constitution v1.3 is re-ratified or superseded, check the 11 criteria against the new text in this order: Section 5.7 (Budget Alignment), Section 6 (Payment and Payout), no anchor (Strategic Fit), Section 5.6 (Oversight and Accountability), Section 4 (Contribution Equity), Section 7 (Community Involvement), and the standalone Code of Conduct v1.0 (Compliance and Ethical Standards). The four criteria with no Constitution anchor, Feasibility and Timeline, Impact and Measurement, Risk and Mitigation, and Co-Funding and Leverage, stay unanchored unless a new provision explicitly covers them. Update both the rubric document and the citation links in Section 03 and Section 05 to point at the new section numbers. If a later Snapshot proposal supersedes a section without a full re-ratification, follow the pattern already used in Section 02, Known Discrepancies: keep citing the Constitution section but add a note naming the superseding proposal as controlling.
Day-to-Day Operation for Council Members
No technical background required. To pre-screen a submitted proposal, open this page, scroll to Section 05, and either fill in the 11 groups by hand from the submission or use the Load Proposal buttons to see a worked example first. Click Run Pre-Screening. Read the summary line for how many of 11 passed, then read each flagged row for its one-line reason and its cited Constitution or Code of Conduct section. A flag is a prompt to look closer during review, not an automatic rejection. Criteria marked Informational never block a proposal on their own. The final accept or reject decision stays with the council.