# HyperTwist Phase 6R-M1 first-party memory contracts and ledger preparation packet

Created on `2026-05-28`

## Status

- first-party HyperTwist packet
- source-backed `Phase 6R-M1` preparation/control slice

## Purpose

This packet scopes the first bounded first-party memory implementation slice
under the canonical `Memory Lanes` doctrine.

The granted slice is:

- first-party memory contracts and ledger only

It is not:

- a broad memory federation packet
- a chronicle/session-grouping packet
- a continuity/resume packet
- a recall/history-search packet
- a shared-context widening packet
- a cognitive fact-extraction packet
- a knowledge-promotion or user-notes packet
- a compact reducer/digest packet

## Current authority basis

This control pass stands on:

- `docs/ops/HYPERTWIST_MEMORY_LANE_AUTHORITY_AND_PHASE_IMPLEMENTATION_DOCTRINE_2026-05-21.md`
- `docs/ops/HYPERTWIST_CONTINUITY_LATTICE_AND_CONTEXT_ASSEMBLY_PROFILE_DOCTRINE_2026-05-23.md`
- `docs/ops/HYPERTWIST_IMPLEMENTATION_PHASE_1_KICKOFF.md`
- `docs/v6_5_deep_manual_pack/HyperTwist/ARCHITECTURE.md`
- `docs/v6_5_deep_manual_pack/HyperTwist/FEATURE_REGISTRY.md`
- `docs/v6_5_deep_manual_pack/HyperTwist/PROVENANCE_AND_TRUST_MODEL.md`
- `docs/VECTORSHELL_MEMORY_SYSTEM_IMPORT_AUTHORITY_FOR_HYPERTWIST_2026-05-25.md`

The preserved owners do not change here:

- first-party HyperTwist remains the top-level owner for live memory-lane
  contracts and memory-ledger product surfaces
- current training, replay, coaching, and repository code remains the raw
  evidence substrate beneath this packet
- the VectorShell memory doctrine remains the external synchronization
  entrypoint and authority map, not a frozen imported implementation

## Granted family

The bounded `Phase 6R-M1` slice may land:

1. lane ids and lane contracts for the canonical first-party `Memory Lanes`
2. memory entity ids for current authoritative, semi-authoritative, and
   derived product-memory objects over the live training repository state
3. provenance-link structures and ledger-visible parentage for non-raw memory
   entities
4. authoritative-versus-derived flags and counts
5. settings keys, feature gates, and preset-backed retention-profile defaults
   for:
   - `Economic-Retention Mode`
   - `Max-Retention Mode`
6. bounded sample contract and serialization coverage for the `6R-M1` ledger
   surface

The packet must stay out of:

- chronicle grouping and resume-pack ownership
- explicit remember/recall search ownership
- scoped shared-context widening
- cognitive extraction, contradiction handling, or supersession
- curated knowledge-promotion flows
- user-authored notes
- compact reducers, digests, or reduced-context packets

## Proposed implementation shape

Land the narrower first-party boundary through:

- new memory types for:
  - lane contracts
  - feature gates
  - provenance links
  - entity descriptors
  - retention profiles
  - bounded ledger state
- a first-party memory-core library that derives the ledger from current
  repository state
- sample-contract helpers for:
  - sample memory ledger creation
  - JSON serialization
  - JSON deserialization
- focused automation in:
  - `HyperTwistMemoryPhase6RM1LedgerContractTest.cpp`

## Validation target

Validate with:

- Unreal build for `UnrealHyperTwistEditor Win64 Development`
- focused automation:
  - `HyperTwist.FirstParty.Memory.Phase6R.M1.LaneContracts`
  - `HyperTwist.FirstParty.Memory.Phase6R.M1.DerivedProvenance`
  - `HyperTwist.FirstParty.Memory.Phase6R.M1.SerializationRoundTrip`

## Queue effect

If this packet lands cleanly, HyperTwist memory no longer remains only a
retained doctrine surface at the contract layer. A first bounded live
first-party memory-ledger seam becomes current product truth.

If later memory implementation continues:

- the next clean move is `Phase 6R-M2`
- do not reopen `6R-M1` as one broad "memory packet"

