> For the complete documentation index, see [llms.txt](https://www.isaacbowen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.isaacbowen.com/2025/07/25/gym.md).

# gym

today

15x of 3x hang power clean + 3 front squats

5x 95#\
5x 105#\
5x 115#

xxx

“are you sure? :)”

^ each time this is asked like this, with curiosity and a hint of playful daring, I think we flip to the other side of the looking glass

xx

ian: your pulling is turning into \[curls] and not \[elbows]

xx

I want to leave my shoulders and arms slack until the hip thrust

the vertical bar pull comes from the hinge opening, not from the hips pushing?

xx

I think this is helping: vertical pull via hinge opening, pushing the attachment point (shoulders) up, and the elbows fold out of the way

x sort of, failed the last hpc, didn’t get to the squats at all

ian: remember, bar wants to go vertical; your hips have a tendency to push forward **instead of jumping vertically**

I left my headphones off for too long, I just tipped over a dysregulation threshold


---

# 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://www.isaacbowen.com/2025/07/25/gym.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.
