Back to corpus
architecturetechnical paper candidatescore 32
Anticipation Pipeline Diagram
```mermaid flowchart TB subgraph Input [Input: MotionWindow] MW[MotionWindow<br/>50 frames @ 50Hz] SF[SkeletonFrames<br/>27 bones × 50 frames] LF[LatentFrames<br/>Optional embeddings] Coverage[Coverage Check<br/>≥ 0.9 required] end
Full HTML reader
Read the full artifact
Extracted abstract or opening context
**Version**: 2.0.0 **Last Updated**: 2025-01-01 **Parent**: [06-ANTICIPATION.md](../06-ANTICIPATION.md)
Where `constraint_saturation` = how close to physical limits (joint angles, balance).
| Value | Meaning | System Response | |-------|---------|-----------------| | 0.0-0.3 | Low | Observe, wait | | 0.3-0.6 | Medium | Prepare response | | 0.6-0.8 | High | Begin execution | | 0.8-1.0 | Very High | Full commit |
| Value | Meaning | |-------|---------| | > 0.5 | Strong convergence | | 0.0-0.5 | Gentle convergence | | -0.5-0.0 | Gentle divergence | | < -0.5 | Strong divergence |
| ID | Invariant | Check Location | |----|-----------|----------------| | INV-001 | Deterministic | No random seeds | | INV-003 | Coverage ≥ 0.9 | Entry validation | | INV-004 | Scalars in bounds | Packet creation | | INV-005 | Bone count = 27 | Frame validation | | INV-007 | Schema version | Deserialization |
Promotion decision
What has to happen next
Promote into a technical note or architecture paper with implementation anchors.
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.