Design proposal. This page describes how changes to programme rules and economic policy could be proposed, reviewed, and put into effect.
Scope and Authority
A proposal identifies the rule being changed, why the change is useful, and which participants, funds, or activities it would affect. The programme’s terms would define who can submit a proposal, who makes the decision, and who is authorised to carry it out. Different matters may involve different responsibilities. A token holding alone does not establish decision-making authority across RNDRNTWRK. For a programme using voting, the rules would explain eligibility, how votes are weighted, quorum, the decision threshold, and how abstentions are counted.Policy Topics
The documented design uses four references to organise proposed changes. These names describe policy topics, not a deployed contract or interface.
A proposal should show the existing rule alongside the requested change, including its effect on costs, agreed payments, committed funds, and unfinished activity.
Proposal Lifecycle
1
Describe the change
Identify the programme and policy topic. Set out the requested change, its purpose, the affected participants and resources, and the information needed to assess its effect.
2
Review and decide
Follow the programme’s stated decision rules. A voting process would record the eligible participation, vote weights, quorum, and result, including yes, no, and abstain responses.
3
Prepare the change
Identify who would carry out the decision and when it would take effect. The rules would explain any delay, pause condition, or recovery action, and who may use those controls.
4
Record what took effect
Connect the decision to the resulting policy version, effective date, and affected records. Distinguish an approved proposal from a change that has actually been applied.