Float frames re-normalized on every Placement reconstruction, so
canonical JSON bytes and content hashes drifted across save/load cycles
(connector interface_hash mismatch, unstable PartInstance placement
identity, spurious cache/dirty misses).
Store every hashed/persisted frame as exact integer ticks at 1e-9
resolution instead:
- placement.py: placement_ticks / validate_placement_ticks (pure integer
unit-orthogonal-handedness checks) / placement_from_canonical with a
from_exact_frame constructor that keeps durable components verbatim;
tick frames short-circuit re-quantization; placement_frame_mm exports
millimetre floats for translators
- ConnectorInterface.local_frame and PartInstance.placement store ticks;
definition content hashes are byte-stable across round trips
- solved snapshots, authored placements, assembly state, solve keys and
component cache payloads compare tick-to-tick; rebuilds reuse
from_exact_frame so verification is exact instead of tolerance-based
- occurrence-graph transforms and scene product ingestion convert ticks
at the runtime boundary only
- FreeCAD runtime and Fusion360/SolidWorks translators convert recorded
tick frames back to millimetre floats when emitting target payloads
Derived z_axis is authoritative (computed once at write time) and is
never recomputed on read. BREP/zip/package integrity checks remain
strict byte hashes. Existing pre-tick packages must be recaptured;
examples/22_mecanum_wheel was rebuilt and revalidated.