Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 11 additions & 11 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,15 +3,13 @@
<p align="center">
<b>Kinematic motion as text.</b>
<br />
Mermaid gave LLMs a way to draw diagrams.
<br />
Posecode gives them a way to show movement.
An inspectable, editable movement format for animation tools, LLMs, and web products.
</p>

<p align="center">
A human-readable spatial DSL for describing, validating, and rendering
Like Mermaid for movement: small text documents for describing, validating, and rendering
<br />
exercises, physiotherapy movements, posture, dance, and human motion.
deterministic human motion without hiding the source inside a black box.
</p>

<p align="center">
Expand Down Expand Up @@ -41,7 +39,9 @@

## Why Posecode?

Ask an LLM to explain physical movement and it usually returns unstructured prose or a static diagram.
Animation clips and generated trajectories can show movement, but they often hide the semantic decisions that produced it.

Posecode keeps those decisions in readable source. A human can write the document, an animation tool can emit it, or an LLM can draft it. Parsing, validation, editing, and rendering do not require an AI model.


<p align="center">
Expand Down Expand Up @@ -75,14 +75,14 @@ A human may understand that instruction, but a renderer cannot reliably determin
- in what sequence,
- or within which physical limits.

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.
Humans, tools, and language models all need a shared syntax for expressing movement in a renderable and testable form.

Posecode provides that missing representation.

### See Posecode in 28 seconds

From an LLM prompt to editable Posecode, validated 3D rendering, MCP tools,
and a one-script web embed.
From readable movement source to validated 3D rendering, MCP tools, and a
one-script web embed.

<p align="center">
<a href="docs/launch-media/posecode-cut2-builder-16x9.mp4">
Expand Down Expand Up @@ -845,7 +845,7 @@ Feedback and contributions are welcome.

---
<p align="center">
<b>LLMs already have languages for software, data, and interfaces.</b>
<b>Animation tools, LLMs, and web products need movement they can inspect.</b>
<br />
<b>Posecode gives them a language for movement.</b>
<b>Posecode makes movement readable source.</b>
</p>
34 changes: 17 additions & 17 deletions playground/for-products.html
Original file line number Diff line number Diff line change
Expand Up @@ -3,23 +3,23 @@
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<title>Use Posecode in Your Product | Open-Source Motion Tools</title>
<meta name="description" content="Embed Posecode movement in a web product today with an open-source web component, parser, renderer, share links, npm packages, or a local MCP server." />
<title>Integrate Inspectable Movement | Posecode for Products</title>
<meta name="description" content="Add a readable, editable movement format to an animation tool, LLM workflow, or web product with Posecode's parser, renderer, web component, and MCP server." />
<link rel="canonical" href="https://www.posecode.org/for-products" />
<link rel="icon" type="image/png" sizes="192x192" href="/favicon-192.png" />
<link rel="apple-touch-icon" sizes="180x180" href="/apple-touch-icon.png" />
<meta name="theme-color" content="#0b0c0d" />
<meta property="og:title" content="Use Posecode in your product" />
<meta property="og:description" content="Open-source building blocks for adding readable, editable 3D movement to web products—with a clear view of what exists today and what does not." />
<meta property="og:title" content="Integrate inspectable movement with Posecode" />
<meta property="og:description" content="Open-source building blocks for adding readable, editable 3D movement to animation tools, LLM workflows, and web products." />
<meta property="og:type" content="website" />
<meta property="og:url" content="https://www.posecode.org/for-products" />
<meta property="og:site_name" content="Posecode" />
<meta property="og:image" content="https://www.posecode.org/og.png" />
<meta property="og:image:width" content="1200" />
<meta property="og:image:height" content="630" />
<meta name="twitter:card" content="summary_large_image" />
<meta name="twitter:title" content="Use Posecode in your product" />
<meta name="twitter:description" content="Embed readable, editable 3D movement with Posecode's open-source web component and TypeScript packages." />
<meta name="twitter:title" content="Integrate inspectable movement with Posecode" />
<meta name="twitter:description" content="Use Posecode's readable movement format, TypeScript packages, and web component in your product." />
<meta name="twitter:image" content="https://www.posecode.org/og.png" />
<link rel="preconnect" href="https://fonts.googleapis.com" />
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin />
Expand Down Expand Up @@ -50,25 +50,25 @@
<section class="product-hero">
<div class="product-hero-copy reveal">
<p class="eyebrow">For product owners &amp; developers</p>
<h1>Put movement inside your product.</h1>
<p class="product-lede">Posecode turns a small, readable text document into an editable 3D movement. Use the open-source pieces now—or help shape the product infrastructure that should come next.</p>
<h1>Build with inspectable movement.</h1>
<p class="product-lede">Posecode is a readable movement format with a parser, typed IR, Three.js renderer, web component, and LLM tools. Author it directly or with an LLM, then keep the result editable and under your control.</p>
<div class="hero-cta">
<a class="btn primary lg" href="mailto:hello@posecode.org?subject=Posecode%20product%20integration">Discuss an integration&nbsp;→</a>
<a class="btn ghost lg" href="#today">See what exists today</a>
</div>
</div>
<aside class="reality-card reveal" aria-label="Posecode service status">
<p class="status-label"><span aria-hidden="true"></span> The honest version</p>
<p class="status-label"><span aria-hidden="true"></span> Current state</p>
<h2>Open-source toolkit today.<br />No hosted commercial platform yet.</h2>
<p>You can ship the web component and TypeScript packages in your own product now. Hosted APIs, cloud rendering, private libraries, and enterprise operations are ideas we would explore with design partnersnot services you can buy today.</p>
<p>You can ship the web component and TypeScript packages in your own product now. Hosted APIs, cloud rendering, private libraries, and enterprise operations are ideas we would explore with design partners. They are not services you can buy today.</p>
</aside>
</section>

<section id="integrate" class="product-section integration-section">
<header class="product-section-head reveal">
<p class="eyebrow">Ways to integrate</p>
<h2>Start at the layer you need.</h2>
<p>Keep the standard player, compose the lower-level libraries, or give a local agent movement tools.</p>
<p>Keep the standard player, compose the lower-level libraries, or give an LLM movement tools.</p>
</header>
<div class="integration-grid">
<article class="integration-card reveal">
Expand All @@ -92,7 +92,7 @@ <h3>Own the interface</h3>
</div>
</article>
<article class="integration-card reveal">
<span class="card-index">03 / agents</span>
<span class="card-index">03 / LLMs</span>
<h3>Run movement tools locally</h3>
<p>The npm MCP server runs over stdio on your machine. It teaches an MCP client the language, validates documents, and creates playground links.</p>
<pre aria-label="Local MCP command example"><code>npx -y posecode-mcp@latest</code></pre>
Expand All @@ -109,11 +109,11 @@ <h3>Run movement tools locally</h3>
<h2>Movement that stays inspectable.</h2>
</header>
<div class="use-case-grid">
<article class="use-case reveal"><h3>Animation editors</h3><p>Generate a first pass from text, expose timing and joint values, and let a human revise the movement instead of accepting a black-box clip.</p></article>
<article class="use-case reveal"><h3>Animation editors</h3><p>Load readable movement source, expose timing and joint values, and let a human revise the result instead of accepting a black-box clip.</p></article>
<article class="use-case reveal"><h3>Fitness &amp; rehab products</h3><p>Show an exercise beside a program or cue. Joint angles are clamped to general range-of-motion limits, but Posecode is not clinical advice or patient-specific validation.</p></article>
<article class="use-case reveal"><h3>Education tools</h3><p>Connect written instruction to a moving figure for anatomy, dance, physical education, or movement vocabulary.</p></article>
<article class="use-case reveal"><h3>Movement libraries</h3><p>Store small, diffable text files, validate them in CI, and open any movement in the browser without pre-rendering video.</p></article>
<article class="use-case reveal"><h3>Agent workflows</h3><p>Let an MCP-capable local agent write, validate, repair, and return a link to movement the user can inspect.</p></article>
<article class="use-case reveal"><h3>LLM workflows</h3><p>Let an MCP-capable LLM write, validate, repair, and return a link to movement the user can inspect.</p></article>
<article class="use-case reveal"><h3>Other web products</h3><p>Use movement as editable content anywhere a video or static diagram is too rigid and a full animation pipeline is too heavy.</p></article>
</div>
</section>
Expand All @@ -138,8 +138,8 @@ <h2>The current open-source surface.</h2>
<section id="exploring" class="product-section exploring-section">
<div class="exploring-copy reveal">
<p class="eyebrow">Exploring next</p>
<h2>Useful infrastructure should be shaped by real products.</h2>
<p>We are interested in working with a small number of design partners to learn which operational layer actually matters. Possibilities—not announced products—include:</p>
<h2>Real integrations should decide what comes next.</h2>
<p>We are interested in working with a small number of design partners to learn which operational layer actually matters. Possible areas to explore include:</p>
</div>
<ul class="future-list reveal">
<li>Hosted generation or validation API</li>
Expand All @@ -151,7 +151,7 @@ <h2>Useful infrastructure should be shaped by real products.</h2>
<li>Usage analytics</li>
<li>Support, security review, and SLAs</li>
</ul>
<p class="future-qualifier reveal">None of these capabilities is generally available today. There is no published commercial pricing. A design-partner conversation is for scoping the problem, constraints, and a possible collaborationnot selling a service that already exists.</p>
<p class="future-qualifier reveal">None of these capabilities is generally available today. There is no published commercial pricing. A design-partner conversation is for scoping the problem, constraints, and a possible collaboration. It is not a sales call for a service that already exists.</p>
</section>

<section class="product-cta reveal" aria-labelledby="product-cta-title">
Expand Down
Loading