# Repository Scope Correction Report

## Finding

The first `xbox-dvd-tools` commit was byte-small but responsibility-large. The
845-path tree was not acceptable merely because Git could store and clone it.

The durable issue was authority: a canonical implementation repository must not
silently combine maintained source, current emulator development, exploratory
reverse engineering, generated evidence, deprecated implementations, and PFES
institutional memory.

## Final boundary

`xbox-dvd-tools` contains maintained implementation source, canonical analyzer
and toolchain code, current validation tooling, build entry points, small
commit-coupled data, and maintained documentation.

Separate lifecycle domains:

- `mn103s-emulator`: active emulator source, tests, profiles, and runtime support;
- research repository or immutable research snapshots: probes, hunters,
  family-specific experiments, and reverse-engineering datasets;
- PFES/reference archive: historical theories, claim-review inputs, planning,
  hardware inventories, and handoffs;
- external artifact store: firmware, disc images, generated analyzer trees,
  candidate windows, traces, result archives, and validation products;
- workstation-only state: editor and machine-specific helpers.

## Correction method

1. preserve and validate the broad import;
2. audit every tracked path;
3. resolve the 27 ambiguous paths;
4. perform dependency closure against excluded paths;
5. remove 22 uncoupled legacy/ad-hoc files;
6. create a separate 115-path root candidate;
7. verify candidate bundle, Git objects, source export, and clean clone;
8. promote atomically while archiving the broad import.

No source original was deleted to obtain a cleaner Git tree.

## Representation rule

Canonical Git blobs and checked-out files are different representations when
`.gitattributes` performs end-of-line conversion. Eight `.cmd`/`.ps1` paths are
stored as LF blobs and checked out/exported as CRLF. Future integrity tooling
must identify which representation it is hashing.
