Back to corpus
proposalexperiment writeup candidatescore 36

cc-anticipation: Implementation Guide

``` cc-anticipation/ ├── Cargo.toml ├── src/ │ ├── lib.rs # Public API, re-exports │ ├── types.rs # MotionWindow, AnticipationPacket, etc. │ ├── config.rs # AnticiaptionConfig (frozen) │ ├── kernel.rs # Main anticipation kernel │ ├── features/ │ │ ├── mod.rs │ │ ├── kinematics.rs # Skeleton-based features │ │ ├── latent_dynamics.rs # LIM-RPS-based features │ │ └── coordination.rs # Cross-limb coherence │ ├── embedding/ │ │ ├── mod.rs │ │ ├── projection.rs # Fixed random projection (v0) │ │ └── encoder.rs # Learned

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

**Document Version**: 0.1.0 **Created**: 2025-12-26 **Parent**: [PROJECT_CHARTER.md](./PROJECT_CHARTER.md)

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.