# HyperTwist Phase 6R-L HactarCE/Hyperspeedcube replay verification preparation packet

Created on `2026-05-22`

## Status

- first-party HyperTwist packet
- source-backed bounded permissive `Phase 6R-L` preparation and control pass

## Purpose

This packet narrows the retained `HactarCE/Hyperspeedcube` runtime-anchor remainder to one first
bounded widening slice.

The controlled slice is:

- replay verification and solve-proof diagnostics boundary

It is not:

- puzzle-definition DSL authoring
- stats-shape widening
- a whole `Hyperspeedcube` runtime transplant
- a donor replay UI or desktop-shell packet
- a donor network-service ownership packet

## Authority basis

This preparation packet stands on:

- `docs/HYPERTWIST_PHASE_0R_PACKET_0R_A_EVALUATION_2026-05-12.md`
- `docs/HYPERTWIST_PHASE_2R_PACKET_2R_A_OWNERSHIP_AND_ACCEPTANCE_CONTRACT_2026-05-13.md`
- `docs/REPO_LICENSE_TRACKING.md`
- `docs/arch/HYPERTWIST_PHASE6R_K_HYPERSPEEDCUBE_NOTATION_SERIALIZATION_IMPLEMENTATION_PACKET_2026-05-22.md`

Retained owner:

- `HactarCE/Hyperspeedcube`

Retained row remainder before this packet:

- puzzle-definition DSL boundary
- replay-event taxonomy and verification boundary
- stats-shape and solve-record contract

## Source-backed control result

The controlling donor seam is narrower than the whole row:

- `crates/hyperpuzzle_log/src/verify.rs`
- `crates/hyperspeedcube_cli_types/src/verification.rs`
- `crates/hyperpuzzle_view/src/simulation/mod.rs`
- `crates/hyperpuzzle_view/src/replay_event.rs`

Why this wins as the next slice:

- the retained catalog, notation, and replay-log serialization contracts are already landed and
  stable
- replay verification is the next adjacent retained runtime-anchor seam above the landed
  notation/log boundary
- the donor seam already isolates verification options, replay reconstruction, timestamp proof
  routing, and solve diagnostics
- stats-shape still remains a separate downstream product-owned lane
- DSL authoring is broader than the current safe widening budget

## Implementation target

The implementation packet may land:

- an expanded first-party `Hyperspeedcube` reference-bundle contract
- package references for retained replay-verification and replay-reconstruction donor files
- one bounded replay-verification contract
- one bounded replay-verification boundary
- an updated donor-attribution boundary
- runtime-library accessors and package-checklist export
- focused automation coverage

## Explicit non-goals

Do not land in `Phase 6R-L`:

- puzzle-definition DSL ownership
- broader stats-shape ownership
- leaderboard policy ownership
- donor replay UI or desktop shell ownership
- host TSA, randomness-beacon, or network-service ownership

## Queue effect

If the bounded implementation lands cleanly, the next clean move becomes:

- source-backed `Phase 6R-M` `HactarCE/Hyperspeedcube` stats-shape and solve-record
  preparation/control pass

Keep the later widening guards visible:

- stats-shape stays separate
- DSL stays separate
- generic hyper-runtime ownership stays first-party and broader than this donor slice
