> 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/multi-stack-assembly.md).
# Multi-Stack Assembly
## Step 1
Align the pin on the Single slice with the matching pocket on the Double 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.
{% hint style="info" %}
A piece of 1/2" OD Hex can be used to line up the parts during assembly.
{% endhint %}
## Step 2
Repeat the process from the previous step with a Double slice. This process can be repeated for as many Double slices as desired.
{% hint style="info" %}
For multi stack assemblies, the screws will all be facing the same direction if screws are used. Screws can be omitted if the slices are constrained by collars or snap rings.
{% endhint %}
## Step 3
After adding as many Double slices as desired, add the final Single slice to the outside. Install the final set of screws, if screws are to be used.
{% hint style="info" %}
For multi stack assemblies, the screws will all be facing the same direction if screws are used. Screws are not included and can be omitted if the slices are constrained by collars or snap rings.
{% 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/multi-stack-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.
