# Untracked Source Prototype Quarantine

Created on `2026-04-29`

## Purpose

This note records untracked prototype-style source files that were found under
`C:\HyperTwist\UnrealHyperTwist\Source\...` but were not part of the tracked
first-party runtime.

The goal is to keep the product worktree clean without losing potentially
useful exploratory code.

## Operator preference

The workflow owner wants Codex to conduct worktree cleanup work proactively, as
much as is safely possible, instead of leaving stray-file tracking to manual
memory.

For the product repo, that means Codex should usually:

- inspect unexpected untracked runtime-source files
- decide whether they are real integrated work, prototype residue, or accidental
  debris
- quarantine or document non-integrated prototypes when they do not belong in
  the live runtime tree
- aim to leave `C:\HyperTwist` with a clean worktree after the cleanup packet
  whenever that can be done without risking legitimate user work

Codex should still avoid blind destructive cleanup. If ownership or intent is
ambiguous, the safer default is to isolate and document rather than silently
discard.

## Quarantined on 2026-04-29

Original untracked paths:

- `C:\HyperTwist\UnrealHyperTwist\Source\HyperTwistCore\Public\DrillTypes.h`
- `C:\HyperTwist\UnrealHyperTwist\Source\HyperTwistTraining\Public\HyperTwistDrillManager.h`
- `C:\HyperTwist\UnrealHyperTwist\Source\HyperTwistTraining\Private\HyperTwistDrillManager.cpp`

Quarantine destination:

- `C:\HyperTwist\docs\quarantine\untracked-source-prototypes\2026-04-29\Source\HyperTwistCore\Public\DrillTypes.h`
- `C:\HyperTwist\docs\quarantine\untracked-source-prototypes\2026-04-29\Source\HyperTwistTraining\Public\HyperTwistDrillManager.h`
- `C:\HyperTwist\docs\quarantine\untracked-source-prototypes\2026-04-29\Source\HyperTwistTraining\Private\HyperTwistDrillManager.cpp`

## Why these were quarantined instead of committed into runtime

These files were not treated as live product code because:

- they existed as untracked top-level source trees outside the tracked
  `Source\UnrealHyperTwist` module surface
- no `Build.cs` files existed for `Source\HyperTwistCore` or
  `Source\HyperTwistTraining`
- exact-name search found no references outside the prototype files themselves
- the contents describe a much earlier and narrower drill-manager concept than
  the current first-party `HyperTwistTraining` stack

Operationally, they are preserved as prototype artifacts, not accepted as
integrated runtime modules.

## Reintegration rule

Do not move these files back under `Source\...` unless all of the following are
true:

1. there is a deliberate product task that needs them
2. they are reviewed against the current first-party training architecture
3. they are either reshaped into existing tracked modules or given a real
   module/build definition
4. their runtime role is explicit and not duplicative of the current owned
   `HyperTwistTraining` surfaces

## Workflow guidance

If future prototype code appears under top-level `Source\...` paths without a
real module definition or tracked task, prefer this same pattern:

1. inspect whether it is integrated or stray
2. quarantine it into `docs\quarantine\untracked-source-prototypes\<date>\...`
3. update this note with the original path and rationale

This keeps the runtime tree clean while preserving handoff context.
