> For the complete documentation index, see [llms.txt](https://pa-vpa-operations-treasury.gitbook.io/vpa-process-working-group/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://pa-vpa-operations-treasury.gitbook.io/vpa-process-working-group/on-boarding-welcome/code-of-conduct.md).

# Code of Conduct

#### For the current Code of Conduct (CoC) please see Chapter 8.1  in the [Governance Framework for PA/(v)PA Operations Treasury](https://docs.google.com/document/d/1bRFsYYbDc52U610XGgg2h-dBFdn2MhgvlXwHtElq3_0/edit#) document:

{% embed url="<https://docs.google.com/document/d/1bRFsYYbDc52U610XGgg2h-dBFdn2MhgvlXwHtElq3_0/edit#heading=h.3moreczex8qp>" %}

### Code of Conduct (CoC) as a *Living Document*

To further develop the Code of Conduct within the context of the vPA process it was proposed to do the following:

> Using a Pol.is survey to gather what statements should be added to the Code of Conduct of the Veteran PA Working Group. \
> Those statements will be used to fashion rules from in an ad hoc fashion.&#x20;
>
> **Ad hoc fashion?** If a Statement in the CoC is being ignored, then from that case a rule could be extrapolated. In case a rule hasn't been broken for a long time, it might is superfluous and can be deleted; the statement remains for another incident to pop up and create a new rule that might fit better for that timespace context. This helps with keeping the CoC lean.
>
> **Please use the following format**: *We value \<f> over \<i>*

#### *->* [Pol.is survey](https://pol.is/54k5j6febf)