# HyperTwist Phase 6R-M3 first-party recall and shared-context preparation packet

Created on `2026-05-28`

## Status

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

## Purpose

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

The granted slice is:

- explicit remember/recall
- history search
- provenance drill-down
- scoped shared-memory rules

It is not:

- a broad memory federation packet
- a chronicle/continuity replay of `6R-M2`
- a cognitive 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/arch/HYPERTWIST_PHASE6R_M1_FIRST_PARTY_MEMORY_CONTRACTS_AND_LEDGER_IMPLEMENTATION_PACKET_2026-05-28.md`
- `docs/arch/HYPERTWIST_PHASE6R_M2_FIRST_PARTY_CHRONICLE_AND_CONTINUITY_IMPLEMENTATION_PACKET_2026-05-28.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 live owner for current recall, provenance
  drill-down, and bounded shared-context product seams
- the landed `Phase 6R-M1` ledger remains the provenance substrate beneath this
  packet
- the landed `Phase 6R-M2` chronicle/continuity layer remains the current
  open-work and history substrate beneath this packet
- 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-M3` slice may land:

1. explicit first-party recall matches over current repository-backed memory
   evidence
2. bounded history-search state over the landed `6R-M1` ledger entities and
   the landed `6R-M2` chronicle/continuity seams
3. provenance drill-down entries that stay linked to current authoritative
   parents rather than inventing silent rewritten memory
4. revocable scoped shared-context rules and projections for:
   - coach follow-up
   - replay review
   - narrow sidecar briefing
5. sample contract and JSON round-trip coverage for the `6R-M3` state

The packet must stay out of:

- contradiction handling, supersession, or confidence decay
- durable cognitive fact extraction
- 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:
  - recall matches
  - provenance drill-down entries
  - shared-context rules
  - shared-context projections
  - bounded recall/shared-context state
- a memory-core derivation function over:
  - current repository state
  - the already-landed `6R-M1` memory ledger
  - the already-landed `6R-M2` chronicle/continuity state
- sample-contract helpers for:
  - sample recall/shared-context derivation
  - JSON serialization
  - JSON deserialization
- focused automation in:
  - `HyperTwistMemoryPhase6RM3RecallSharedContextContractTest.cpp`

## Validation target

Validate with:

- Unreal build for `UnrealHyperTwistEditor Win64 Development`
- focused automation:
  - `HyperTwist.FirstParty.Memory.Phase6R.M3.RecallSearch`
  - `HyperTwist.FirstParty.Memory.Phase6R.M3.SharedContextRules`
  - `HyperTwist.FirstParty.Memory.Phase6R.M3.SerializationRoundTrip`

## Queue effect

If this packet lands cleanly, HyperTwist memory no longer stops at the
ledger-plus-chronicle seam. The bounded first-party explicit recall and scoped
shared-context layer becomes current product truth above `6R-M1` and `6R-M2`.

If later memory implementation continues:

- the next clean move is `Phase 6R-M4`
- do not reopen `6R-M3` as one broad memory packet
