# HyperTwist zustand 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/zustand`.

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/zustand` reference target reopen already landed
  first-party browser state, gesture, and motion 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/zustand` 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-state-reference-page-stack`
   - `SurfaceType`: `browser-spatial-state-reference`
   - `IncorporationChannel`: `browser-spatial-state-motion-contract`
   - `TargetAssetFamily`: `state-motion-note`

Important adjacent fact:

- this target preserves lightweight store lifecycle, gesture composition and
  routing, spring-based motion/interpolation, and schema-driven parameter
  control semantics already enforced by the landed lane
- it stays subordinate to the broader landed browser spatial owner trio and
  does not absorb the already explicit `drei` helper-stack slice or reopen a
  broader support-cluster implementation packet

## Slice-local verdict

| Slice | Primary authority | Secondary value kept | Result |
|---|---|---|---|
| First-party browser state, gesture, and motion implementation | first-party current code plus landed `Phase 3R-F` packet | retained `pmndrs/zustand` reference target stays a subordinate provenance-grounding surface | unchanged live implementation owner |
| Rewritten state, gesture, and motion grounding | `pmndrs/zustand` retained permissive lane | factual store lifecycle, gesture-routing, spring-motion, and schema-driven control 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 playground wording, donor demo framing, donor package-marketing copy, or
a silent upstream private fork.

The checked target explicitly requires:

- preserving bounded state-store, gesture-routing, spring-motion, and
  schema-driven control semantics
- rewriting donor playground wording, donor demo framing, and donor
  package-marketing copy

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 already explicit `pmndrs/drei` helper-stack slice
- any broader browser support-cluster implementation packet
- any browser app-shell or playground ownership posture

## Current exact grounded role

`pmndrs/zustand` currently grounds one live rewritten first-party
contract/reference target for `Browser 3D and XR Support`:

- browser spatial state, gesture, and motion contract

This target preserves bounded browser state-motion 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/zustand` reference-incorporation side is now explicit:

- `1` rewritten first-party contract/reference target
- it remains inside the landed `Phase 3R-F` browser spatial lane
- state-store, gesture-routing, spring-motion, and parameter-control grounding
  stay explicit

This closes the `pmndrs/zustand` reference side without reopening product
code.
