Working systems only. This lane stays small until a prototype has enough behavior, failure, or evidence to teach something useful.
Prototype notes should show what was tested, what changed, and what the system still cannot do.
Tests that reveal adaptive behavior, state continuity, AI workflow constraints, or headset-specific friction.
Reusable APIs belong in Tools. Buyer-facing delivery belongs on VeeRuby. Private client detail stays private.
A test path for turning gaze, head pose, hands, posture, boundaries, and task state into adaptive interface decisions that can be inspected after the session.
A small benchmark for how much spatial memory must persist before an XR system feels continuous rather than reset-heavy.
Count how many orientation actions a returning user must repeat before work can continue.
Separate remembered environment state from remembered user preference so adaptation can be audited.
The next public version should show the intended behavior and the failure mode that still needs work.