Tracks registry decision D-K under #43. The topology states a candidate design, not a settled fact. Explicit owner GO is required.
Decision question
Should camera motion and hot-loop edits in realtime preview become sampled inputs under the chassis animation kernel, or remain separately framed host inputs over the same pure core?
Decision time
When the preview lane starts, after Phase 2 instruments exist and before legacy realtime-performance policy is adopted.
Evidence bar
A render-modes design doc must map:
- realtime preview, accurate static, and accurate animation onto one meaning-preserving pipeline;
- camera state, in-flight edits, committed document state, and explicit sample time;
- host clock/scheduling ownership, replay identity, determinism, damage, and cache keys;
- the legacy estate—frame reuse, interaction-quality rendering, cache promotion, progressive rerasterization, and camera quantization—onto host/compositor policy;
- counterexamples where sampling could change meaning, history framing, picking, or export, with a benchmark and conformance plan.
Guardrails
- Modes may differ in when and at what quality they paint, never in what things mean.
- The core owns no wall clock or frame scheduler.
- No preview optimization enters resolve or display-list semantics.
- Do not migrate the legacy performance estate or authorize implementation here.
Context
Done
The design doc and rejected model are linked; owner GO records unified or separate input framing; replay/cache/clock ownership is unambiguous; follow-up work is filed; and the verdict is recorded in the charter and #43.
Tracks registry decision D-K under #43. The topology states a candidate design, not a settled fact. Explicit owner GO is required.
Decision question
Should camera motion and hot-loop edits in realtime preview become sampled inputs under the chassis animation kernel, or remain separately framed host inputs over the same pure core?
Decision time
When the preview lane starts, after Phase 2 instruments exist and before legacy realtime-performance policy is adopted.
Evidence bar
A render-modes design doc must map:
Guardrails
Context
Done
The design doc and rejected model are linked; owner GO records unified or separate input framing; replay/cache/clock ownership is unambiguous; follow-up work is filed; and the verdict is recorded in the charter and #43.