Skip to content
Baseworks KB

Keeping back foot in high-heel position — curated notes

Created 2026-04-12
Type curated-notes
Status reply-drafted
Tags primer-communitycurated-notesforumnathalie-dore

Persistent sidecar for the auto-synced topic at 2026-04-12-keeping-back-foot-in-high-heel-position. The forum content sync rewrites the topic file on every cycle, so anything that needs to survive — recommended tags, the draft reply text, working notes — lives here instead.

Topic context: Applied Practice Lab — Ascendant Torsion, Lesson 3.5. Nathalie asked about pelvis alignment and losing balance when the back foot is in high-heel position while leaning forward.

Section titled “Recommended tags for the topic”

Nathalie didn’t apply tags when she posted. The list below should be added directly on the BuddyBoss topic (topic-id 22196) so they persist through the sync. Copy-paste this comma-separated line into the BuddyBoss tag field:

Baseworks Movement Patterns, Intensity Modification, Distributed Activation, Forms, Proprioceptive Awareness, Gridlines & Symmetry, Adaptive Learning, Body Awareness, Spatial Awareness, Applied Practice Lab, Ascendant Torsion

From the Forum Tag Shortlist — these will auto-suggest as you type on BuddyBoss:

  • Baseworks Movement Patterns
  • Intensity Modification
  • Distributed Activation
  • Forms
  • Proprioceptive Awareness
  • Gridlines & Symmetry
  • Adaptive Learning
  • Body Awareness
  • Spatial Awareness

New tags — not yet on the shortlist. Type them out in full the first time and BuddyBoss will create them on the fly. Once created, they’ll auto-suggest for future posts:

  • Applied Practice Lab
  • Ascendant Torsion

The new tags add a form-specific cluster (Ascendant Torsion) and a practice-lab-specific cluster (Applied Practice Lab) so future questions about the same form or same lab can be grouped together. Worth eventually adding these to the Forum Tag Shortlist itself once you confirm you want them as permanent entries.

Draft reply (pastable markdown)

Section titled “Draft reply (pastable markdown)”

The full Patrick reply as drafted 2026-04-12, kept here as a persistent backup. Once the reply is actually posted on BuddyBoss and the sync regenerates the synced topic file, this draft and the synced version should match.

Hi Nathalie,


Yes, the pelvis should stay straight. The instability you're describing usually comes from a combination of the stance being a little too wide and the forward lean being a little too deep for the stabilizing patterns to catch up. A few things to work with.


**Narrow the stance and ease off the forward lean.** Start less deep than you think you need to. Pull back slightly on the angle you're leaning forward at, and keep the distance between the feet smaller. That gives you more control while you work on layering the other patterns into the form.


**Apply the patterns you already know.** The traction of the legs away from each other, and the drawing of the shoulders down, are what stabilize you at whatever depth you're in. They aren't separate from the form. They're how the form holds together. The deeper you go, the more you need them, so keep reapplying them as you settle in.


**Watch the front knee.** One thing we noticed with you in session: the front knee tends to travel a little too far forward. Keep it stacked over the ankle in the lunge. This is part of why we recommend not going so deep initially. Once the knee drifts past vertical, the geometry gets harder to hold.


**Feet hip-width apart as you tuck.** This is directly connected to keeping the pelvis uniform. If the feet drift out of hip-width, the pelvis loses its reference.


**Draw the extended leg hip slightly in.** One thing you can add: almost exaggerate the motion of the extended leg hip drawing in toward the bent knee, as a mild torsion. It's subtle, but it helps the pelvis hold its uniform position while you're working on everything else.


On the broader point, we'd really recommend revisiting this practice lab along with the prior ones. The form dynamics change from lab to lab, but the patterns are the same, and that reapplication across different forms is how the program is designed to be assimilated. As we've mentioned on the weekends and throughout the program communications, the in-person sessions are where we go through everything together and progressively close the gaps between your self-guided practice and the in-person Q&A. A lot of what the patterns do isn't obvious on a first encounter.


One thing worth adding, because it matters well beyond this specific question: we completely understand the desire to get it right, and we genuinely appreciate the care and motivation you're bringing to the practice. Not everything in the method is meant to be understood immediately, though. A big part of what we're introducing is a deconditioning of what normally feels habitual, including assumptions about what should or shouldn't feel correct in the early phases. Rather than trying to sort it all out up front, work through it as best you can and let the theory and the practical application start to correlate over time.


As linear as the rollout might feel at first, like any form of deep learning it's the reapplication of the approach that brings the most clarity to the outcomes. And with Baseworks specifically, that reapplication is closely interwoven with each person's circumstances: personal condition, lifestyle constraints, how the practice fits into a given week. That's why moderation is so central to the method. It's what keeps the work doable and manageable, so you can stay with it long enough for the reapplication to take effect.


One last note for everyone reading: when you post a question on the forum, please take a moment to refer to our [Forum Tag Shortlist](https://practice.baseworks.com/groups/primer-community/forum/discussion/forum-tag-shortlist-how-to-tag-your-forum-posts/) and apply the relevant tags to your post. It makes the forum much more searchable over time, and turns it into a real resource where anyone can click a tag on any post to surface related discussions on the same topic.


Patrick

Teaching frames extracted from the posted reply

Section titled “Teaching frames extracted from the posted reply”

Seeded 2026-04-22 as part of the backfill exception described in the Draft Response — Collaboration Protocol. These frames are extracted by Claude Code from Patrick’s posted reply, not captured as editorial deltas during drafting. They are retrievable as precedent but should be treated as observed patterns from the finished reply, not as corrections made during a drafting session.

1. Patterns are not additions to forms; they are what hold forms together. The traction of the legs away from each other and the drawing of the shoulders down are not separate from the form — they are how the form holds. The deeper the practitioner goes, the more the patterns are needed, not less. Reusable across any form-stability question.

2. Go less deep than you think. For Ascendant Torsion specifically, but broader as a principle: depth without patterns is unstable. The first corrective move when a participant reports instability in a lunge-like form is usually to narrow the stance and pull back on the lean. Depth comes after patterns are reliable, not before.

3. Stance width has a pelvic-reference function. Feet drifting out of hip-width costs the pelvis its geometry. This is why “feet hip-width apart as you tuck” is a specific geometric check, not a stylistic preference. The pelvis needs the reference lines the feet provide.

4. Knee over ankle as the geometric check. In a lunge, once the front knee drifts past vertical, the geometry becomes much harder to hold. This is a reusable diagnostic: when a pelvis or lunge feels unstable, check whether the front knee has traveled past the ankle.

5. Torsion as a stabilizing micro-action. Drawing the extended-leg hip slightly in toward the bent knee is a mild torsion that helps the pelvis hold its uniform position during forward lean. Subtle, but it earns its place. Reusable whenever a pelvis wants to tilt or twist under lean or load.

6. Reapplication across forms is the assimilation mechanism. The method works by repeating the same patterns across different forms. Forms differ, patterns are the same, and the exposure-across-contexts is how the program is designed to be internalized. When a participant asks about one form, the right answer often includes “revisit this along with the prior labs — the patterns repeat, and that is the point.”

7. Deconditioning of “what should feel correct” is part of the method. Early-phase uncertainty about whether something is being done right is expected and designed-for. The appropriate frame for a participant trying to sort it all out up front is: work through it as best you can and let theory and practical application correlate over time. Don’t promise clarity at the first encounter.

8. Moderation as methodological principle. What keeps the work doable and reapplication possible is moderation: not pushing depth or intensity beyond what the patterns can currently support. The method is designed for sustained engagement interwoven with the practitioner’s personal condition and life, not for maximal effort sessions. Moderation is not a softening of the practice; it is what makes the practice compound.

Notes

Section titled “Notes”
  • Reply written: 2026-04-12 in collaboration between Patrick and Claude Code on Patrick’s Mac.
  • Forum Tag Shortlist link: Points to the Primer Community version (posted 2026-04-12), not the earlier Winter cohort version at topic 21433.
  • Status: Draft complete. Awaiting Patrick’s post to BuddyBoss.
Section titled “Related”