diff --git a/docs/HYPERTWIST_CODEXR_OFF_DOMAIN_XR_COLLABORATION_DISCARD_CONFIRMATION_RECONCILIATION_2026-05-27.md b/docs/HYPERTWIST_CODEXR_OFF_DOMAIN_XR_COLLABORATION_DISCARD_CONFIRMATION_RECONCILIATION_2026-05-27.md
new file mode 100644
index 0000000..635765b
--- /dev/null
+++ b/docs/HYPERTWIST_CODEXR_OFF_DOMAIN_XR_COLLABORATION_DISCARD_CONFIRMATION_RECONCILIATION_2026-05-27.md
@@ -0,0 +1,87 @@
+# HyperTwist CodeXR Off-Domain XR Collaboration Discard Confirmation Reconciliation - 2026-05-27
+
+## Status
+
+This document is the source-backed discard-confirmation note for
+`aMonteSl/CodeXR` inside the HyperTwist `0R-E` non-live queue.
+
+It answers one narrow question:
+
+- does the current `CodeXR` source justify any retained HyperTwist owner,
+  benchmark, clean-room, or comparison lane beyond historical reference
+
+Result:
+
+- no retained HyperTwist lane survives
+- the earlier `0R-E` discard call remains correct
+- no product-code reopening is required
+- no clean-room or donor route should be reopened from this row
+
+## Source basis
+
+- `C:\HyperTwist\docs\HYPERTWIST_PHASE_0R_PACKET_0R_E_EVALUATION_2026-05-13.md`
+- `C:\HyperTwist\docs\REPO_LICENSE_TRACKING.md`
+- `C:\HyperTwist\docs\HYPERTWIST_REPO_STATE_BOARD_2026-05-11.md`
+- `C:\HyperTwist\docs\HYPERTWIST_PHASE_1R_RETAINED_SET_CONTRACT_AND_HANDOFF_2026-05-13.md`
+- `C:\HyperTwist\docs\HYPERTWIST_REPO_EVALUATION_RESET_AND_IMPLEMENTATION_SCHEDULE_2026-05-11.md`
+- `C:\Workspaces\HyperTwist\repos.manifest.json`
+- `C:\Workspaces\HyperTwist\mirrors\restrictive\aMonteSl\CodeXR\README.md`
+- `C:\Workspaces\HyperTwist\mirrors\restrictive\aMonteSl\CodeXR\src\core\startup\startupCoordinator.ts`
+- `C:\Workspaces\HyperTwist\mirrors\restrictive\aMonteSl\CodeXR\src\code_analysis\engine\analysisOrchestrator.ts`
+- `C:\Workspaces\HyperTwist\mirrors\restrictive\aMonteSl\CodeXR\src\servers\runtime\multiServerLauncher.ts`
+- `C:\Workspaces\HyperTwist\mirrors\restrictive\aMonteSl\CodeXR\templates\components\codexr\virtual-screen\virtualScreenRuntime.js`
+- `C:\Workspaces\HyperTwist\mirrors\restrictive\aMonteSl\CodeXR\templates\components\codexr\collaboration\codexrCollaborationRuntime.js`
+
+## Why discard remains correct
+
+The source is real and nontrivial, but its center of gravity is off-domain for
+HyperTwist:
+
+- `README.md` is explicitly about Visual Studio Code code-analysis
+  visualization in `XR`, not cubing/training/runtime ownership
+- `startupCoordinator.ts` is a deferred startup queue for extension boot and
+  analysis/session orchestration
+- `analysisOrchestrator.ts` is centered on code-analysis execution flow
+- `multiServerLauncher.ts` is centered on heterogeneous local server/runtime
+  launch and registry patterns
+- `virtualScreenRuntime.js` is centered on collaborative virtual-screen
+  broadcasting, placement, and transport state
+- `codexrCollaborationRuntime.js` is centered on room/session signaling,
+  remote presence, and synchronized collaboration state
+
+Those are interesting generic ideas, but they do not beat HyperTwist's current
+retained owners for the things that actually matter in-scope:
+
+- `pmndrs/xr` already covers the retained browser/XR runtime reference side
+- `screenpipe/screenpipe` already covers retained capture/history reference
+  value
+- `PostHog/posthog` already covers retained instrumentation/session-control
+  reference value
+- `remotion-dev/remotion` already covers retained export/explainer reference
+  value
+
+So `CodeXR` has no surviving unique HyperTwist slice after the later canon was
+sharpened.
+
+## Operational result
+
+Keep `CodeXR` as:
+
+- historical reference only
+- restrictive custody only
+- inactive for HyperTwist implementation planning
+
+Do not keep `CodeXR` as:
+
+- an active retained benchmark
+- a future clean-room row
+- a generic XR collaboration next step
+- a donor-style implementation candidate
+
+## Propagation answer
+
+The current board, tracker, handoff, and manifest discard posture remains
+correct.
+
+This note exists only to make that closure explicit and source-backed, so the
+row no longer depends on packet-era discard prose alone.
diff --git a/docs/REPO_LICENSE_TRACKING.md b/docs/REPO_LICENSE_TRACKING.md
index ca81d40..a679a00 100644
--- a/docs/REPO_LICENSE_TRACKING.md
+++ b/docs/REPO_LICENSE_TRACKING.md
@@ -1510,12 +1510,16 @@ Source basis:
 - `C:\Workspaces\HyperTwist\mirrors\restrictive\aMonteSl\CodeXR\src\servers\runtime\multiServerLauncher.ts`
 - `C:\Workspaces\HyperTwist\mirrors\restrictive\aMonteSl\CodeXR\templates\components\codexr\virtual-screen\virtualScreenRuntime.js`
 - `C:\HyperTwist\docs\HYPERTWIST_PHASE_0R_PACKET_0R_E_EVALUATION_2026-05-13.md`
+- `C:\HyperTwist\docs\HYPERTWIST_CODEXR_OFF_DOMAIN_XR_COLLABORATION_DISCARD_CONFIRMATION_RECONCILIATION_2026-05-27.md`
 
 Approved working posture:
 
 - do not schedule donor, clean-room, or implementation work from this row
 - if later XR collaboration ideas are compared historically, keep that comparison conceptual and bounded
 - the active retained set should rely on already-kept XR/runtime/capture rows instead
+- discard-confirmed on `2026-05-27`: no surviving unique HyperTwist lane
+  remains above retained `pmndrs/xr`, `screenpipe/screenpipe`,
+  `PostHog/posthog`, and `remotion-dev/remotion`
 
 ### `MathewKJ2048/Rubiks-cube-simulator`