# PFES Roadmap

Detailed active work lives in `NEXT_WORK_PLAN.md`.

## Phase 1 — PFES foundation and knowledge preservation

**Status:** Substantially established

- Git authority and cumulative release lineage are active;
- evidence/status and retention models are established;
- historical analyzer and emulator knowledge are preserved;
- repository and artifact boundaries are explicit;
- project incubation and repository admission are now formalized.

## Phase 2 — Repository, artifact, and project infrastructure

**Status:** Canonical repositories active; incubation gate active; independent backup pending

- `pfes`, `xbox-dvd-tools`, `mn103s-emulator`, and `friidump` are canonical;
- firmware corpus phase-one intake is cataloged outside Git;
- project admission is separate from repository admission;
- the MN103S recovery programmer is the first registered incubating project;
- same-disk recovery bundles exist;
- an independent physical backup remains blocked on hardware.

## Phase 3 — Analyzer refinement

**Status:** Active refinement

- improve indirect/table-driven command discovery;
- treat a missing direct `0xAD` compare as scanner evidence, not handler absence;
- analyze additional families before broad heuristics are promoted;
- avoid unnecessary Stage5B reruns;
- preserve generated evidence outside Git with provenance.

## Phase 4 — MN103S emulator and firmware behavior

**Status:** v259 ready in separate workstream

- trace descriptor-output/window-selector consumers;
- prove firmware-derived media-window selection;
- close READ(12) after READ(10) consumer proof;
- improve timer/MMIO/IRQ fidelity after the current descriptor target.

## Phase 5 — MN103S recovery hardware

**Status:** Incubating at Rev B0

- review ERC and resolve electrical issues;
- verify module and connector mechanics;
- complete layout and DRC;
- perform read-only first-article ATA/ATAPI bring-up;
- authorize destructive recovery operations only after a separate gate;
- establish a dedicated repository when PFES-ENG-045 readiness criteria pass.

## Phase 6 — Security-sector and authentication acquisition

**Status:** Planned

Exercise patched `0xE7` memory-dump capability only with provenance and hardware
safety controls.

## Phase 7 — Additional media and export formats

**Status:** Evidence-gated

CCI remains an acquisition/export possibility, not an emulator backing-image
claim. Implement only after framing, compression, and scrub semantics are
proven from matched evidence.

## PFES 1.0 readiness

PFES reaches 1.0 when current state and backlog are inheritable without chat
history, major subsystem chapters are usable, evidence paths are traceable, and
a new engineer can continue analyzer, emulator, media, hardware-incubation, and
repository work from canonical artifacts alone.
