# HyperTwist SpeedCubeDB Reference Incorporation Provenance Board - 2026-05-27

## Status

This document is the source-backed provenance and hierarchy note for the live
retained-web-content reference-incorporation side currently materialized from
`SpeedCubeDB`.

It closes the adjacent surface that remained after the deck-backed retained web
content pass.

It answers one narrow question:

- do the live `SpeedCubeDB` reference targets reopen already landed
  first-party training/coaching or knowledge/runtime implementation, or do they
  instead need a reference-side provenance-board 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_TRAINING_CATALOG_RETAINED_WEB_CONTENT_PROVENANCE_BOARD_2026-05-27.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\httrack-retained-reference-pages.jsonl`

## Counts confirmed from current first-party materialization

Current live `SpeedCubeDB` reference-incorporation targets:

- `2` total rewritten reference targets
- both are under `Advanced 3x3 Systems`
- both are for `speedcubedb-root`

Exact surfaces:

1. `reference/speedcubedb-course-reference-page-speedcubedb-root`
   - `SurfaceType`: `course-reference`
   - `IncorporationChannel`: `course-reference-supplement`
   - `TargetAssetFamily`: `reference-page`
2. `reference/speedcubedb-tool-reference-page-speedcubedb-root`
   - `SurfaceType`: `tool-reference`
   - `IncorporationChannel`: `feature-reference`
   - `TargetAssetFamily`: `tool-note`

Important adjacent fact:

- current live `CubingApp` reference-incorporation target count is `0`

## Slice-local verdict

| Slice | Primary authority | Secondary value kept | Result |
|---|---|---|---|
| First-party rewritten knowledge/reference targets and live training-shell/runtime ownership | first-party current code and rewritten reference layer | retained `SpeedCubeDB` reference targets stay subordinate provenance-grounding surfaces | unchanged live implementation owner |
| Broad advanced and multi-puzzle retained deck corpus grounding | `SpeedCubeDB` retained web content | already handled in the retained web-content deck provenance board | unchanged retained broad deck-corpus ground |
| Rewritten advanced `3x3` course-reference and tool-reference grounding for the `SpeedCubeDB` root surface | `SpeedCubeDB` retained web content | factual method/software semantics are preserved while prose remains first-party | unchanged retained reference-grounding surface beneath first-party targets |

## Why no product-code reopening is required

The live surfaces here are already rewritten first-party targets, not copied
donor pages.

The checked targets explicitly require:

- preserving topic scope, page role, and factual software/method semantics
- rewriting page title and all instructional/reference prose

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

So this pass does not reopen:

- training-session runtime
- review-plan or coaching orchestration
- the broader imported deck-corpus hierarchy
- the first-party knowledge/reference bundle

## Current exact grounded role

`SpeedCubeDB` currently grounds two live rewritten reference targets for the
`Advanced 3x3 Systems` family:

- a course-reference supplement for the `Speedcubedb Root` surface
- a feature-reference tool note for the same root surface

These remain narrower than the already-landed `185`-deck corpus grounding from
the deck side and narrower than the first-party knowledge/reference shell that
consumes them.

`CubingApp` currently contributes no live rewritten reference targets on this
side, so there is no parallel adjunct reference family to backfill here.

## 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 `SpeedCubeDB` reference-incorporation side is now explicit:

- `2` rewritten first-party reference targets
- both grounded in retained `SpeedCubeDB` web content
- both beneath the first-party knowledge/reference shell

This closes the adjacent reference side of the retained web-content provenance
sequence without reopening product code.
