> For the complete documentation index, see [llms.txt](https://gilmour.online/compsci/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gilmour.online/compsci/archives/vanek-archives/archives-art-i/lesson-9-the-project-putting-it-all-together.md).

# Lesson 9: The Project - Putting it all together

We will be creating a finished digital sculpture using blender. This will take the skills you learned on the animal sculpture and allow you to think about theme and composition as well as detail and process.

The sculpture must:

* have multiple objects (characters, set pieces, etc).
* capture the theme of **balance**.
* have good composition from every angle of the sculpture (except the bottom)
* use good detailing, especially in places of focus.
* be fully painted.
* be placed on a base.

This will be a multi-class project. For today’s class, I want to to generate 10 idea sketches. Take a picture of the sketches, open them on a computer and walk me through your ideas with a screencast.


---

# 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://gilmour.online/compsci/archives/vanek-archives/archives-art-i/lesson-9-the-project-putting-it-all-together.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.