# HyperTwist Phase 6R-K HactarCE/Hyperspeedcube notation and serialization preparation packet

Created on `2026-05-22`

## Status

- first-party HyperTwist packet
- source-backed bounded permissive `Phase 6R-K` 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:

- notation and replay-log serialization boundary

It is not:

- puzzle-definition DSL authoring
- replay verification
- stats-shape widening
- a donor move-input UI packet
- a donor desktop shell or whole-app runtime transplant

## 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_A_HYPERSPEEDCUBE_PUZZLE_CATALOG_IMPLEMENTATION_PACKET_2026-05-20.md`

Retained owner:

- `HactarCE/Hyperspeedcube`

Retained row remainder before this packet:

- puzzle-definition DSL boundary
- notation grammar and serialization 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/hypuz_notation/src/unspanned.rs`
- `crates/hypuz_notation/src/spanned.rs`
- `crates/hypuz_notation/src/parse.rs`
- `crates/hyperpuzzle_log/src/lib.rs`
- `crates/hyperspeedcube/src/app.rs`

Why this wins as the next slice:

- the retained catalog contract is already landed and stable
- notation parse/format and replay-log serialization are adjacent retained runtime-anchor seams
- replay verification still depends on a later product-owned verification contract
- DSL authoring is broader than the current safe widening budget
- stats-shape is still a separate downstream solve-record lane

## Implementation target

The implementation packet may land:

- a first-party `Hyperspeedcube` reference-bundle contract
- package references for retained notation and log-serialization donor files
- one bounded notation contract
- one bounded replay-log serialization boundary
- one bounded donor-attribution boundary
- runtime-library accessors and package-checklist export
- focused automation coverage

## Explicit non-goals

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

- puzzle-definition DSL ownership
- replay verification ownership
- stats-shape ownership
- move-input or editor shell ownership
- file-dialog or donor desktop shell ownership

## Queue effect

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

- source-backed `Phase 6R-L` `HactarCE/Hyperspeedcube` replay verification preparation/control pass

Keep the later widening guards visible:

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