Backfill Superliminal reference provenance

This commit is contained in:
axiomlogicnexus 2026-05-27 15:45:34 +02:00
parent 607b0d0705
commit 08e91aa970
3 changed files with 157 additions and 6 deletions

View file

@ -381,12 +381,15 @@ That does not make them legally cleared or deeply audited. It only means this pa
## Recommended next implementation slice
The retained-web-content deck and reference provenance-board passes for the
additional live non-71 surfaces are now complete. The next clean bounded move
is not another trainer-shell widening by default; it is a source-backed pass on
the remaining live non-repo reference-incorporation surfaces still grouped only
implicitly in `hypertwist-reference-incorporation-targets.json`, starting with
`superliminal.com` and `Superliminal Wiki` if you want the non-repo reference
side closed to the same standard.
additional live non-71 surfaces are now complete, including `SpeedCubeDB`,
`CubingApp`, `superliminal.com`, and `Superliminal Wiki`.
The next clean bounded move is not another retained-web-content provenance pass
by default. If this audit line continues, shift to 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`, instead of reopening the
closed retained-web-content reference side.
For the readable all-rows follow-up board that pairs this audit with the reset schedule, use:

View file

@ -0,0 +1,146 @@
# HyperTwist Superliminal 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
`superliminal.com` and `Superliminal Wiki`.
It closes the remaining non-repo retained-web-content reference side that
stayed implicit after the retained deck-corpus pass and the adjacent
`SpeedCubeDB` reference pass.
It answers one narrow question:
- do the live `superliminal.com` and `Superliminal Wiki` reference targets
reopen already landed first-party knowledge/runtime 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_TRAINING_CATALOG_RETAINED_WEB_CONTENT_PROVENANCE_BOARD_2026-05-27.md`
- `C:\HyperTwist\docs\HYPERTWIST_SPEEDCUBEDB_REFERENCE_INCORPORATION_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 retained-web-content reference-incorporation targets:
- `7` total rewritten reference targets
- `6` targets grounded in `superliminal.com`
- `1` target grounded in `Superliminal Wiki`
Exact surfaces:
1. `reference/superliminal-com-course-reference-page-magic-cube-4d-solution`
- `SurfaceType`: `course-reference`
- `TrackTitle`: `Hypercubing Software Manuals`
- `TargetAssetFamily`: `reference-page`
2. `reference/superliminal-com-software-manual-reference-page-magic-cube-4d`
- `SurfaceType`: `software-manual`
- `TrackTitle`: `Hypercubing Software Manuals`
- `TargetAssetFamily`: `manual-page`
3. `reference/superliminal-com-software-manual-reference-page-magic-cube-7d`
- `SurfaceType`: `software-manual`
- `TrackTitle`: `Hypercubing Software Manuals`
- `TargetAssetFamily`: `manual-page`
4. `reference/superliminal-com-software-manual-reference-page-magic-hyperbolic-tile`
- `SurfaceType`: `software-manual`
- `TrackTitle`: `Hypercubing Software Manuals`
- `TargetAssetFamily`: `manual-page`
5. `reference/superliminal-com-software-manual-reference-page-magic-puzzle-ultimate`
- `SurfaceType`: `software-manual`
- `TrackTitle`: `Hypercubing Software Manuals`
- `TargetAssetFamily`: `manual-page`
6. `reference/superliminal-com-software-manual-reference-page-magic-simplex-5d`
- `SurfaceType`: `software-manual`
- `TrackTitle`: `Hypercubing Software Manuals`
- `TargetAssetFamily`: `manual-page`
7. `reference/superliminal-wiki-historical-reference-page-hypercubing-reference`
- `SurfaceType`: `historical-reference`
- `TrackTitle`: `Hypercubing Reference`
- `TargetAssetFamily`: `history-note`
Important adjacent fact:
- the retained-web-content reference side now has no remaining unbackfilled
non-repo source family after this pass
## Slice-local verdict
| Slice | Primary authority | Secondary value kept | Result |
|---|---|---|---|
| First-party rewritten knowledge/reference targets and live knowledge/runtime ownership | first-party current code and rewritten reference layer | retained `superliminal.com` and `Superliminal Wiki` targets stay subordinate provenance-grounding surfaces | unchanged live implementation owner |
| Rewritten higher-dimensional software-manual and solution-reference grounding | `superliminal.com` retained web content | factual software, puzzle-family, and method/workflow semantics are preserved while prose remains first-party | unchanged retained reference-grounding surface beneath first-party targets |
| Rewritten historical hypercubing context grounding | `Superliminal Wiki` retained web content | factual historical and conceptual hypercubing context is preserved while prose remains first-party | unchanged retained historical-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 or method semantics
- rewriting page title and all instructional/reference prose
That means the retained surfaces are provenance and factual grounding, not
donor shell ownership.
So this pass does not reopen:
- the first-party knowledge/reference bundle
- first-party higher-dimensional runtime owners
- the retained deck-corpus grounding already assigned to `SpeedCubeDB` and
`CubingApp`
- any donor manual or historical wiki shell as a live product owner
## Current exact grounded role
`superliminal.com` currently grounds six live rewritten first-party manual and
reference targets:
- one `Magic Cube 4D` course-reference supplement
- five software-manual pages across `Magic Cube 4D`, `Magic Cube 7D`,
`Magic Hyperbolic Tile`, `Magic Puzzle Ultimate`, and `Magic Simplex 5D`
These targets preserve factual software, method, and workflow semantics for the
checked puzzle families while keeping all surfaced prose first-party.
`Superliminal Wiki` currently grounds one live rewritten first-party historical
reference note:
- `Hypercubing Historical Reference`
That target preserves historical and conceptual context for the hypercubing
reference side while remaining narrower than the first-party knowledge shell
that consumes it.
## 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 retained-web-content reference-incorporation side is now explicit:
- `6` rewritten first-party `superliminal.com` manual/reference targets
- `1` rewritten first-party `Superliminal Wiki` historical-reference target
- all `7` targets remain beneath the first-party knowledge/reference shell
This closes the remaining non-repo retained-web-content reference side without
reopening product code.

View file

@ -202,6 +202,8 @@ repo.
| Retained advanced and multi-puzzle algorithm corpus grounding | Implemented now | `SpeedCubeDB` retained web content + first-party current code | Current live imported catalog breadth across advanced `3x3`, big cube, megaminx, broad pyraminx, broad skewb, and broad square-1 families remains grounded in retained `SpeedCubeDB` web content beneath the first-party rewritten course layer. This does not displace the first-party training runtime or the narrower `CubingApp` one-handed/shaped-subset adjunct. |
| Retained one-handed and shaped-subset adjunct corpus grounding | Implemented now | `CubingApp` retained web content + first-party current code | Current live imported adjunct depth across one-handed `CMLL`, Sarah-intermediate skewb triggers, pyraminx last-layer, and square-1 `CSP` / `OBL` families remains grounded in retained `CubingApp` web content beneath the first-party rewritten course layer. This does not displace the broader `SpeedCubeDB` corpus ground or the first-party training runtime. |
| Rewritten advanced `3x3` reference supplement and tool-reference grounding | Implemented now | `SpeedCubeDB` retained web content + first-party current code | Current live `Advanced 3x3 Systems` reference side includes two rewritten first-party targets grounded in retained `SpeedCubeDB` web content: one course-reference supplement and one tool-reference note for the `Speedcubedb Root` surface. This does not displace the first-party knowledge/reference shell or the broader retained `SpeedCubeDB` deck-corpus ground. |
| Rewritten hypercubing software-manual and solution-reference grounding | Implemented now | `superliminal.com` retained web content + first-party current code | Current live `Hypercubing Software Manuals` reference side includes six rewritten first-party targets grounded in retained `superliminal.com` web content: one `Magic Cube 4D` course-reference supplement plus five software-manual pages across `Magic Cube 4D`, `Magic Cube 7D`, `Magic Hyperbolic Tile`, `Magic Puzzle Ultimate`, and `Magic Simplex 5D`. This does not displace the first-party knowledge/reference shell or any first-party higher-dimensional runtime owner. |
| Rewritten hypercubing historical-reference grounding | Implemented now | `Superliminal Wiki` retained web content + first-party current code | Current live `Hypercubing Reference` side includes one rewritten first-party historical-reference note grounded in retained `Superliminal Wiki` web content for the `Hypercubing Historical Reference` surface. This does not displace the first-party knowledge/reference shell or any first-party higher-dimensional runtime owner. |
| Hypercubing knowledge/reference bundle | Implemented now | landed knowledge packet + first-party consumption | Live knowledge family. |
| Curated training atlas / wiki-like memory | Deep-source grounded retained | first-party target + memory doctrine | Not yet source-grounded enough for stronger external-lane ownership. |