|
37 | 37 | </a> |
38 | 38 | </p> |
39 | 39 |
|
40 | | -> **OpenAI Build Week 2026:** Posecode existed before the hackathon. During Build Week, the project is being meaningfully extended with a GPT-5.6-powered biomechanical Physics Critic and an end-to-end Codex-built agent workflow. The sections below clearly distinguish previous work from new hackathon work. |
| 40 | +--- |
| 41 | + |
| 42 | +## Why Posecode? |
| 43 | + |
| 44 | +Ask an LLM to explain physical movement and it usually returns unstructured prose or a static diagram. |
| 45 | + |
41 | 46 |
|
42 | 47 | <p align="center"> |
43 | 48 | <img |
|
57 | 62 | </sub> |
58 | 63 | </p> |
59 | 64 |
|
| 65 | +For example: |
| 66 | + |
| 67 | +> Bend your knees, move your hips backward, and keep your chest upright. |
| 68 | +
|
| 69 | +A human may understand that instruction, but a renderer cannot reliably determine: |
| 70 | + |
| 71 | +- which joints should move, |
| 72 | +- by how many degrees, |
| 73 | +- in which coordinate frame, |
| 74 | +- over what duration, |
| 75 | +- in what sequence, |
| 76 | +- or within which physical limits. |
| 77 | + |
| 78 | +Large language models can often reason about the components of human movement, but they lack a standardized syntax for expressing that reasoning in a renderable and testable form. |
| 79 | + |
| 80 | +Posecode provides that missing representation. |
| 81 | + |
| 82 | +### See Posecode in 28 seconds |
| 83 | + |
| 84 | +From an LLM prompt to editable Posecode, validated 3D rendering, MCP tools, |
| 85 | +and a one-script web embed. |
| 86 | + |
| 87 | +<p align="center"> |
| 88 | + <a href="docs/launch-media/posecode-cut2-builder-16x9.mp4"> |
| 89 | + <img |
| 90 | + src="docs/launch-media/posecode-cut2-payoff.png" |
| 91 | + width="800" |
| 92 | + alt="Watch the 28-second Posecode builder demo" |
| 93 | + /> |
| 94 | + </a> |
| 95 | +</p> |
| 96 | + |
| 97 | +<p align="center"> |
| 98 | + <a href="docs/launch-media/posecode-cut2-builder-16x9.mp4"><b>▶ Watch the 28-second builder demo</b></a> |
| 99 | + <br /> |
| 100 | + <sub>Plain text in. Smooth, programmable 3D motion out.</sub> |
| 101 | +</p> |
| 102 | + |
| 103 | +### Movement examples |
| 104 | + |
60 | 105 | <table align="center"> |
61 | 106 | <tr> |
62 | 107 | <td align="center"> |
|
79 | 124 |
|
80 | 125 | --- |
81 | 126 |
|
82 | | -## OpenAI Build Week Extension |
83 | | - |
84 | | -### What existed before July 13, 2026 |
85 | | - |
86 | | -Before OpenAI Build Week, Posecode already included: |
87 | | - |
88 | | -- the core `.posecode` domain-specific language, |
89 | | -- a parser and intermediate motion representation, |
90 | | -- basic range-of-motion validation, |
91 | | -- a Three.js/WebGL renderer, |
92 | | -- forward kinematics, |
93 | | -- basic inverse-kinematics and ground-lock behavior, |
94 | | -- a browser playground, |
95 | | -- example movement files, |
96 | | -- shareable Posecode links, |
97 | | -- and an MCP server foundation. |
98 | | - |
99 | | -This original version was developed primarily with **Claude** as an AI-assisted engineering tool. |
100 | | - |
101 | | -That prior work provides the foundation for the project, but it is not presented as the new hackathon contribution. |
102 | | - |
103 | | -### What is being added during Build Week |
104 | | - |
105 | | -During the July 13–21 Build Week submission period, Posecode is being meaningfully extended with: |
106 | | - |
107 | | -1. **GPT-5.6 Physics Critic** |
108 | | -2. **Biomechanical fidelity scorecard** |
109 | | -3. **Natural-language-to-motion agent workflow** |
110 | | -4. **Interactive generation and critique experience** |
111 | | -5. **Codex-built tests, tooling, and renderer improvements** |
112 | | - |
113 | | -The new workflow allows a user to describe a movement in ordinary language, generate structured Posecode, validate it deterministically, and receive a detailed GPT-5.6 critique explaining biomechanical or spatial problems. |
114 | | - |
115 | | -### Build Week feature status |
116 | | - |
117 | | -- [ ] GPT-5.6 movement generation |
118 | | -- [ ] GPT-5.6 Physics Critic |
119 | | -- [ ] Structured fidelity-score response |
120 | | -- [ ] Critique panel in the playground |
121 | | -- [ ] Generate → validate → critique → revise loop |
122 | | -- [ ] MCP tools for critique and revision |
123 | | -- [ ] Automated tests for the new workflow |
124 | | -- [ ] Demo-ready example movements |
125 | | -- [ ] Build Week commit links added below |
126 | | -- [ ] Codex session ID added below |
127 | | - |
128 | | ---- |
129 | | - |
130 | | -## Why Posecode? |
131 | | - |
132 | | -Ask an LLM to explain physical movement and it usually returns unstructured prose or a static diagram. |
133 | | - |
134 | | -For example: |
135 | | - |
136 | | -> Bend your knees, move your hips backward, and keep your chest upright. |
137 | | -
|
138 | | -A human may understand that instruction, but a renderer cannot reliably determine: |
139 | | - |
140 | | -- which joints should move, |
141 | | -- by how many degrees, |
142 | | -- in which coordinate frame, |
143 | | -- over what duration, |
144 | | -- in what sequence, |
145 | | -- or within which physical limits. |
146 | | - |
147 | | -Large language models can often reason about the components of human movement, but they lack a standardized syntax for expressing that reasoning in a renderable and testable form. |
148 | | - |
149 | | -Posecode provides that missing representation. |
150 | | - |
151 | | ---- |
152 | | - |
153 | 127 | ## Why Not Diffusion Text-to-Motion? |
154 | 128 |
|
155 | 129 | Neural text-to-motion systems can generate impressive movement, but they introduce problems for lightweight, programmable applications. |
@@ -305,37 +279,6 @@ npm run build |
305 | 279 |
|
306 | 280 | --- |
307 | 281 |
|
308 | | -## GPT-5.6 Configuration |
309 | | - |
310 | | -> Update these instructions to match the final implementation. |
311 | | -
|
312 | | -Create an environment file: |
313 | | - |
314 | | -```bash |
315 | | -cp .env.example .env |
316 | | -``` |
317 | | - |
318 | | -Add your OpenAI API key: |
319 | | - |
320 | | -```env |
321 | | -OPENAI_API_KEY=your_api_key_here |
322 | | -``` |
323 | | - |
324 | | -Optionally configure the model: |
325 | | - |
326 | | -```env |
327 | | -OPENAI_MODEL=gpt-5.6 |
328 | | -``` |
329 | | - |
330 | | -Start the application: |
331 | | - |
332 | | -```bash |
333 | | -npm run dev |
334 | | -``` |
335 | | - |
336 | | -Never commit API keys to the repository. |
337 | | - |
338 | | ---- |
339 | 282 |
|
340 | 283 | ## MCP Server |
341 | 284 |
|
@@ -716,6 +659,56 @@ Feedback and contributions are welcome. |
716 | 659 | --- |
717 | 660 |
|
718 | 661 |
|
| 662 | +> **OpenAI Build Week 2026:** Posecode existed before the hackathon. During Build Week, the project is being meaningfully extended with a GPT-5.6-powered biomechanical Physics Critic and an end-to-end Codex-built agent workflow. The sections below clearly distinguish previous work from new hackathon work. |
| 663 | +
|
| 664 | +--- |
| 665 | + |
| 666 | +## OpenAI Build Week Extension |
| 667 | + |
| 668 | +### What existed before July 13, 2026 |
| 669 | + |
| 670 | +Before OpenAI Build Week, Posecode already included: |
| 671 | + |
| 672 | +- the core `.posecode` domain-specific language, |
| 673 | +- a parser and intermediate motion representation, |
| 674 | +- basic range-of-motion validation, |
| 675 | +- a Three.js/WebGL renderer, |
| 676 | +- forward kinematics, |
| 677 | +- basic inverse-kinematics and ground-lock behavior, |
| 678 | +- a browser playground, |
| 679 | +- example movement files, |
| 680 | +- shareable Posecode links, |
| 681 | +- and an MCP server foundation. |
| 682 | + |
| 683 | +This original version was developed primarily with **Claude** as an AI-assisted engineering tool. |
| 684 | + |
| 685 | +That prior work provides the foundation for the project, but it is not presented as the new hackathon contribution. |
| 686 | + |
| 687 | +### What is being added during Build Week |
| 688 | + |
| 689 | +During the July 13–21 Build Week submission period, Posecode is being meaningfully extended with: |
| 690 | + |
| 691 | +1. **GPT-5.6 Physics Critic** |
| 692 | +2. **Biomechanical fidelity scorecard** |
| 693 | +3. **Natural-language-to-motion agent workflow** |
| 694 | +4. **Interactive generation and critique experience** |
| 695 | +5. **Codex-built tests, tooling, and renderer improvements** |
| 696 | + |
| 697 | +The new workflow allows a user to describe a movement in ordinary language, generate structured Posecode, validate it deterministically, and receive a detailed GPT-5.6 critique explaining biomechanical or spatial problems. |
| 698 | + |
| 699 | +### Build Week feature status |
| 700 | + |
| 701 | +- [ ] GPT-5.6 movement generation |
| 702 | +- [ ] GPT-5.6 Physics Critic |
| 703 | +- [ ] Structured fidelity-score response |
| 704 | +- [ ] Critique panel in the playground |
| 705 | +- [ ] Generate → validate → critique → revise loop |
| 706 | +- [ ] MCP tools for critique and revision |
| 707 | +- [ ] Automated tests for the new workflow |
| 708 | +- [ ] Demo-ready example movements |
| 709 | +- [ ] Build Week commit links added below |
| 710 | +- [ ] Codex session ID added below |
| 711 | + |
719 | 712 | --- |
720 | 713 |
|
721 | 714 | ## The Build Week Feature: Physics Critic |
|
0 commit comments