> For the complete documentation index, see [llms.txt](https://docs.creativeconners.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.creativeconners.com/docs/technical-support/tech-tips/deck-winch-connection.md).

# How A Deck Wagon Attaches To A Winch System

## The Pieces

This first image has the side frame removed from the wagon, and the deck track lid removed from the section where the dog is, so you can see all the pieces that are typically covered up.

The knife goes through the scenery deck, through the knife receiver (that just gives it more rigidity to the scenery than just going through the scenery deck), then into the dog.

The dog has the wire rope secured to it (we feed all the way through and then use screws to secure it in place), which allows the dog (and knife, and thus the scenery) to move with it.

![Deck wagon with the side frame removed](https://3040525219-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MhFI6SSKpm8M7EkrYqp%2Fuploads%2Fgit-blob-4b8e81798d44cb5cb006dfd2347f711d3ecbe7ed%2FDeck_track_with_numbers.png?alt=media)

1. Knife
2. Knife Receiver
3. Dog
4. Deck Wagon
5. Deck Track

## A Simplified View

Here's the other side that shows the wire rope path. Note how it bends around where the knife goes in.

![Basic deck wagon with the kinfe, receiver and dog isolated from the surrounding track](https://3040525219-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MhFI6SSKpm8M7EkrYqp%2Fuploads%2Fgit-blob-a6f34e2212cf18a5c25206abbf8beea4f6992f03%2Fdeck_dog_wagon_knife.png?alt=media)

Here you can see where the knife goes through the top of the deck wagon, through the knife receiver, and into the dog.

You can also see the 4x holes on top where the set screws tighten down onto the wire rope.

![Basic deck wagon with the kinfe receiver and deck dog, showing the slot in the wagon where the knife would go](https://3040525219-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MhFI6SSKpm8M7EkrYqp%2Fuploads%2Fgit-blob-e72226a96e652f29d511faccb9117d3caf421165%2Fdeck_dog_wagon_no_knife.png?alt=media)


---

# 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.creativeconners.com/docs/technical-support/tech-tips/deck-winch-connection.md?ask=<question>&goal=<user_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.