# Created on `2026-05-27`

## Status

`closed`

## Purpose

This note closes the remaining stale-routing gap inside the residual `Phase 2R-C` permissive cluster for:

- `NuiLab/code-vr`
- `pissang/claygl`
- `pissang/clay-viewer`

The source-backed ownership packet already kept all three rows subordinate, but the row-source pack and manifest still left them too close to straight implementation-candidate wording.

## Current judgment

- no previously landed product packet needs reopening
- no product code change is justified from this pass
- no default widening packet is open for `NuiLab/code-vr`
- the optional `3R-G` browser comparison lane remains deferred for `pissang/claygl` and `pissang/clay-viewer`

## `NuiLab/code-vr`

Retain only the narrow symbolic-to-spatial pedagogy value visible in the checked mirror:

- abstract syntax or graph structure converted into spatial layout
- parse/export/runtime separation
- language-aware spatial teaching-sidecar behavior
- experimental onboarding or code-structure pedagogy

Do not promote:

- the VR runtime shell
- the gameplay or competition shell
- the practical XR session/runtime owner role

Current live owners already cover the practical stack:

- first-party knowledge and curriculum surfaces own the current learning shell
- the landed browser spatial owner trio owns the browser-side spatial stack
- `pmndrs/xr` remains the practical XR support owner inside that browser spatial family

The older historical `Phase 6R-F` widening label is superseded for this row only, because later live product work already uses `Phase 6R-F` for the landed `SYSTRAN/faster-whisper` transcription-service packet.

Current canon should therefore use:

- `retained symbolic-to-spatial XR pedagogy lane`
- `no default widening packet open`

## `pissang/claygl` and `pissang/clay-viewer`

Retain only the optional browser comparison value visible in the checked mirrors:

- lower-level renderer, scene, camera, control, and compositor patterns from `claygl`
- compact browser viewer/editor, hotspot, animation-preview, environment, and post-effect patterns from `clay-viewer`

Do not promote:

- either repo as a browser-spatial runtime owner
- either repo as a gameplay or puzzle-renderer foundation
- either repo as a default next browser implementation packet

Current live owners already cover the practical stack:

- `mrdoob/three.js`, `pmndrs/react-three-fiber`, and `pmndrs/xr` own the landed browser spatial core
- `google/model-viewer` owns the landed browser viewer/editor and asset-QA lane

So `3R-G` remains only an optional deferred comparison lane. It should reopen only if the landed browser spatial and viewer stack leaves a real sidecar gap.

## Required canon posture

Current authority surfaces should now say all of the following consistently:

- `NuiLab/code-vr` is not a straight `Phase 3R` permissive implementation candidate
- `NuiLab/code-vr` does not own practical XR runtime behavior
- the older `6R-F` widening label for `NuiLab/code-vr` is superseded by later speech-lane use of `Phase 6R-F`
- `pissang/claygl` and `pissang/clay-viewer` remain optional browser comparison context only
- `3R-G` stays deferred unless a real browser-side gap is proven
