# Phase 1: Reproducible Fidelity Baseline - Discussion Log > **Audit trail only.** Planning, research and execution consume CONTEXT.md, not this log. **Date:** 2026-11-12 **Phase:** 01-reproducible-fidelity-baseline **Areas discussed:** Baseline journeys, Comparison review, Evidence navigation, Original and Windows access The user selected all four areas. Discussion used individual numbered text questions. Each area was completed explicitly, and the user selected “Ready for context” after the final summary. ## Baseline journeys ### For lab → VR04 → lab → outside, how should comparison runs be organized? | Option | |--------| | Full route plus focused replays (Recommended) | | Full route first | | Focused replays first | **User’s choice / clarification:** Full route plus focused replays: capture the continuous journey, then replay specific moments such as dialogue return, banked jumps and landing. ### How should natural and skipped dialogue appear in the baseline? | Option | |--------| | Both as equal cases (Recommended) | | Natural dialogue first | | Skipped dialogue first | **User’s choice / clarification:** Both as equal cases: run the route with dialogue completing naturally and with dialogue skipped. ### How should fresh entry and retained return be covered? | Option | |--------| | Separate, equally required runs (Recommended) | | Continuous journey first | | Fresh start first | **User’s choice / clarification:** Separate, equally required runs: capture a clean start and a continuous departure/return journey, preserving each lifetime. ### How should player inputs be chosen for the focused replays? | Option | |--------| | Normal play plus deliberate edge cases (Recommended) | | Normal play first | | Repeat your reported sequences first | **User’s choice / clarification:** Normal play plus deliberate edge cases: include ordinary movement alongside held input through dialogue/return, banked jumps, landing and idle. ### More on baseline journeys, or next area? | Option | |--------| | Next area | | More on baseline journeys | **User’s choice / clarification:** Next area: Comparison review. ## Comparison review ### What should appear first when opening scenario results? | Option | |--------| | Paired playback with marked differences (Recommended) | | Written findings first | | Chronological capture timeline | **User’s choice / clarification:** Paired playback with marked differences: original and port shown together, with links to matching images, audio and input/event traces. ### How should differences be highlighted? | Option | |--------| | Clean playback with optional overlays (Recommended) | | Annotations always visible | | Clean playback with notes alongside | **User’s choice / clarification:** Clean playback with optional overlays: both captures remain unobstructed by default; annotations and image differences can be toggled for inspection. ### How should original and port playback line up when timing differs? | Option | |--------| | Align key events and show timing drift (Recommended) | | Start together and run continuously | | Step through matching events | **User’s choice / clarification:** Align key events and show timing drift, preserving actual recording speed and elapsed time. ### How should audio be reviewed? | Option | |--------| | Switch between original and port (Recommended) | | Original then port excerpts | | Separate audio review | **User’s choice / clarification:** Switch between original and port at corresponding moments, hearing one recording at a time; review-only volume adjustments must be clearly labeled. ### More on comparison review, or next area? | Option | |--------| | Next area | | More on comparison review | **User’s choice / clarification:** Next area: Evidence navigation. ## Evidence navigation ### What should be the main entry point into the full-game evidence ledger? | Option | |--------| | Gameplay capabilities (Recommended) | | Playable journeys | | Requirements | **User’s choice / clarification:** Gameplay capabilities: browse movement, contacts, gadgets, progression, visuals and audio; each leads to scenarios, source evidence and platform receipts. ### What should each capability show before detailed evidence? | Option | |--------| | Current state and remaining gap (Recommended) | | Latest comparison result | | Evidence summary | **User’s choice / clarification:** Current state and remaining gap: what works, where it was verified, known differences and remaining acceptance conditions. ### How should earlier evidence appear when newer work supersedes it? | Option | |--------| | Current evidence first, history expandable (Recommended) | | Full history alongside current evidence | | Separate history index | **User’s choice / clarification:** Current evidence first, history expandable; retain older results with clear revision and superseded labels. ### How should open discrepancies be ordered within a capability? | Option | |--------| | Player impact first (Recommended) | | Route order | | Newest findings first | **User’s choice / clarification:** Player impact first: failures blocking or visibly disrupting play precede subtler differences and missing verification. ### More on evidence navigation, or next area? | Option | |--------| | Next area | | More on evidence navigation | **User’s choice / clarification:** Next area: Original and Windows access. ## Original and Windows access ### What Windows environment is available for this phase? | Option | |--------| | A local Windows PC | | A local Windows VM | | None currently | **User’s choice / clarification:** A local Windows PC; the user can run a prepared test package and return results. ### How should Windows checks be run? | Option | |--------| | One local test bundle per checkpoint (Recommended) | | Guided sessions | | Written checklist | **User’s choice / clarification:** One local test bundle per checkpoint, with a launcher collecting revision details, logs and captures; packages and captures remain local and transfer uses a local method. ### Can the Windows PC also run a separate generated copy of the original? | Option | |--------| | Yes, try it on that PC (Recommended) | | Use Linux/Wine for original captures | | Original-game execution is unavailable for now | **User’s choice / clarification:** Yes, try it on that PC, using a separate generated copy and recording execution/rendering limitations. ### How should hands-on capture sessions be scheduled? | Option | |--------| | Prepare everything, then one combined session per checkpoint (Recommended) | | Original captures first, port checks later | | Short sessions as needed | **User’s choice / clarification:** Prepare everything, then one combined session per checkpoint, bundling original-reference captures and port checks with clear steps and collecting results together. ### Finish execution access or discuss further? | Option | |--------| | Finish this area | | More on execution access | **User’s choice / clarification:** User clarification: Local testing on my windows machine will have the original game running via dxwnd. ### Finish this area or discuss the DxWnd setup further? | Option | |--------| | Finish this area | | Discuss the DxWnd setup further | **User’s choice / clarification:** Finish this area. Original reference execution uses DxWnd; record its version/configuration with captures and distinguish wrapper effects from native Windows port checks. ## Agent discretion No explicit product-choice delegation. Implementation mechanics remain for research/planning within the captured decisions. ## Deferred Ideas None.