diff --git a/docs/HT_REPO_INCORPORATION_AUDIT_2026-05-11.md b/docs/HT_REPO_INCORPORATION_AUDIT_2026-05-11.md index 1f26fa3..3741fb6 100644 --- a/docs/HT_REPO_INCORPORATION_AUDIT_2026-05-11.md +++ b/docs/HT_REPO_INCORPORATION_AUDIT_2026-05-11.md @@ -394,14 +394,15 @@ compliance reference side is now explicit too. The `met4citizen/TalkingHead` embodied companion and narration reference side is now explicit too, and the `apache/echarts` analytics and report reference -side is now explicit too. +side is now explicit too, and the `Hypercubers/hypercubing.xyz` knowledge, +taxonomy, and leaderboard/report 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 -`Hypercubers/hypercubing.xyz` if you want the adjacent knowledge, -leaderboard/report, and taxonomy reference side closed to the same standard. +`mrdoob/three.js` if you want the adjacent browser scene, renderer, and +render-loop reference side closed to the same standard. For the readable all-rows follow-up board that pairs this audit with the reset schedule, use: diff --git a/docs/HYPERTWIST_HYPERCUBING_XYZ_REFERENCE_INCORPORATION_PROVENANCE_BOARD_2026-05-27.md b/docs/HYPERTWIST_HYPERCUBING_XYZ_REFERENCE_INCORPORATION_PROVENANCE_BOARD_2026-05-27.md new file mode 100644 index 0000000..be8283a --- /dev/null +++ b/docs/HYPERTWIST_HYPERCUBING_XYZ_REFERENCE_INCORPORATION_PROVENANCE_BOARD_2026-05-27.md @@ -0,0 +1,138 @@ +# HyperTwist hypercubing.xyz 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 +`Hypercubers/hypercubing.xyz`. + +It closes the source-specific reference side that remained implicit after the +landed `Phase 3R-B` packet and the broader live-lane audit. + +It answers one narrow question: + +- do the live `Hypercubers/hypercubing.xyz` reference targets reopen already + landed first-party hypercubing knowledge, notation, progression, software + matrix, and leaderboard/report 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_B_HYPERCUBING_XYZ_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\hypercubing-xyz-reference-pages.jsonl` + +## Counts confirmed from current first-party materialization + +Current live `Hypercubers/hypercubing.xyz` reference-incorporation targets: + +- `4` total rewritten reference targets +- all `4` stay inside the already-landed `Phase 3R-B` bounded lane + +Exact surfaces: + +1. `reference/hypercubing-xyz-course-reference-page-progression` + - `SurfaceType`: `course-reference` + - `TrackTitle`: `Hypercubing Progression` + - `IncorporationChannel`: `course-reference-supplement` + - `TargetAssetFamily`: `reference-page` +2. `reference/hypercubing-xyz-notation-reference-page-cell-turning-hypercubes` + - `SurfaceType`: `notation-reference` + - `TrackTitle`: `Hypercubing Notation` + - `IncorporationChannel`: `notation-reference-supplement` + - `TargetAssetFamily`: `glossary-page` +3. `reference/hypercubing-xyz-tool-reference-page-software-matrix` + - `SurfaceType`: `tool-reference` + - `TrackTitle`: `Hypercubing Software` + - `IncorporationChannel`: `feature-reference` + - `TargetAssetFamily`: `tool-note` +4. `reference/hypercubing-xyz-community-reference-page-leaderboards` + - `SurfaceType`: `community-reference` + - `TrackTitle`: `Hypercubing Leaderboards` + - `IncorporationChannel`: `community-reference-supplement` + - `TargetAssetFamily`: `leaderboard-note` + +Important adjacent fact: + +- all four targets preserve progression ordering, notation grammar, + software-comparison taxonomy, and leaderboard display-rule semantics already + enforced by the landed lane +- these targets stay in the knowledge/reference family and do not widen into + runtime simulation, solver execution, timer execution, or host-shell + ownership + +## Slice-local verdict + +| Slice | Primary authority | Secondary value kept | Result | +|---|---|---|---| +| First-party hypercubing knowledge, notation, progression, software matrix, and leaderboard/report implementation | first-party current code plus landed `Phase 3R-B` packet | retained `Hypercubers/hypercubing.xyz` reference targets stay subordinate provenance-grounding surfaces | unchanged live implementation owner | +| Rewritten progression, notation, and software-matrix grounding | `Hypercubers/hypercubing.xyz` retained permissive lane | factual stage order, prerequisite logic, notation grammar, and software-capability taxonomy are preserved while prose remains first-party | unchanged retained reference-grounding surface beneath first-party contracts | +| Rewritten leaderboard conventions grounding | `Hypercubers/hypercubing.xyz` retained permissive lane | event naming, format semantics, relative-date posture, and solver/program-badge conventions stay explicit in first-party notes | unchanged bounded community-reference surface | + +## Why no product-code reopening is required + +The live surfaces here are already rewritten first-party targets, not copied +donor docs, donor site shell, donor HTML output, or a silent upstream private +fork. + +The checked targets explicitly require: + +- preserving bounded progression ordering, notation grammar, software + comparison, and leaderboard-contract semantics +- rewriting page titles, donor instructional prose, donor-specific examples, + donor presentation formatting, and donor HTML or site-shell output + +That means the retained surfaces are provenance and factual grounding, not +donor site or runtime ownership. + +So this pass does not reopen: + +- the closed `Phase 3R-B` first-party knowledge-reference lane +- any higher-dimensional runtime, topology, or simulation owner lane +- any timer, recognition, or solver-execution owner lane +- any host application shell or static-site architecture ownership posture + +## Current exact grounded role + +`Hypercubers/hypercubing.xyz` currently grounds four live rewritten first-party +contract/reference targets: + +- hypercubing progression ladder +- cell-turning hypercube notation +- hypercubing software matrix +- hypercubing leaderboard conventions + +These targets preserve bounded hypercubing knowledge 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 `Hypercubers/hypercubing.xyz` reference-incorporation side is now +explicit: + +- `4` rewritten first-party contract/reference targets +- all `4` remain inside the landed `Phase 3R-B` knowledge-reference lane +- progression, notation, software-matrix, and leaderboard/report grounding stay + explicit + +This closes the `Hypercubers/hypercubing.xyz` reference side without reopening +product code. diff --git a/docs/v6_5_deep_manual_pack/HyperTwist/FEATURE_REGISTRY.md b/docs/v6_5_deep_manual_pack/HyperTwist/FEATURE_REGISTRY.md index a1c6a12..0c7404f 100644 --- a/docs/v6_5_deep_manual_pack/HyperTwist/FEATURE_REGISTRY.md +++ b/docs/v6_5_deep_manual_pack/HyperTwist/FEATURE_REGISTRY.md @@ -210,6 +210,7 @@ repo. | 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. | +| Rewritten hypercubing progression, notation, software-matrix, and leaderboard-reference grounding | Implemented now | `Hypercubers/hypercubing.xyz` retained permissive lane + first-party current code | Current live hypercubing reference side includes four rewritten first-party targets grounded in retained `hypercubing.xyz`: progression ladder, cell-turning hypercube notation, software matrix, and leaderboard conventions. This does not displace the landed `Phase 3R-B` first-party knowledge-reference owner or widen into runtime simulation, timer execution, recognition, solver execution, or host-shell ownership. | | 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. | ### 5. Publication, leaderboard, entitlement, and social training