体积数据流

<!-- motion-registry-context:{"format":"1.0.0","recipe_id":"data.flow-volume","recipe_version":"0.2.0","recipe_source":"recipes/data/flow-volume/recipe.yaml"} -->
# Motion Registry Context

<!-- motion-registry-section:recipe-identity:start -->
## Recipe identity
- Recipe ID: data.flow-volume
- Schema version: 0.2.0
- Recipe source: recipes/data/flow-volume/recipe.yaml
<!-- motion-registry-section:recipe-identity:end -->

<!-- motion-registry-section:motion-intent:start -->
## Motion intent and scope
- Purpose (zh): 发光数据包沿三维流道穿过空间节点并在终点汇聚，形成有限时长的吞吐叙事。
- Purpose (en): Glowing data packets cross spatial nodes through 3D flow lanes and converge at targets in a finite throughput narrative.
- Scope: scene
- Complexity: advanced
- Subjects: mixed
- Intents: explain, emphasize, reveal
- Use cases: data-story, knowledge-video, product-demo, presentation
- Recipe capabilities: volumetric-flow, packet-travel, spatial-nodes, throughput-control
<!-- motion-registry-section:motion-intent:end -->

<!-- motion-registry-section:inputs:start -->
## Inputs
- nodes: string (required; default=INGEST|PROCESS|CACHE|DELIVER) — Pipe-separated labels for the source, transit, and target nodes.
- packet_count: integer (optional; default=18) — Deterministic number of packets travelling through the volume.
- flow_rate: number (optional; default=0.82) — Normalized throughput multiplier for packet travel distance.
- headline: string (required; default=THROUGHput / 24H) — Caption explaining the flow volume.
<!-- motion-registry-section:inputs:end -->

<!-- motion-registry-section:normalized-timeline:start -->
## Normalized motion timeline (0 to 1)
- 0.04–0.30 · volume.reveal · opacity.fade → volume · parameters={"from":0,"to":1}
- 0.10–0.56 · nodes.stagger · collection.stagger → nodes · parameters={"order":"source","fraction":0.1}
- 0.18–0.74 · packets.flow · path.draw → packets · parameters={"from":0,"to":1}
- 0.58–0.82 · volume.emphasis · transform.scale → volume · parameters={"from":0.96,"to":1}
- 0.82–1.00 · volume.hold · state.hold → volume · parameters={}
<!-- motion-registry-section:normalized-timeline:end -->

<!-- motion-registry-section:output-envelope:start -->
## Output envelope
- Aspect ratios: 16:9, 9:16, 1:1
- Duration: min 2.8s; preferred 4.2s; max 6s
<!-- motion-registry-section:output-envelope:end -->

<!-- motion-registry-section:acceptance:start -->
## Acceptance constraints
- volumetric-grammar: The final frame shows depth-separated nodes, multiple flow lanes, and packet trails rather than a flat graph.
- finite-flow: Every packet travels a bounded distance and stops at a target before the hold.
- deterministic: The same inputs produce identical packet lanes, node positions, timing, and final state.
- readable-labels: Node labels and the headline remain readable and are not covered by packets or glow.
<!-- motion-registry-section:acceptance:end -->

<!-- motion-registry-section:handoff-invariants:start -->
## Handoff invariants
- Preserve the subject, input meaning, event order, overlaps, final state, and approximate normalized timing.
- Keep the implementation deterministic and retain a readable, stable final hold.
- Treat the Recipe document as the source of truth; do not infer engine APIs in this shared core.
<!-- motion-registry-section:handoff-invariants:end -->