Motivation(s) for this role

• We want open contribution, and one barrier to that is context - just knowing what the Unit needs and what skills would help. The radiator should facilitate finding tasks that can be opened up, and giving contributors the context about what they need to do
• We hear that a big problem in subDAO trust is that when a Unit is moving fast, doing updates that noone reads falls by the wayside, but then when something breaks, noone has context to fix it
• Some projects may need or want to protect client secrecy, and we don’t want a Unit to be incentivised to go against the RnDAO mission and vision of openness and contributing to shared knowledge.
• A lot of projects should end in a publication, but the people doing the research may not be good at doing the writing. A radiator would be there through the process, capturing info as it goes and maintaining context. They would be in the best position to either write or edit public-facing posts.

Role Attributes

• Purpose: the guiding question, purpose or reason for the Role or Units to exist. This is often defined as who+why (who is the unit serving and what needs or aspirations does it seek to address for them).
• Accountabilities: specific tasks or responsibilities for which the role is accountable.
• Domains: areas over which the role has exclusive decision-making authority.
• Permissions*: specific abilities the role has e.g. access rights to specific tools or domains, admin control of a tool, etc.*
• Success Criteria: Objectives, Metrics (KPIs), and or Targets (specific quantity within a metric or qualitative change within an objective that's aimed to attain or exceed).
• Agreements with other Roles and/or Units: by default, every role and Unit inherits RnDAO agreements, and every role also inherits any agreements from the Unit it belongs to. The Agreements fall within the following categories: