Back to corpus
research noteexperiment writeup candidatescore 18

Motion-To-Inscription Source Authority And Mac4 Seated Protocol V1

This document defines the practical motion-to-inscription operating plan for the current hardware reality. It assumes the twelve-sensor Mocopi upgrade is not available yet and that full room-scale depth integration is not finished. The goal is to stop waiting for ideal hardware and establish a robust, usable capture regime that can generate a real motion library and feed the inscription system now.

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

This document defines the practical motion-to-inscription operating plan for the current hardware reality. It assumes the twelve-sensor Mocopi upgrade is not available yet and that full room-scale depth integration is not finished. The goal is to stop waiting for ideal hardware and establish a robust, usable capture regime that can generate a real motion library and feed the inscription system now. The operating principle is simple. We do not need the perfect capture stack to begin learning stable motion-to-inscription mappings. We need one trustworthy capture regime that is consistent enough to support repeatable motion states, clean semantic labels, and replayable rendering. The inscription engine is real. The `cc-inscription` Rust system already exists and compiles embodied dynamics into typed claims and N'Ko surface forms. The Unity and MotionMix visual stack also exists and has been validated enough to run and receive body state. What is missing is not the symbolic layer. What is missing is a stable live body-source chain. The current `:9404` motion surface is up, but the live body state is degraded. The `/skeleton-3d` endpoint currently reports effectively empty fused body state. That means the main bottleneck is source quality, not rendering or inscription code.

Promotion decision

What has to happen next

Attach run IDs, datasets, metrics, and reproduction commands.

Why this is not always a full paper yet

Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.