# HyperTwist Phase 6R-M HactarCE/Hyperspeedcube stats-shape and solve-record preparation packet

Created on `2026-05-22`

## Status

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

- stats-shape and solve-record boundary

It is not:

- puzzle-definition DSL authoring
- a whole `Hyperspeedcube` runtime transplant
- a donor solve-summary or leaderboard UI packet
- a donor analytics dashboard packet
- a donor publication or remote-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_L_HYPERSPEEDCUBE_REPLAY_VERIFICATION_IMPLEMENTATION_PACKET_2026-05-22.md`

Retained owner:

- `HactarCE/Hyperspeedcube`

Retained row remainder before this packet:

- puzzle-definition DSL boundary
- stats-shape and solve-record contract

## Source-backed control result

The controlling donor seam is narrower than the whole row:

- `crates/hyperstats/src/lib.rs`
- `crates/hyperspeedcube/src/gui/modals/solve_summary.rs`
- `crates/hyperspeedcube_cli_types/src/verification.rs`

Why this wins as the next slice:

- the retained catalog, notation, replay-log serialization, and replay-verification contracts are
  already landed and stable
- the donor source isolates a narrow per-puzzle PB database and solve-record qualifier seam above
  the already landed verification types
- the donor PB categories are narrower than HyperTwist's already landed analytics and publication
  owners
- solve-summary qualifier flow provides bounded evidence for `blind`, `used_filters`, and
  `used_macros` without transferring donor UI or remote-service ownership
- puzzle-definition 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
- retained package references for:
  - the donor stats DB source
  - the donor solve-summary qualifier source
- one bounded stats-shape contract
- one bounded solve-record 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-M`:

- puzzle-definition DSL ownership
- broader analytics dashboard ownership
- publication or leaderboard ownership
- donor solve-summary UI shell ownership
- donor desktop shell or host filesystem ownership

## Queue effect

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

- source-backed `Phase 6R-N` `HactarCE/Hyperspeedcube` puzzle-definition DSL
  preparation/control pass

Keep the later widening guards visible:

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