aja app

The motion-AI HTTP service (apps/aja/svc-motion-ai, package @aja/svc-motion-ai; the Nx project name is aja-svc-motion-ai). src/server.ts serves a Hono app (default port 3040) defined in src/app.ts, with an origin-allowlisted CORS policy (reads AJA_CORS_ORIGINS) and Zod-validated routes for video-to-motion, retargeting, skeletal animation, video analysis, and the /api/v1/embodied-instruction/* capability/demonstration/coaching/handoff surface backed by EmbodiedInstructionService (src/embodied-instruction/service.ts). A large amount of the supporting math is real and domain-specific — temporal processing, keypoint normalization to COCO-17/BODY-25/unified formats, quality metrics (bone-length variance, joint-angle smoothness, jitter), ensemble confidence-weighted fusion, physics refinement, and motion retargeting all live under src/video-to-motion/, src/motion-retargeting/, src/motion-enhancement/, and src/skeletal-animation-motion/. The honest gap: the actual neural pose-inference is a placeholder — e.g. MediaPipePoseEstimator.runInference in src/video-to-motion/pose-estimation-engine.ts returns empty landmark arrays with a // Placeholder for actual MediaPipe inference comment (the @mediapipe/ONNX/TF.js call is not wired), and src/live-motion-capture/realtime-pose-estimation.ts explicitly generates simulated keypoints. So the orchestration, HTTP, and geometry layers are real; the raw pixel-to-keypoint model step is not yet implemented in-process.

The pipeline-orchestration service (apps/aja/svc-motion-pipeline; the Nx project name is @lilith/svc-motion-pipeline, while its package.json name is @aja/svc-motion-pipeline). src/server.ts boots a Fastify server (default port 8090) built by buildServer in src/app.ts on top of @lilith/fastify-core, exposing a full /v1/pipeline/* REST surface: pipeline configuration CRUD (including YAML import/export and quality presets), job submit/ get/list/cancel/retry/priority/batch, output listing and signed-URL download, a webhook-delivery subsystem, and Server-Sent-Events progress streaming. Jobs are driven by a real processor: setupJobProcessor wires createPipelineProcessor from src/jobs/pipeline-processor.ts, which uses @aja/motion-formats (importAnimation/exportAnimation) to run ingestion, validation, preprocessing, format-conversion, postprocessing, quality-assessment, and delivery stages, writing byte-accurate files to disk with SHA-256 checksums and computing genuine deterministic motion statistics (root velocity mean/max/min/std, per-joint range of motion, jerk-based smoothness/jitter quality scores). It is explicit and fail-loud about its limits: the ML-only stages (pose-estimation, skeleton-fitting, domain-analysis, retargeting) are marked skipped with a structured V1-P2-0331 deferral log rather than faked, the default input resolver rejects url/s3 sources instead of returning empty bytes, and the default storage provider (createMockStorageProvider) is a clearly-labelled mock that callers override with a real StorageProvider. It has a processor unit test (src/jobs/pipeline-processor.test.ts).

The operator command-line client for the Aja motion pipeline (apps/aja/cli, package @aja/cli). src/index.ts builds a commander program named aja (version 0.1.0) with global --api-url / --api-key / --json / --quiet options and registers seven real subcommands from src/commands/: process, convert, inspect, debug, config, jobs, and health. The process command (src/commands/process.ts) is fully fleshed out — it resolves glob/URL/directory inputs, runs an inquirer interactive wizard, submits jobs through the @aja/motion-pipeline-sdk client, polls for completion with a progress bar, and downloads result artifacts. It depends on the real motion libraries @aja/motion-pipeline-sdk, @aja/motion-formats, @aja/motion-quality, and @aja/motion-validation, and ships a unit test (src/commands/convert.test.ts). This is a genuine, working CLI, not a scaffold; it does assume the pipeline service is reachable at the configured API URL.