You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Expanded the README with details about the OpenAI Build Week 2026, including what existed before and what was added during the event. Removed the roadmap section and included evidence of pull requests related to the Build Week.
@@ -175,6 +175,136 @@ A `.posecode` file describes movement as timed phases with targeted joint action
175
175
176
176
---
177
177
178
+
179
+
180
+
> **OpenAI Build Week 2026:** Posecode existed before the hackathon. During Build Week, the project was extended using **Codex** — running on **GPT-5.6** — as the primary engineering tool for a real batch of shipped work: motion/grounding quality, language contract diagnostics, licensing restructuring, release automation, and product-facing pages. The sections below distinguish previous work from Build Week work using actual commit history, not a roadmap.
181
+
182
+
---
183
+
184
+
## OpenAI Build Week Extension
185
+
186
+
### What existed before Build Week
187
+
188
+
Before Build Week, Posecode already included:
189
+
190
+
- the core `.posecode` domain-specific language,
191
+
- a parser and intermediate motion representation,
192
+
- basic range-of-motion validation,
193
+
- a Three.js/WebGL renderer,
194
+
- forward kinematics,
195
+
- basic inverse-kinematics and ground-lock behavior,
196
+
- a browser playground,
197
+
- example movement files,
198
+
- shareable Posecode links,
199
+
- and an MCP server foundation.
200
+
201
+
This original version was developed primarily with **Claude** as an AI-assisted engineering tool.
202
+
203
+
That prior work provides the foundation for the project, but it is not presented as the new hackathon contribution.
204
+
205
+
### What was added during Build Week
206
+
207
+
Every item below is a merged, dated pull request built with Codex (GPT-5.6) — see [Build Week Evidence](#build-week-evidence) for direct links.
208
+
209
+
1.**Motion and grounding overhaul** — ROM-constrained reach IK, semantic palm/fist/sole/knee/pelvis contact surfaces, multi-contact refinement, stable support handoffs, and XBot-aware grounding ([#76](https://github.com/posecode-dev/posecode/pull/76)).
210
+
2.**Language contract and diagnostics** — Posecode language/IR v0.3 custom start-pose blocks with ROM-checked overrides, live and clip-wide grounding/self-collision diagnostics, and an accessible metric floor guide ([#92](https://github.com/posecode-dev/posecode/pull/92)).
211
+
3.**Licensing restructure** — split the monorepo into an Apache-2.0 standard layer (spec, parser, share, language, LSP, VS Code) and an AGPL-3.0 product layer (render, embed, MCP, eval, playground), with a commercial-license path ([#84](https://github.com/posecode-dev/posecode/pull/84)).
212
+
4.**Release automation** — Changesets-driven npm publishing via GitHub OIDC, MCP Registry publishing, and CI validation of package versions, entry points, and tarball contents ([#66](https://github.com/posecode-dev/posecode/pull/66)).
213
+
5.**Third-party integration readiness** — Posecode 0.2 timing vocabulary (`drive`/`settle`/`flow`/`snap`), a parser validation CLI, and embed compatibility metadata ([#62](https://github.com/posecode-dev/posecode/pull/62)).
214
+
6.**Ground-lock correctness** — parser-owned validation for per-side foot/hand/elbow ground locks and back-contact support for supine movements, replacing silent acceptance of invalid contacts ([#61](https://github.com/posecode-dev/posecode/pull/61), [#64](https://github.com/posecode-dev/posecode/pull/64)).
215
+
7.**LLM-first landing page and product page** — redesigned the landing page around a prompt → Posecode → live 3D story, and added a `/for-products` page documenting the web component, parser, renderer, and MCP server for integrators ([#82](https://github.com/posecode-dev/posecode/pull/82), [#74](https://github.com/posecode-dev/posecode/pull/74)).
216
+
8.**Mobile and search fixes** — mobile toolbar/viewer layout, natural hand orientation, and Google Search indexing corrections ([#78](https://github.com/posecode-dev/posecode/pull/78), [#65](https://github.com/posecode-dev/posecode/pull/65)).
During Build Week, Codex sessions ran on **GPT-5.6** (GPT-5.6 Terra), which is the model that powers Codex for this event. GPT-5.6 is the reasoning engine behind every Build Week change listed above: reading the existing monorepo, proposing the ROM-constrained IK and contact-surface design in [#76](https://github.com/posecode-dev/posecode/pull/76), designing the language/IR v0.3 diagnostics in [#92](https://github.com/posecode-dev/posecode/pull/92), and drafting the licensing boundary in [#84](https://github.com/posecode-dev/posecode/pull/84).
232
+
233
+
A GPT-5.6-powered natural-language-to-Posecode generation feature (describe a movement in plain English, get a validated `.posecode` document back) is a natural next step given the existing [`posecode_authoring_guide` MCP tool](packages/posecode-mcp/README.md), but it is **not yet built** — it is not claimed as shipped functionality here.
234
+
235
+
---
236
+
237
+
## How Codex Is Used
238
+
239
+
Codex is the primary engineering tool used for the Build Week extension.
240
+
241
+
During the hackathon period, Codex was used to:
242
+
243
+
- inspect and understand the existing monorepo before each change,
244
+
- design and implement the ROM-constrained reach IK and contact-surface system ([#76](https://github.com/posecode-dev/posecode/pull/76)),
245
+
- design and implement the language/IR v0.3 diagnostics and floor guide ([#92](https://github.com/posecode-dev/posecode/pull/92)),
246
+
- restructure package licensing across the monorepo ([#84](https://github.com/posecode-dev/posecode/pull/84)),
247
+
- build the Changesets/OIDC npm and MCP Registry release pipeline ([#66](https://github.com/posecode-dev/posecode/pull/66)),
248
+
- fix ground-lock validation and silent-acceptance bugs ([#61](https://github.com/posecode-dev/posecode/pull/61), [#64](https://github.com/posecode-dev/posecode/pull/64)),
249
+
- redesign the landing page and add the product integration page ([#82](https://github.com/posecode-dev/posecode/pull/82), [#74](https://github.com/posecode-dev/posecode/pull/74)),
250
+
- write unit, integration, and evaluation-harness tests for each change,
251
+
- and fix mobile UI and search-indexing regressions.
252
+
253
+
Codex accelerates implementation, but the project remains human-directed. The following decisions were reviewed and selected manually: DSL semantics, system architecture, licensing boundaries, biomechanical constraints, validation policy, user experience, and acceptance or rejection of generated code.
254
+
255
+
### Codex development workflow
256
+
257
+
The Build Week workflow follows this process:
258
+
259
+
1. Define a specific product or engineering problem.
260
+
2. Ask Codex to inspect the relevant implementation.
261
+
3. Request one or more possible approaches.
262
+
4. Review the trade-offs and choose the architecture.
263
+
5. Use Codex to implement the selected approach.
264
+
6. Run type checking, tests, and biomechanical evaluations (`npm run eval`).
265
+
7. Inspect failures manually.
266
+
8. Refine the implementation with additional Codex sessions.
267
+
9. Review the final changes before committing.
268
+
269
+
---
270
+
271
+
## Build Week Evidence
272
+
273
+
All Build Week work is public, dated, and directly linked below — no placeholders.
> **OpenAI Build Week 2026:** Posecode existed before the hackathon. During Build Week, the project was extended using **Codex** — running on **GPT-5.6** — as the primary engineering tool for a real batch of shipped work: motion/grounding quality, language contract diagnostics, licensing restructuring, release automation, and product-facing pages. The sections below distinguish previous work from Build Week work using actual commit history, not a roadmap.
662
-
663
-
---
664
-
665
-
## OpenAI Build Week Extension
666
-
667
-
### What existed before Build Week
668
-
669
-
Before Build Week, Posecode already included:
670
-
671
-
- the core `.posecode` domain-specific language,
672
-
- a parser and intermediate motion representation,
673
-
- basic range-of-motion validation,
674
-
- a Three.js/WebGL renderer,
675
-
- forward kinematics,
676
-
- basic inverse-kinematics and ground-lock behavior,
677
-
- a browser playground,
678
-
- example movement files,
679
-
- shareable Posecode links,
680
-
- and an MCP server foundation.
681
-
682
-
This original version was developed primarily with **Claude** as an AI-assisted engineering tool.
683
-
684
-
That prior work provides the foundation for the project, but it is not presented as the new hackathon contribution.
685
-
686
-
### What was added during Build Week
687
-
688
-
Every item below is a merged, dated pull request built with Codex (GPT-5.6) — see [Build Week Evidence](#build-week-evidence) for direct links.
689
-
690
-
1.**Motion and grounding overhaul** — ROM-constrained reach IK, semantic palm/fist/sole/knee/pelvis contact surfaces, multi-contact refinement, stable support handoffs, and XBot-aware grounding ([#76](https://github.com/posecode-dev/posecode/pull/76)).
691
-
2.**Language contract and diagnostics** — Posecode language/IR v0.3 custom start-pose blocks with ROM-checked overrides, live and clip-wide grounding/self-collision diagnostics, and an accessible metric floor guide ([#92](https://github.com/posecode-dev/posecode/pull/92)).
692
-
3.**Licensing restructure** — split the monorepo into an Apache-2.0 standard layer (spec, parser, share, language, LSP, VS Code) and an AGPL-3.0 product layer (render, embed, MCP, eval, playground), with a commercial-license path ([#84](https://github.com/posecode-dev/posecode/pull/84)).
693
-
4.**Release automation** — Changesets-driven npm publishing via GitHub OIDC, MCP Registry publishing, and CI validation of package versions, entry points, and tarball contents ([#66](https://github.com/posecode-dev/posecode/pull/66)).
694
-
5.**Third-party integration readiness** — Posecode 0.2 timing vocabulary (`drive`/`settle`/`flow`/`snap`), a parser validation CLI, and embed compatibility metadata ([#62](https://github.com/posecode-dev/posecode/pull/62)).
695
-
6.**Ground-lock correctness** — parser-owned validation for per-side foot/hand/elbow ground locks and back-contact support for supine movements, replacing silent acceptance of invalid contacts ([#61](https://github.com/posecode-dev/posecode/pull/61), [#64](https://github.com/posecode-dev/posecode/pull/64)).
696
-
7.**LLM-first landing page and product page** — redesigned the landing page around a prompt → Posecode → live 3D story, and added a `/for-products` page documenting the web component, parser, renderer, and MCP server for integrators ([#82](https://github.com/posecode-dev/posecode/pull/82), [#74](https://github.com/posecode-dev/posecode/pull/74)).
697
-
8.**Mobile and search fixes** — mobile toolbar/viewer layout, natural hand orientation, and Google Search indexing corrections ([#78](https://github.com/posecode-dev/posecode/pull/78), [#65](https://github.com/posecode-dev/posecode/pull/65)).
During Build Week, Codex sessions ran on **GPT-5.6** (GPT-5.6 Terra), which is the model that powers Codex for this event. GPT-5.6 is the reasoning engine behind every Build Week change listed above: reading the existing monorepo, proposing the ROM-constrained IK and contact-surface design in [#76](https://github.com/posecode-dev/posecode/pull/76), designing the language/IR v0.3 diagnostics in [#92](https://github.com/posecode-dev/posecode/pull/92), and drafting the licensing boundary in [#84](https://github.com/posecode-dev/posecode/pull/84).
714
-
715
-
A GPT-5.6-powered natural-language-to-Posecode generation feature (describe a movement in plain English, get a validated `.posecode` document back) is a natural next step given the existing [`posecode_authoring_guide` MCP tool](packages/posecode-mcp/README.md), but it is **not yet built** — it is not claimed as shipped functionality here.
716
-
717
-
---
718
-
719
-
## How Codex Is Used
720
-
721
-
Codex is the primary engineering tool used for the Build Week extension.
722
-
723
-
During the hackathon period, Codex was used to:
724
-
725
-
- inspect and understand the existing monorepo before each change,
726
-
- design and implement the ROM-constrained reach IK and contact-surface system ([#76](https://github.com/posecode-dev/posecode/pull/76)),
727
-
- design and implement the language/IR v0.3 diagnostics and floor guide ([#92](https://github.com/posecode-dev/posecode/pull/92)),
728
-
- restructure package licensing across the monorepo ([#84](https://github.com/posecode-dev/posecode/pull/84)),
729
-
- build the Changesets/OIDC npm and MCP Registry release pipeline ([#66](https://github.com/posecode-dev/posecode/pull/66)),
730
-
- fix ground-lock validation and silent-acceptance bugs ([#61](https://github.com/posecode-dev/posecode/pull/61), [#64](https://github.com/posecode-dev/posecode/pull/64)),
731
-
- redesign the landing page and add the product integration page ([#82](https://github.com/posecode-dev/posecode/pull/82), [#74](https://github.com/posecode-dev/posecode/pull/74)),
732
-
- write unit, integration, and evaluation-harness tests for each change,
733
-
- and fix mobile UI and search-indexing regressions.
734
-
735
-
Codex accelerates implementation, but the project remains human-directed. The following decisions were reviewed and selected manually: DSL semantics, system architecture, licensing boundaries, biomechanical constraints, validation policy, user experience, and acceptance or rejection of generated code.
736
-
737
-
### Codex development workflow
738
-
739
-
The Build Week workflow follows this process:
740
-
741
-
1. Define a specific product or engineering problem.
742
-
2. Ask Codex to inspect the relevant implementation.
743
-
3. Request one or more possible approaches.
744
-
4. Review the trade-offs and choose the architecture.
745
-
5. Use Codex to implement the selected approach.
746
-
6. Run type checking, tests, and biomechanical evaluations (`npm run eval`).
747
-
7. Inspect failures manually.
748
-
8. Refine the implementation with additional Codex sessions.
749
-
9. Review the final changes before committing.
750
-
751
-
### Codex session
752
-
753
-
```text
754
-
Codex /feedback session ID: TODO — run /feedback in the Codex thread where the majority
755
-
of this Build Week work was built, then paste the resulting Session ID here.
756
-
```
757
-
758
-
---
759
-
760
-
## Build Week Evidence
761
-
762
-
All Build Week work is public, dated, and directly linked below — no placeholders.
0 commit comments