Stage 5: RAIL — Execution Plan
| Step | Task | Machine | Est. | |------|------|---------|------| | 0.1 | Create `model/dit.py` with MotionDiT architecture (Tiny: 4 blocks/128dim, Full: 8 blocks/256dim) | Mac1 | 4h | | 0.2 | Create `model/flow_matching.py` with OT-CFM (training + Euler/midpoint sampling + CFG) | Mac1 | 4h | | 0.3 | Create `training/flow_losses.py` (flow matching loss + existing structure regularizers) | Mac1 | 2h | | 0.4 | Modify `config.py` to add FlowMatchingConfig and DiTConfig blocks | Mac1 | 1h | | 0.5 | Modify `training/tra
Full HTML reader
Read the full artifact
Extracted abstract or opening context
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.