NAVIGATORIM — PRINTING AND WORKFLOW GUIDE
Prepared for 3.7.11 / Build54. Visual planning and training only.

1. PREPARE THE BENCH
Use a stationary, well-lit demonstration setup with powered equipment stopped and safely isolated. Keep loose/spare duplicate marker sheets outside the camera view. Use the app's current requirements and permissions; the source targets iOS/visionOS 27.0, but installation compatibility and signing must be checked on the actual device.

2. PRINT THE CORRECT KIT
Print NavigatorIM_All_9_Carriers_PRINT_100_PERCENT.pdf or the individual carrier PDFs at Actual Size / 100%. Turn off Fit, Shrink, scaling and borderless enlargement. These are DICT_5X5_100 markers. Do not mix them with an older DICT_4X4_50 calibration/reference set. The black square, including its black border, is 40.00 mm. The full label is 60.00 mm. Verify the 100 mm scale plus horizontal and vertical dimensions on more than one label. The guide's illustrations and video frames are NOT printable-scale substitutes for the marker PDF.

3. MAKE AND MEASURE THE RIGID CARRIER
The supplied STL is a 59.60 mm core. It assumes 0.20 mm combined label-plus-adhesive thickness on each opposing side, giving finished marker planes 60.00 mm apart. Measure the actual stack. If needed, adjust label_thickness in the SCAD source and regenerate the core rather than stretching the PDFs. The blind mount bore is 6.40 mm diameter and 18 mm deep, entering -Y. The STL retains the tracking-coordinate orientation: rotate X by +90 degrees in the slicer to place -Y down, then place it on the bed. Select material and print parameters for adequate rigidity; no validated mechanical loading specification is provided.

4. APPLY THE FIVE LABELS IN THE CORRECT ORIENTATION
Each carrier has FRONT +Z, RIGHT +X, BACK -Z, LEFT -X and TOP +Y labels. The unmarked bottom/mount face is -Y. Vertical-face marker tops point toward +Y. The top-face marker's top edge points toward -Z. Centre each label and align it with the face edges. Use matte, opaque labels without glossy laminate. Keep one page's five IDs together; do not rotate a face independently or duplicate an identity in the camera scene.

CARRIER / FRONT / RIGHT / BACK / LEFT / TOP
reference26 / 0 / 1 / 2 / 3 / 4
selector7 / 10 / 11 / 12 / 13 / 14
tool8 / 20 / 21 / 22 / 23 / 24
selector22 / 30 / 31 / 32 / 33 / 34
aux6 / 40 / 41 / 42 / 43 / 44
aux9 / 50 / 51 / 52 / 53 / 54
fixture1001 / 60 / 61 / 62 / 63 / 64
fixture1003 / 70 / 71 / 72 / 73 / 74
fixture1004 / 80 / 81 / 82 / 83 / 84

5. CALIBRATE THE REAL PHYSICAL TIPS
Fix RED reference26 rigidly to the workpiece. CYAN selector7 is the explicit optical point selector; WHITE tool8 is a separate operation tool. The current Build54 source and rigs.json set the CYAN7 starting tip to (0,-175,0) mm. An older prose ASSEMBLY.md in the supplied source says +175 mm; that historical sentence is not the current source value. Neither sign nor a preset is proof of the physical tip: measure your actual carrier/mount/shaft and confirm the calibrated tip on known targets. The JSON explicitly has tip_confirmed=false. WHITE tool presets depend on the chosen tool mode; do not assume a saw preset fits a drill or impactor.

6. REGISTER WITH ONE SELECTED INPUT
Choose the reference frame and point-capture source explicitly. Keep the required reference and selector currently visible/tracked and show two well-resolved, nonparallel faces where feasible. Follow the P1/P2/D3/D4 prompts and review the requested samples; the demonstrated workflow has twelve samples. Check the counter and positions after every capture. Recollect questionable samples. A visible sphere or held model is not evidence of a fresh, capture-eligible pose. Do not replace CYAN with WHITE or Muse without an explicit source change and suitable calibration.

7. IMPORT AND PLACE THE MODEL
Use a known-scale supported USDZ file. Choose free-space placement, a selected point or the appropriate recognized reference; then adjust position, rotation, scale and transparency deliberately. Inspection mode may show a temporary viewing size. Verify a known model dimension and the reference frame before interpreting alignment. Visual model import does not train or recognize an arbitrary physical object.

ORIGIN WARNING FOR THE INCLUDED CARRIER USDZ FILES
The visual USDZ assets are Y-up, in metres, with their origin at the bottom centre of the 59.60 mm core. The tracking rig/SCAD uses the centre of the finished carrier. The core centre is therefore 29.8 mm above the visual model origin. These are different coordinate contracts: do not treat the visual USDZ origin as the tracking origin or apply an offset twice. Verify the app's attachment transform with known geometry before pairing these assets. The USDZ files are visual references, not print-ready STL or calibration manifests.

8. READ MEASUREMENTS IN CONTEXT
Identify the selected point/axis before comparing point, radial, along, axis and plane values. The displays answer different questions. Use the radar together with the main scene and show/hide panels to improve visibility. Millimetre labels are units, not an accuracy specification. Keep-out and green/yellow/red cues only describe configured geometry; they do not detect hidden services or certify safe physical clearance.

9. CHECK A SIMPLE KNOWN SETUP
With the same frame and source, check a known tip location, known distance and known direction independently. Repeat from several viewpoints. Occlude RED and CYAN separately and confirm new capture is unavailable until valid tracking returns. Move/reseat a mount and treat the old registration as invalid. Keep a record of reference IDs, print dimensions, tip calibration, selected engine, tracking state and independent checks. Do not invent a passing tolerance: set and justify acceptance for your intended non-safety-critical demonstration.

10. PLATFORM DISTINCTIONS
The supplied iOS target uses OpenCV ArUco for active navigation. Build54 has one native Vision Enterprise target: ARKit Image Anchors starts with RED26/CYAN7/WHITE8 and raw Main Camera off. The explicit Main Camera/OpenCV mode requires the appropriate Apple authorization and private deployment arrangements. Hand and Muse are separate supported native Vision inputs, not native iPhone sources. A requested 120 Hz processing budget is not a measured 120 fps camera or accuracy guarantee.

SUPPORT AND LIMITATIONS
info@orthopractis.com | https://www.orthopractis.com/
For visual planning and training, not patient care, certified metrology, hidden-service detection, powered-machine operation or accident prevention. Stop and independently verify when tracking, calibration, mounting, scale or interpretation is uncertain. The source code and this media package have not been physically validated on your setup.

SOURCE BASIS
User-supplied Build54: README.md; BUILD54_COMPARISON.md; BUILD54_DEVICE_TEST.txt; NavigatorShared/NavigatorArucoTracking.swift; ArUcoReferenceKit/rigs.json, assembly geometry and original marker PDFs; SourceDesign/AppleReady_USDZ/README_VALIDATION.txt. Original marker PDFs and STL geometry are copied, not regenerated. This guide corrects the historical CYAN prose sign and does not alter the source app.
