The public workspace is useful when application shells can depend on shared models without inheriting a product's renderer, permissions, assets, or release pipeline.
rusty-xr-contracts is the shared center for plain data: math, poses, frame timing, eye views, camera/depth metadata, hand snapshots, media layers, interaction rays, room mesh state, capture lifecycle metadata, depth query summaries, render payloads, and counters.
Utility crates build on contracts without pulling in native platform dependencies. This keeps tests fast and lets downstream shells choose their own Android, OpenXR, Vulkan, Makepad, Unity, LSL, OSC, or diagnostics UI integration strategy.
rusty-xr-debug-canvas owns normalized diagnostic HUD documents, draw lists, tones, and input-neutral HUD commands. rusty-xr-osc owns generic OSC packets, endpoint status, and UDP helpers. Quest renderers, controller bindings, LSL bridges, ADB intents, and app-specific address trees remain shell-owned.
rusty-xr-particles owns surface-locked coordinate sampling, live hand-mesh particle anchors, same-surface and cross-surface neighborhoods, collider-ready dynamic mesh surfaces, diagnostic shells, and public SDF attraction helpers. rusty-xr-sdf owns packed SDF grids, sparse TSDF snapshots, mesh-to-SDF conversion, and depth-derived support or impact query contracts.
Graph and boundary audits are used as local checks, but raw audit outputs stay out of the public site. The published takeaway is the stable dependency direction: plain contracts and deterministic helpers in Rusty XR, native runtime ownership and product behavior in downstream shells.