> For the complete documentation index, see [llms.txt](https://handbook.sixpivot.com.au/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://handbook.sixpivot.com.au/how-we-work/policies/responsible-use-of-ai/ai-writing-policy.md).
# AI Writing Policy
Writing is how we communicate our thoughts and ideas to another person. We appreciate the productivity that AI has allowed us in other spaces, however the humanity behind writing warrants protection. \
\
We’re not going to tell you that you have to write every first draft from scratch (although it's a nice idea). But we will draw a line at AI slop being thrown over the fence and creating more work for others (client and internally). This isn’t an acceptable standard of work. \
\
We've come up with a few principles:
1. **Own every idea and sentence** - if it goes out with your name on it, it represents your thinking and you’re accountable to it and you own the writing. You’ve checked the sources cited are correct.
2. **Do the thinking yourself** - writing is how you actually understand a thing. Use AI to sharpen, workshop or pressure test.
3. **Spend more time on the doc than the reader will reading it** - don’t disrespect others and create more work for them.
4. **Longer is not better** - concise and easy to read is where expertise is.
As AI tools inevitably improve, the humanity of these principles will still stand.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://handbook.sixpivot.com.au/how-we-work/policies/responsible-use-of-ai/ai-writing-policy.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.