# HyperTwist three.js Reference Incorporation Provenance Board - 2026-05-27

## Status

This document is the source-backed provenance and hierarchy note for the live
repo-backed reference-incorporation side currently materialized from
`mrdoob/three.js`.

It closes the source-specific reference side that remained implicit after the
landed `Phase 3R-F` packet and the broader live-lane audit.

It answers one narrow question:

- does the live `mrdoob/three.js` reference target reopen already landed
  first-party browser spatial scene, renderer, camera, render-loop, and WebXR
  integration implementation, or does it instead need a reference-side
  provenance-board and canon backfill

Result:

- no product-code reopening is required
- yes reference-side provenance-board and feature-canon backfill is required

## Source basis

- `C:\HyperTwist\docs\HT_REPO_INCORPORATION_AUDIT_2026-05-11.md`
- `C:\HyperTwist\docs\HYPERTWIST_PHASE_3R_PACKET_3R_F_BROWSER_SPATIAL_SUPPORT_IMPLEMENTATION_2026-05-13.md`
- `C:\HyperTwist\docs\HYPERTWIST_LIVE_LANES_SOURCE_AND_PRESERVATION_AUDIT_2026-05-13.md`
- `C:\HyperTwist\docs\REPO_LICENSE_TRACKING.md`
- `C:\HyperTwist\docs\v6_5_deep_manual_pack\HyperTwist\FEATURE_REGISTRY.md`
- `C:\HyperTwist\UnrealHyperTwist\Content\HyperTwistTraining\MaterializedCatalog\hypertwist-reference-incorporation-targets.json`
- `C:\HyperTwist\UnrealHyperTwist\Content\HyperTwistTraining\MaterializedCatalog\raw-extracts\browser-spatial-support-reference-pages.jsonl`

## Counts confirmed from current first-party materialization

Current live `mrdoob/three.js` reference-incorporation targets:

- `1` total rewritten reference target
- that target is under `Browser 3D and XR Support`
- it stays inside the already-landed `Phase 3R-F` bounded lane

Exact surface:

1. `reference/browser-spatial-scene-reference-page-stack`
   - `SurfaceType`: `browser-spatial-scene-reference`
   - `IncorporationChannel`: `browser-spatial-scene-contract`
   - `TargetAssetFamily`: `scene-contract-note`

Important adjacent fact:

- this target preserves scene and renderer lifecycle, camera and raycaster
  binding, frameloop invalidation, and WebXR-manager integration semantics
  already enforced by the landed lane
- it stays subordinate to the broader landed browser spatial owner trio and
  does not absorb the adjacent `react-three-fiber` or `xr` reference slices

## Slice-local verdict

| Slice | Primary authority | Secondary value kept | Result |
|---|---|---|---|
| First-party browser spatial scene, renderer, camera, render-loop, and WebXR-manager implementation | first-party current code plus landed `Phase 3R-F` packet | retained `mrdoob/three.js` reference target stays a subordinate provenance-grounding surface | unchanged live implementation owner |
| Rewritten browser scene and renderer-contract grounding | `mrdoob/three.js` retained permissive lane | factual scene lifecycle, camera binding, frameloop invalidation, and WebXR-manager semantics are preserved while prose remains first-party | unchanged retained reference-grounding surface beneath first-party contracts |

## Why no product-code reopening is required

The live surface here is already a rewritten first-party target, not copied
donor docs, donor editor shell, donor example chrome, or a silent upstream
private fork.

The checked target explicitly requires:

- preserving bounded browser scene, renderer, camera, render-loop, and WebXR
  manager semantics
- rewriting donor docs or demo wording, donor editor-shell framing, and donor
  example chrome

That means the retained surface is provenance and factual grounding, not donor
browser-shell ownership.

So this pass does not reopen:

- the closed `Phase 3R-F` first-party browser spatial lane
- the adjacent `pmndrs/react-three-fiber` renderer-bridge slice
- the adjacent `pmndrs/xr` XR-session slice
- any broader browser app-shell or editor ownership posture

## Current exact grounded role

`mrdoob/three.js` currently grounds one live rewritten first-party
contract/reference target for `Browser 3D and XR Support`:

- browser spatial scene and renderer contract

This target preserves bounded browser-scene semantics while keeping all
surfaced prose and shell framing first-party.

## Backfill result

### Earlier incorporation audit reopened

- `C:\HyperTwist\docs\HT_REPO_INCORPORATION_AUDIT_2026-05-11.md`

### Feature canon reopened

- `C:\HyperTwist\docs\v6_5_deep_manual_pack\HyperTwist\FEATURE_REGISTRY.md`

## Final call

The live `mrdoob/three.js` reference-incorporation side is now explicit:

- `1` rewritten first-party contract/reference target
- it remains inside the landed `Phase 3R-F` browser spatial lane
- scene lifecycle, camera binding, frameloop, and WebXR-manager grounding stay
  explicit

This closes the `mrdoob/three.js` reference side without reopening product
code.
