# Advice Process

### About

The Advice Process enriches decision making and is a great companion of Do-ocracy. Community members are encouraged to take initiative anytime a problem or opportunity is identified. Using the Advice Process is easy and consists of identifying who are the experts or the people who will be affected by what is being proposed, directly requesting their advice and incorporating their feedback where it's appropriate according to the proponents discernment.&#x20;

### **Advice Process Main Actions** &#x20;

* Request advice in the Advice Process Forum section
* Request Advice during a working group call&#x20;
* Request Advice on Github issues
* Tag experts and individuals that are or will be affected by the proposal &#x20;
* Add comments and replies to the posts&#x20;
* Add comments and suggestions to documents&#x20;
* Incorporate feedback based on your discernment if you are the proponent&#x20;
* Provide constructive feedback if you are an advisor&#x20;
* Once the Advice Process is completed, the proponent can move the proposal to a voting category in the forum if needed.&#x20;
* Community members can guide new members to the Advice Process.&#x20;

**Is this action or outcome required?**&#x20;

* The Advice process is optional, but its use is recommended by the community.&#x20;
* We value people’s time and attention, be mindful when tagging individuals to give advice to a proposal.&#x20;
* The advice to a proposal should be respectful and based on constructive feedback rather than criticism.&#x20;

**Is this action or outcome discouraged?**&#x20;

* Violating the general code of conduct&#x20;
* Criticizing a proposal based on personal differences and/or conflict.&#x20;


---

# 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://token-engineering-commons.gitbook.io/tec-handbook/tec-agreements-1/collective-agreements/advice-process.md?ask=<question>
```

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.
