Backfill drei reference provenance

This commit is contained in:
axiomlogicnexus 2026-05-27 17:58:39 +02:00
parent 64e4bd4262
commit bf34873f53
3 changed files with 121 additions and 3 deletions

View file

@ -402,14 +402,15 @@ reference side is now explicit too, and the `pmndrs/xr` XR session and
immersive-interaction reference side is now explicit too, and the
`pmndrs/uikit` world-anchored spatial UI reference side is now explicit too,
and the `pmndrs/postprocessing` browser post-processing and effect-boundary
reference side is now explicit too.
reference side is now explicit too, and the `pmndrs/drei` helper-stack and
utility reference side is now explicit too.
The next clean bounded move is a source-backed pass on the remaining
repo-backed reference-incorporation families whose hierarchy or canon
follow-through is still only implicit in
`hypertwist-reference-incorporation-targets.json`, starting with
`pmndrs/drei` if you want the adjacent helper-stack and utility reference side
closed to the same standard.
`pmndrs/zustand` if you want the adjacent state, gesture, and motion reference
side closed to the same standard.
For the readable all-rows follow-up board that pairs this audit with the reset schedule, use:

View file

@ -0,0 +1,116 @@
# HyperTwist drei 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
`pmndrs/drei`.
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 `pmndrs/drei` reference target reopen already landed
first-party browser helper-stack and utility 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 `pmndrs/drei` 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-helper-reference-page-stack`
- `SurfaceType`: `browser-spatial-helper-reference`
- `IncorporationChannel`: `browser-spatial-helper-stack`
- `TargetAssetFamily`: `helper-note`
Important adjacent fact:
- this target preserves scissored view embedding, HTML overlay bridging, XR
controller-model helpers, and motion-friendly math semantics already enforced
by the landed lane
- it stays subordinate to the broader landed browser spatial owner trio and
does not absorb the adjacent `zustand` state-motion or `postprocessing`
effect-boundary reference slices
## Slice-local verdict
| Slice | Primary authority | Secondary value kept | Result |
|---|---|---|---|
| First-party browser helper-stack and utility integration implementation | first-party current code plus landed `Phase 3R-F` packet | retained `pmndrs/drei` reference target stays a subordinate provenance-grounding surface | unchanged live implementation owner |
| Rewritten helper-stack and utility grounding | `pmndrs/drei` retained permissive lane | factual view embedding, HTML overlay, XR controller-model helper, and motion-friendly utility 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 helper-demo wording, donor example framing, donor sample-shell
assumptions, or a silent upstream private fork.
The checked target explicitly requires:
- preserving bounded helper-stack, overlay, controller-helper, and utility
semantics
- rewriting donor helper-demo wording, donor example framing, and donor
sample-shell assumptions
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/zustand` state-motion slice
- the adjacent `pmndrs/postprocessing` effect-boundary slice
- any broader browser app-shell or helper-demo ownership posture
## Current exact grounded role
`pmndrs/drei` currently grounds one live rewritten first-party
contract/reference target for `Browser 3D and XR Support`:
- browser spatial helper and utility stack
This target preserves bounded browser helper-stack 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 `pmndrs/drei` reference-incorporation side is now explicit:
- `1` rewritten first-party contract/reference target
- it remains inside the landed `Phase 3R-F` browser spatial lane
- helper-stack, overlay, controller-helper, and utility grounding stay
explicit
This closes the `pmndrs/drei` reference side without reopening product code.

View file

@ -144,6 +144,7 @@ Do not collapse those three tiers into one undifferentiated "features" voice.
| Rewritten browser XR session and immersive-interaction grounding | Implemented now | `pmndrs/xr` retained permissive lane + first-party current code | Current live `Browser 3D and XR Support` reference side includes one rewritten first-party target grounded in retained `pmndrs/xr`: the browser XR session and immersive interaction contract. This does not displace the landed `Phase 3R-F` first-party browser spatial owner trio or absorb the adjacent `three.js` scene substrate and `react-three-fiber` renderer-bridge slices. |
| Rewritten world-anchored spatial UI grounding | Implemented now | `pmndrs/uikit` retained permissive lane + first-party current code | Current live `Browser 3D and XR Support` reference side includes one rewritten first-party target grounded in retained `pmndrs/uikit`: browser spatial UI and world-anchored controls. This does not displace the landed `Phase 3R-F` first-party browser spatial owner trio or absorb the adjacent `postprocessing` effect-boundary and `drei` helper-stack slices. |
| Rewritten browser post-processing and effect-boundary grounding | Implemented now | `pmndrs/postprocessing` retained permissive lane + first-party current code | Current live `Browser 3D and XR Support` reference side includes one rewritten first-party target grounded in retained `pmndrs/postprocessing`: the browser post-processing and effect boundary. This does not displace the landed `Phase 3R-F` first-party browser spatial owner trio or absorb the adjacent `drei` helper-stack and `uikit` spatial-UI slices. |
| Rewritten browser helper-stack and utility grounding | Implemented now | `pmndrs/drei` retained permissive lane + first-party current code | Current live `Browser 3D and XR Support` reference side includes one rewritten first-party target grounded in retained `pmndrs/drei`: the browser spatial helper and utility stack. This does not displace the landed `Phase 3R-F` first-party browser spatial owner trio or absorb the adjacent `zustand` state-motion and `postprocessing` effect-boundary slices. |
## Feature families