# Page 4 ### Circle Which circle(s) owns this role? Every role assignment is rooted in only one Circle so when making a role proposal keep this in mind and articulate what ## Role Name Every role has a name. This is simply a pointer to help others know what the role is accountable for. Nobody can deduct any meaning from a name or hold you accountable for anything based on the name of a role. ### Purpose Though a purpose is not mandatory, it is highly recommended to add it. It is the WHY of a role. It should describe which part of the Circle Purpose this role is here to manifest. ### Accountabilities What can this role be held accountable for? What ongong value should this role provide to the circle and the organisation? These are formulated as ongoing and should start with a verb ending in ...ing (eg: Designing..., Coding...., Publishing...). Interpreting and translating an accountability to work should be easy. ### Domains Domains describe a property right this role is the owner of. This means by definition adding a domain introduces bureaucracy as any other role that wishes to interact with that domain will need to ask for permission from this role. ### Compensation Each role will be compensated at one of N predefined "Salary Bands", or unique salaries (depending on the DHO). #### Role submitted by \_\_\_\_ of \_\_\_\_\_ --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://explore.joinseeds.earth/libraries-and-templates/role-templates-and-library/catalysing-and-connecting/page-4.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.