> For the complete documentation index, see [llms.txt](https://docs.wcproducts.com/welcome/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wcproducts.com/welcome/system-and-structure/polycord-pulleys/assembly-instructions/getting-started/double-pulley-assembly.md).
# Double Pulley Assembly
Align the pin on the Single slice with the matching pocket on the Middle slice. Install the desired amount of #2-28 screws to hold the pulley slices together. Be sure to tighten the screws fully. There should be no gap between the pulleys when they are assembled.
For the double pulleys, the screws will need to come from the inside of the pulley stack into the Single slice. For the final slice, the screw goes from the Single slice into the Double slice. This can be seen in the image below.
{% hint style="info" %}
Screws can be omitted if used with the 7/8” long VersaRoller insert or the slices are constrained by collars or snap rings.
{% endhint %}
{% hint style="info" %}
A piece of 1/2" OD Hex can be used to line up the parts during assembly.
{% endhint %}
---
# 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://docs.wcproducts.com/welcome/system-and-structure/polycord-pulleys/assembly-instructions/getting-started/double-pulley-assembly.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.
