# HyperTwist google/model-viewer 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 the landed
`google/model-viewer` browser viewer lane.

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

It answers one narrow question:

- do the live root-lane `google/model-viewer` reference targets reopen already
  landed first-party browser viewer, compact editor, export, renderer
  comparison, and docs-boundary implementation, or do they 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_D_MODEL_VIEWER_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\google-model-viewer-reference-pages.jsonl`

## Counts confirmed from current first-party materialization

Current live root-lane `google/model-viewer` reference-incorporation targets:

- `5` total rewritten reference targets
- all `5` are under `Browser Viewer and Asset QA`
- all `5` stay inside the already-landed `Phase 3R-D` bounded lane

Exact surfaces:

1. `reference/google-model-viewer-browser-viewer-reference-page-embed-contract`
   - `SurfaceType`: `browser-viewer-reference`
   - `IncorporationChannel`: `viewer-embed-contract`
   - `TargetAssetFamily`: `support-widget`
2. `reference/google-model-viewer-browser-editor-reference-page-compact-editor`
   - `SurfaceType`: `browser-editor-reference`
   - `IncorporationChannel`: `viewer-editor-contract`
   - `TargetAssetFamily`: `editor-panel`
3. `reference/google-model-viewer-browser-export-reference-page-snippet-and-export`
   - `SurfaceType`: `browser-export-reference`
   - `IncorporationChannel`: `viewer-export-contract`
   - `TargetAssetFamily`: `export-note`
4. `reference/google-model-viewer-renderer-comparison-reference-page-fidelity`
   - `SurfaceType`: `renderer-comparison-reference`
   - `IncorporationChannel`: `renderer-comparison-contract`
   - `TargetAssetFamily`: `regression-note`
5. `reference/google-model-viewer-docs-boundary-reference-page-demo-separation`
   - `SurfaceType`: `docs-boundary-reference`
   - `IncorporationChannel`: `docs-demo-boundary`
   - `TargetAssetFamily`: `docs-boundary-note`

Important adjacent fact:

- the five targets preserve embeddable viewer lifecycle, camera and framing,
  hotspot/editor inspection, snippet/export posture, renderer-fidelity
  comparison, and docs/demo separation semantics already enforced by the
  landed lane
- subordinate sidecars such as `space-opera`, `modelviewer.dev`, and
  `render-fidelity-tools` stay explicit support-only contributors beneath the
  landed `google/model-viewer` owner
- `google/model-viewer/packages/shared-assets` remains a separate already
  explicit boundary-sensitive fixture lane and is not folded back into this
  root pass

## Slice-local verdict

| Slice | Primary authority | Secondary value kept | Result |
|---|---|---|---|
| First-party browser viewer, compact editor, export, renderer-comparison, and docs-boundary implementation | first-party current code plus landed `Phase 3R-D` packet | retained root `google/model-viewer` reference targets stay subordinate provenance-grounding surfaces | unchanged live implementation owner |
| Rewritten viewer/embed, editor, export, renderer-comparison, and docs-boundary grounding | `google/model-viewer` retained permissive lane | factual viewer lifecycle, inspection/editor, snippet/export, fidelity-comparison, and docs/demo-boundary semantics are preserved while prose remains first-party | unchanged retained reference-grounding surface beneath first-party contracts |
| Subordinate sidecar contribution boundaries | `google/model-viewer` retained permissive lane | `space-opera`, `modelviewer.dev`, and `render-fidelity-tools` stay explicit support-only contributors beneath the landed viewer owner | unchanged subordinate support posture |

## Why no product-code reopening is required

The live surfaces here are already rewritten first-party targets, not copied
donor docs, donor demo shell, donor site framing, or a silent upstream private
fork.

The checked targets explicitly require:

- preserving bounded viewer/embed, compact-editor, snippet/export,
  renderer-comparison, and docs/demo-boundary semantics
- rewriting donor docs and demo copy, donor shell assumptions, donor
  navigation framing, donor tutorial wording, and donor workflow text

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

So this pass does not reopen:

- the closed `Phase 3R-D` first-party browser viewer lane
- the separate already-explicit `Phase 4R-C` shared-assets lane
- any separate live-lane claim for `space-opera`, `modelviewer.dev`, or
  `render-fidelity-tools`
- the adjacent `KhronosGroup/glTF-Sample-Viewer` standards-aware QA lane

## Current exact grounded role

The root `google/model-viewer` lane currently grounds five live rewritten
first-party contract/reference targets for `Browser Viewer and Asset QA`:

- browser viewer embed contract
- compact browser editor and inspection
- snippet and export surface
- renderer comparison and fidelity
- docs and demo separation boundary

These targets preserve bounded browser-viewer 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 root `google/model-viewer` reference-incorporation side is now
explicit:

- `5` rewritten first-party contract/reference targets
- all `5` remain inside the landed `Phase 3R-D` browser viewer lane
- embed, editor, export, renderer-comparison, and docs/demo-boundary grounding
  stay explicit

This closes the root `google/model-viewer` reference side without reopening
product code.
