Compare commits
2
Commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
9aa49970e4 | ||
|
|
ac60452db6 |
No files matched your search
@@ -0,0 +1,127 @@
|
||||
# Requirements: Neutron GamePort
|
||||
|
||||
**Defined:** 2026-11-12
|
||||
**Core Value:** Match original behavior and presentation as accurately as possible, governed by authoritative evidence and explicit verification.
|
||||
|
||||
## v1 Requirements — Remaining Full Reconstruction
|
||||
|
||||
The release scope is the full original game. Existing bounded implementations are foundations; unchecked items represent their remaining full-scope acceptance, not absence of all implementation. Original means behavior established from authoritative binaries/assets and observed execution, including significant quirks. Approximation and unavailable comparison evidence must stay explicit; neither is silently counted as verified parity.
|
||||
|
||||
### Reference and Fidelity Baseline
|
||||
|
||||
- [ ] **EVID-01**: Every original file remains byte-identical to the recorded inventory throughout recovery, testing and release preparation; generated copies and outputs remain separate.
|
||||
- [ ] **EVID-02**: Reviewers can reproduce identified original-game reference scenarios from an isolated generated installation, with input/event, visual and audio captures where applicable; unresolved execution limitations are recorded and leave comparison acceptance open.
|
||||
- [ ] **EVID-03**: Reviewers can identify each capability's source evidence, implementation revision, runtime platform, current discrepancy and acceptance condition in a maintained full-game coverage ledger.
|
||||
- [ ] **EVID-04**: Testers can repeat the baseline movement/route scenarios on native Linux and native Windows with revision-specific receipts; cross-publish, Wine, component execution and native gameplay remain separately labeled.
|
||||
|
||||
### Movement, Contacts and Scene Ownership
|
||||
|
||||
- [ ] **MOVE-01**: Jimmy's intended original keyboard/mouse/controller inputs, where supported by the original, produce source-faithful movement, facing, jumps, gravity and effect behavior across required movement modes and frame rates.
|
||||
- [ ] **MOVE-02**: Jimmy and participating bodies resolve static/dynamic support, walls, ceilings and special contacts using evidenced real actor responses, live callback reads, ordered physical membership and helper lifetimes before broader scene admission.
|
||||
- [ ] **MOVE-03**: Players retain the original action/animation acceptance, playback, interruption and completion behavior through movement, landing, conversation and control changes.
|
||||
- [ ] **MOVE-04**: Players experience original camera/input/control handoffs through scripts, pause, fresh entry, LOAD and RETURN, preserving correct object/state ownership without invented orientation resets.
|
||||
- [ ] **MOVE-05**: Players can complete lab → VR04 → lab → outside under fresh and retained entry with natural/skipped dialogue, banked jumping, landing, held input and gadget cleanup, preserving implemented startup-order corrections and legitimate landing bank.
|
||||
|
||||
### Actors, Hazards and Combat
|
||||
|
||||
- [ ] **ACT-01**: Original NPC/enemy classes exhibit their evidenced sensing, action transitions, movement, animation and RNG-dependent behavior in their intended scenes.
|
||||
- [ ] **ACT-02**: Players and actors receive original health, damage, immunity, hazard, death and recovery behavior through real gameplay consumers.
|
||||
- [ ] **ACT-03**: Enter/stay/leave and special actor interactions perform original task, score, control and class-specific side effects in the evidenced order.
|
||||
|
||||
### Gadgets, Vehicles and Inventory
|
||||
|
||||
- [ ] **GAD-01**: Players acquire and select all original gadgets/items through original gameplay paths with faithful inventory, energy and availability rules.
|
||||
- [ ] **GAD-02**: Players can use every original gadget against its intended actors/objects with source-faithful aiming, firing, state, projectile and effect behavior; existing bounded gadget implementations retain their verified behavior.
|
||||
- [ ] **GAD-03**: Players can summon, mount, drive/fly and dismount original vehicles through intended modes, inputs, camera, passenger, collision and cleanup behavior.
|
||||
- [ ] **GAD-04**: Gadget/vehicle/companion state follows original interruption, death, script, LOAD/RETURN and save/resume lifetimes across intended scenes.
|
||||
|
||||
### Campaign and Authored Content
|
||||
|
||||
- [ ] **CAMP-01**: Players can enter and traverse every evidenced reachable original campaign and optional/practice level with its intended original assets and entry/exit rules.
|
||||
- [ ] **CAMP-02**: Original missions, authored scripts/cutscenes, tasks, objectives, collectibles and level-specific mechanisms advance through ordinary gameplay in their intended order.
|
||||
- [ ] **CAMP-03**: Players can complete every original campaign route and evidenced optional branch through original completion/win/loss outcomes without debug grants or warps.
|
||||
- [ ] **CAMP-04**: The content ledger accounts for every supplied level/resource and distinguishes reachable content, unreachable/unused content and unresolved missing dependencies using evidence; absent assets are never silently substituted.
|
||||
|
||||
### Frontend, Configuration and Persistence
|
||||
|
||||
- [ ] **UI-01**: Players can use original startup, new-game, menu, pause, objective/HUD, prompt and ending flows through source-supported input and timing; modern diagnostics remain distinguishable.
|
||||
- [ ] **UI-02**: Players can change and persist original-supported configuration, including relevant input/display/audio settings, with source-faithful defaults and bounds.
|
||||
- [ ] **SAVE-01**: Players can save, load and resume through original player-facing workflows with faithful checkpoint, task, inventory, health/energy and progression state, preserving required original-format fields.
|
||||
- [ ] **SAVE-02**: Fresh start, repeated load, scene return and resume reproduce correct retained/reset actor, helper, companion, gadget, script and camera state, verified by equivalent continued gameplay.
|
||||
|
||||
### Visual, Animation and Audio Fidelity
|
||||
|
||||
- [ ] **VIS-01**: Players see original geometry, textures, model hierarchy/pivots, morphs, sprites, animation and UI layout at faithful authored positions and playback timing.
|
||||
- [ ] **VIS-02**: Original lighting, materials, fog, texture stages/sampling, blending, alpha/depth/culling and render-layer behavior are reproduced by Vulkan equivalents and compared against identified original references.
|
||||
- [ ] **VIS-03**: Original gameplay/script cameras, projection, clipping, aspect behavior and transitions reproduce authored presentation without distorting the scene.
|
||||
- [ ] **AUD-01**: Players hear original music, speech and contextual sound banks/events with faithful selection, timing, channel priority, looping and interruption through gameplay and transitions.
|
||||
- [ ] **AUD-02**: Players hear faithful volume, panning, attenuation, positional/frequency behavior and listener ownership, validated through physical audible output as well as event/stream checks.
|
||||
|
||||
### Full-Game Acceptance and Local Delivery
|
||||
|
||||
- [ ] **REL-01**: Players can run clean, self-contained Linux x64 and Windows x64 packages offline with required SDL3/resources/shaders, without development tools, original installation paths or runtime online services.
|
||||
- [ ] **REL-02**: Current packages pass integrated full campaign/optional-content, input, audio, window/focus/resize/fullscreen and resource-lifecycle checks on native Linux and native Windows, with exact source/package identities and recorded Vulkan diagnostics.
|
||||
- [ ] **REL-03**: The final discrepancy audit compares the reconstructed game against original reference scenarios across gameplay, timing, visuals, audio and progression; unresolved differences and verification gaps remain explicit and prevent unsupported full-fidelity completion claims.
|
||||
- [ ] **REL-04**: Maintainers can reproduce local builds/tests/packages and review current evidence, compatibility and known limitations; verified source/tools/docs are pushed to existing Gitea while originals, generated traces and packages stay local.
|
||||
|
||||
## Deferred Requirements
|
||||
|
||||
No original-required feature category is deferred outside the full reconstruction release. Phase-level deferral only establishes dependency order; unknown original behavior is investigated rather than invented. New-gadget expansion remains behind the current movement/route stabilization gate.
|
||||
|
||||
## Out of Scope
|
||||
|
||||
| Feature | Reason |
|
||||
|---------|--------|
|
||||
| Creative mechanics, replacement movement tuning or visual modernization | Original fidelity governs the reconstruction. |
|
||||
| Online runtime services, telemetry, cloud CI | Shared native offline implementation and local builds/tests are mandatory. |
|
||||
| Uploading originals, generated traces or release packages | Source-control authorization covers verified source/tools/docs only. |
|
||||
| Treating third-party remakes as behavior authority | Only original evidence establishes faithful behavior. |
|
||||
|
||||
## Definition of Done
|
||||
|
||||
Each requirement requires evidence recovery, integrated implementation, appropriate regressions and runtime verification, and a verified source revision. Preserve source addresses/offsets and complete REA evidence for binary investigations. Native Windows execution is not replaced by Wine or cross-publishing. Component parity is not whole-original execution. Capture comparison tolerances per system with an evidence-backed reason; never assume blanket pixel/bit identity. All original-required content must be accounted for before full-game completion, and unresolved reference/platform access is an open acceptance dependency.
|
||||
|
||||
## Traceability
|
||||
|
||||
Every v1 requirement maps to exactly one accountable phase. Preservation, evidence capture and fidelity checks continue throughout later phases without duplicating requirement ownership. All statuses begin Pending; existing bounded implementations do not establish full-scope acceptance.
|
||||
|
||||
| Requirement | Phase | Status |
|
||||
|-------------|-------|--------|
|
||||
| EVID-01 | Phase 1 | Pending |
|
||||
| EVID-02 | Phase 1 | Pending |
|
||||
| EVID-03 | Phase 1 | Pending |
|
||||
| EVID-04 | Phase 1 | Pending |
|
||||
| MOVE-01 | Phase 2 | Pending |
|
||||
| MOVE-02 | Phase 2 | Pending |
|
||||
| MOVE-03 | Phase 2 | Pending |
|
||||
| MOVE-04 | Phase 2 | Pending |
|
||||
| MOVE-05 | Phase 2 | Pending |
|
||||
| ACT-01 | Phase 3 | Pending |
|
||||
| ACT-02 | Phase 3 | Pending |
|
||||
| ACT-03 | Phase 3 | Pending |
|
||||
| GAD-01 | Phase 4 | Pending |
|
||||
| GAD-02 | Phase 4 | Pending |
|
||||
| GAD-03 | Phase 4 | Pending |
|
||||
| GAD-04 | Phase 4 | Pending |
|
||||
| CAMP-01 | Phase 5 | Pending |
|
||||
| CAMP-02 | Phase 5 | Pending |
|
||||
| CAMP-03 | Phase 5 | Pending |
|
||||
| CAMP-04 | Phase 5 | Pending |
|
||||
| UI-01 | Phase 6 | Pending |
|
||||
| UI-02 | Phase 6 | Pending |
|
||||
| SAVE-01 | Phase 6 | Pending |
|
||||
| SAVE-02 | Phase 6 | Pending |
|
||||
| VIS-01 | Phase 7 | Pending |
|
||||
| VIS-02 | Phase 7 | Pending |
|
||||
| VIS-03 | Phase 7 | Pending |
|
||||
| AUD-01 | Phase 7 | Pending |
|
||||
| AUD-02 | Phase 7 | Pending |
|
||||
| REL-01 | Phase 8 | Pending |
|
||||
| REL-02 | Phase 8 | Pending |
|
||||
| REL-03 | Phase 8 | Pending |
|
||||
| REL-04 | Phase 8 | Pending |
|
||||
|
||||
**Coverage:** 33 v1 requirements; 33 mapped; 0 unmapped; 0 duplicate phase assignments.
|
||||
|
||||
---
|
||||
*Last updated: 2026-11-12 after full-scope research, playable-slice selection and roadmap traceability*
|
||||
@@ -0,0 +1,150 @@
|
||||
# Roadmap: Neutron GamePort
|
||||
|
||||
## Overview
|
||||
|
||||
Complete the remaining original game as faithfully as possible, building on the existing runtime and bounded implementations. Eight delivery boundaries separate reference access, movement ownership, real actor consumers, gadget use, complete progression, player-facing persistence, presentation closure and native acceptance. Each phase uses playable slices: recover the source contract, integrate it into its intended scenario, and verify the resulting behavior. No original-required content is deferred outside this reconstruction.
|
||||
|
||||
## Delivery and Evidence Rules
|
||||
|
||||
- Preserve the original inventory throughout every phase; use separate generated copies for execution and analysis. Phase 1 owns the preservation baseline; all later phases keep checking it.
|
||||
- Every acceptance receipt identifies source/package/resource revision and platform. Static recovery, inference, compilation, copied-original component execution, port runtime, Wine and whole-original/native Windows comparisons are distinct.
|
||||
- Reference access and native Windows verification start in Phase 1 and continue throughout. If access is unavailable, keep EVID-02/EVID-04 and affected comparison criteria open. Phase 2 and other independently source-backed recovery may proceed on the available ledger/baseline; this exception does not mark Phase 1 complete or waive final acceptance.
|
||||
- Movement stabilization precedes gameplay expansion. Before broader source collision admission, establish actual derived responses, ordered physical membership, helper activation/cleanup and shared mutable reclip. Preserve the lab/outside capsule until its replacement gate closes.
|
||||
- The TSK-backed first-story startup-order correction is implemented. Preserve it and legitimate landing bank; do not invent orientation resets or substitute third-party movement tuning.
|
||||
- Rendering, audio, menus and persistence needed by an earlier playable slice are integrated there. Their later owning phase closes full-game coverage rather than authorizing temporary invented behavior.
|
||||
- Derive comparison tolerances from original evidence per system. Missing comparison evidence stays an acceptance dependency, not a parity claim. REA Evidence and authoritative bytes govern future binary investigations.
|
||||
|
||||
## Phases
|
||||
|
||||
Integer phases are planned work; decimal phases may be inserted for urgent recovered dependencies. Independent investigations may run in parallel with exclusive ownership, while integration follows the dependencies below.
|
||||
|
||||
- [ ] **Phase 1: Reproducible Fidelity Baseline** - Compare identified original and port routes with preserved assets and current native-platform receipts.
|
||||
- [ ] **Phase 2: Faithful Movement and Scene Handoffs** - Stabilize Jimmy, real contacts, animation and retained ownership in the integrated lab/tutorial/outside route.
|
||||
- [ ] **Phase 3: Original Actors, Hazards and Combat** - Make intended NPC/enemy encounters and their consequences playable.
|
||||
- [ ] **Phase 4: Complete Gadget and Vehicle Use** - Acquire and use all original gadgets/vehicles against real consumers across intended lifetimes.
|
||||
- [ ] **Phase 5: Complete Campaign and Optional Routes** - Traverse all original-required content and reach original outcomes through normal progression.
|
||||
- [ ] **Phase 6: Original Frontend and Save/Resume** - Use original menus/options and resume equivalent gameplay through player-facing persistence.
|
||||
- [ ] **Phase 7: Original Visual and Audible Presentation** - Close rendering, playback, camera and sound differences across complete gameplay.
|
||||
- [ ] **Phase 8: Full-Game Native Acceptance and Delivery** - Verify standalone Linux/Windows packages against original journeys and publish verified source documentation.
|
||||
|
||||
## Phase Details
|
||||
|
||||
### Phase 1: Reproducible Fidelity Baseline
|
||||
**Goal:** Testers can reproduce identified original/port comparison scenarios and understand exactly what the current reconstruction proves on each native platform.
|
||||
**Mode:** mvp
|
||||
**Depends on:** Nothing (existing codebase and evidence are the starting point).
|
||||
**Requirements:** EVID-01, EVID-02, EVID-03, EVID-04
|
||||
**Success Criteria** (what must be TRUE):
|
||||
1. A reviewer can verify every original against the recorded inventory and run investigation/reference copies without altering the original installation.
|
||||
2. A tester can reproduce identified whole-original reference scenarios from an isolated generated installation and inspect corresponding input/events, images and audio where applicable; unavailable execution keeps this criterion open.
|
||||
3. A reviewer can trace every full-game capability from original evidence through current implementation, platform receipts, discrepancies and its remaining acceptance condition.
|
||||
4. Testers can repeat the same baseline movement/route scenarios on native Linux and native Windows with exact revision identities; Wine/cross-publish receipts remain separately labeled and cannot close missing native execution.
|
||||
**Plans:** TBD
|
||||
|
||||
### Phase 2: Faithful Movement and Scene Handoffs
|
||||
**Goal:** Players move, contact the world and return from scripts/scenes with the original movement, animation, camera and state ownership intact.
|
||||
**Mode:** mvp
|
||||
**Depends on:** Phase 1 baseline/ledger and available reference evidence; independently source-backed work may proceed under the access exception above.
|
||||
**Requirements:** MOVE-01, MOVE-02, MOVE-03, MOVE-04, MOVE-05
|
||||
**Success Criteria** (what must be TRUE):
|
||||
1. Players reproduce evidenced Jimmy movement/facing/jump/effect modes using original-supported input devices across tested frame rates without changing significant source arithmetic or timing.
|
||||
2. Players and participating bodies experience evidenced static/dynamic support, walls, ceilings and special contacts through real responses; full state/event comparisons establish helper membership, live callback reads and shared reclip before any wider solver admission.
|
||||
3. Movement, landing, talk and control changes accept, interrupt and complete actions/animations with the original clocks and outcomes.
|
||||
4. Camera/input/control ownership and retained/reset state remain faithful across fresh entry, scripts, pause, LOAD and RETURN, including the implemented TSK startup order and original landing bank.
|
||||
5. Players complete lab → VR04 → lab → outside with natural/skipped conversations, banked jumps, held input, landing/idle and gadget cleanup; integrated port/native receipts and available original comparisons identify remaining differences explicitly.
|
||||
**Plans:** TBD
|
||||
|
||||
### Phase 3: Original Actors, Hazards and Combat
|
||||
**Goal:** Players encounter original NPC/enemy behavior and receive the correct gameplay consequences through real scene interactions.
|
||||
**Mode:** mvp
|
||||
**Depends on:** Phase 2; actor-specific membership/response contracts must precede each live admission.
|
||||
**Requirements:** ACT-01, ACT-02, ACT-03
|
||||
**Success Criteria** (what must be TRUE):
|
||||
1. Players encounter each original-required NPC/enemy class in its intended scenes with evidenced sensing, movement, action/RNG decisions and animation rather than generic placeholder policies.
|
||||
2. Combat and hazards produce original health, damage, immunity, death and recovery outcomes for players and affected actors during normal play.
|
||||
3. Real enter/stay/leave and special interactions produce the correct ordered task, score, control and class-specific effects, including callback mutations and repeated contacts.
|
||||
**Plans:** TBD
|
||||
|
||||
### Phase 4: Complete Gadget and Vehicle Use
|
||||
**Goal:** Players acquire and use every original gadget and vehicle through intended gameplay paths, consumers and scene lifetimes.
|
||||
**Mode:** mvp
|
||||
**Depends on:** Phases 2 and 3; required normal acquisition routes are integrated with each gadget slice before Phase 5 closes complete campaign coverage.
|
||||
**Requirements:** GAD-01, GAD-02, GAD-03, GAD-04
|
||||
**Success Criteria** (what must be TRUE):
|
||||
1. Players acquire/select every original gadget/item through its evidenced normal gameplay path, with original availability, inventory and energy behavior; debug grants alone do not satisfy acquisition.
|
||||
2. Every gadget can be aimed/activated/fired against its intended actor/object consumers with the evidenced states, projectiles and effects, while already verified bounded features keep working.
|
||||
3. Players summon, mount, operate and dismount original vehicles in supported modes with faithful input, collision, passenger and camera behavior.
|
||||
4. Interruptions, death, scripts, LOAD/RETURN and supported save/resume preserve or clear gadget, vehicle and companion state exactly at evidenced lifetime boundaries.
|
||||
**Plans:** TBD
|
||||
|
||||
### Phase 5: Complete Campaign and Optional Routes
|
||||
**Goal:** Players traverse all original-required campaign and optional content and reach original outcomes through ordinary progression.
|
||||
**Mode:** mvp
|
||||
**Depends on:** Phases 2–4; integrate any prerequisite frontend/persistence behavior within each route slice.
|
||||
**Requirements:** CAMP-01, CAMP-02, CAMP-03, CAMP-04
|
||||
**Success Criteria** (what must be TRUE):
|
||||
1. Players enter/traverse every evidenced reachable campaign, optional and practice level using its original assets and correct entrance/exit rules.
|
||||
2. Authored scripts/cutscenes, missions, tasks, objectives, collectibles and level mechanisms advance in the original order through normal play.
|
||||
3. Players complete every original campaign route and evidenced optional branch through its original completion/win/loss outcome without debug grants, warps or substituted progression.
|
||||
4. Reviewers can account for every supplied level/resource as reachable, evidenced unused/unreachable, or an unresolved dependency; missing archives are investigated for actual reachability rather than silently substituted or assumed fatal.
|
||||
**Plans:** TBD
|
||||
**UI hint:** yes
|
||||
|
||||
### Phase 6: Original Frontend and Save/Resume
|
||||
**Goal:** Players use the original frontend/options and save/resume completed gameplay with equivalent progression and retained state.
|
||||
**Mode:** mvp
|
||||
**Depends on:** Phases 2–5; save/configuration callers needed by earlier slices are recovered and integrated earlier.
|
||||
**Requirements:** UI-01, UI-02, SAVE-01, SAVE-02
|
||||
**Success Criteria** (what must be TRUE):
|
||||
1. Players use original startup, new-game, menu, pause, objective/HUD, prompt and ending flows with evidenced input/timing; modern diagnostics are distinguishable from original UI.
|
||||
2. Players change and persist original-supported input/display/audio configuration with faithful defaults and bounds.
|
||||
3. Players save/load/resume through original player-facing workflows with correct checkpoints, tasks, inventory, health/energy and progression, preserving required original-format fields.
|
||||
4. Fresh start, repeated load, scene return and resumed play preserve the appropriate actor/helper/companion/gadget/script/camera state and produce equivalent continued gameplay, not merely matching serialized bytes.
|
||||
**Plans:** TBD
|
||||
**UI hint:** yes
|
||||
|
||||
### Phase 7: Original Visual and Audible Presentation
|
||||
**Goal:** Players see and hear the original authored presentation across complete gameplay, with remaining visual/audio differences resolved through identified comparisons.
|
||||
**Mode:** mvp
|
||||
**Depends on:** Phases 2–6 and original reference access from Phase 1; blocking presentation contracts are integrated with earlier slices.
|
||||
**Requirements:** VIS-01, VIS-02, VIS-03, AUD-01, AUD-02
|
||||
**Success Criteria** (what must be TRUE):
|
||||
1. Original geometry, textures, hierarchy/pivots, morphs, sprites, animation and UI appear at faithful authored positions and playback timing in matched gameplay/reference captures.
|
||||
2. Lighting, materials, fog, texture stages/sampling, blend/alpha/depth/culling and render layers match the evidenced original behavior through Vulkan equivalents, using justified system-specific comparison tolerances.
|
||||
3. Gameplay/script camera framing, projection, clipping, aspect handling and transitions preserve the authored scene without distortion.
|
||||
4. Players hear the original music/speech/contextual banks and events with correct timing, priorities, loops and interruption through gameplay and scene changes.
|
||||
5. Physical audible checks and matched event/listener observations confirm volume, panning, attenuation, positional/frequency behavior and camera/listener ownership; dummy streams alone do not establish fidelity.
|
||||
**Plans:** TBD
|
||||
**UI hint:** yes
|
||||
|
||||
### Phase 8: Full-Game Native Acceptance and Delivery
|
||||
**Goal:** Players can run reproducible offline packages on native Linux and Windows and complete the original game with current full-game fidelity evidence.
|
||||
**Mode:** mvp
|
||||
**Depends on:** Phases 1–7; all original/native comparison acceptance dependencies must close for full completion.
|
||||
**Requirements:** REL-01, REL-02, REL-03, REL-04
|
||||
**Success Criteria** (what must be TRUE):
|
||||
1. Clean self-contained Linux x64 and Windows x64 packages run offline without SDK/development paths or the original installation, carrying the required SDL3, resources and shaders.
|
||||
2. Current packages complete integrated campaign/optional-content scenarios and physical input/audio/window/focus/resize/fullscreen/lifecycle checks on both native platforms with exact source/package identities and Vulkan diagnostics.
|
||||
3. A final original-versus-port discrepancy audit covers gameplay, timing, visuals, audio and progression; unresolved original-required differences or unavailable comparisons remain visible and prevent unsupported full-fidelity completion claims.
|
||||
4. Maintainers reproduce local builds/tests/packages and find current compatibility/evidence/limitations; verified source/tools/docs are pushed to existing Gitea while originals, generated traces and packages remain local, and original hashes still match.
|
||||
**Plans:** TBD
|
||||
|
||||
## Progress
|
||||
|
||||
Execution follows 1 → 2 → 3 → 4 → 5 → 6 → 7 → 8, subject to the explicit reference-access exception and earlier prerequisite integration. Full completion cannot bypass an open phase or acceptance dependency.
|
||||
|
||||
| Phase | Plans Complete | Status | Completed |
|
||||
|-------|----------------|--------|-----------|
|
||||
| 1. Reproducible Fidelity Baseline | 0/TBD | Not started | - |
|
||||
| 2. Faithful Movement and Scene Handoffs | 0/TBD | Not started | - |
|
||||
| 3. Original Actors, Hazards and Combat | 0/TBD | Not started | - |
|
||||
| 4. Complete Gadget and Vehicle Use | 0/TBD | Not started | - |
|
||||
| 5. Complete Campaign and Optional Routes | 0/TBD | Not started | - |
|
||||
| 6. Original Frontend and Save/Resume | 0/TBD | Not started | - |
|
||||
| 7. Original Visual and Audible Presentation | 0/TBD | Not started | - |
|
||||
| 8. Full-Game Native Acceptance and Delivery | 0/TBD | Not started | - |
|
||||
|
||||
**Coverage:** 33/33 v1 requirements assigned once; all phases have 3–5 observable success criteria. Existing bounded implementation is not counted as phase completion.
|
||||
|
||||
---
|
||||
*Initialized: 2026-11-12 — remaining full reconstruction, playable slices*
|
||||
@@ -0,0 +1,79 @@
|
||||
---
|
||||
gsd_state_version: '1.0'
|
||||
status: planning
|
||||
progress:
|
||||
total_phases: 8
|
||||
completed_phases: 0
|
||||
total_plans: 0
|
||||
completed_plans: 0
|
||||
percent: 0
|
||||
---
|
||||
|
||||
# Project State
|
||||
|
||||
## Project Reference
|
||||
|
||||
See: .planning/PROJECT.md (updated 2026-11-12)
|
||||
|
||||
**Core value:** Match original behavior and presentation as accurately as possible, governed by authoritative evidence and explicit verification.
|
||||
**Current focus:** Phase 1 — Reproducible Fidelity Baseline.
|
||||
|
||||
## Current Position
|
||||
|
||||
Phase: 1 of 8 (Reproducible Fidelity Baseline)
|
||||
Plan: None yet; phase plan count TBD
|
||||
Status: Ready to plan
|
||||
Last activity: 2026-11-12 — Initialized full-reconstruction roadmap with 33 requirements mapped once.
|
||||
|
||||
Progress: [░░░░░░░░░░] 0%
|
||||
|
||||
## Performance Metrics
|
||||
|
||||
- Total plans completed: 0
|
||||
- Average duration: Not established
|
||||
- Total execution time: 0 hours
|
||||
|
||||
| Phase | Plans | Total | Avg/Plan |
|
||||
|-------|-------|-------|----------|
|
||||
| - | - | - | - |
|
||||
|
||||
Recent trend: No execution plans completed in this roadmap. Existing project work predates initialization and retains its documented bounded evidence.
|
||||
|
||||
## Accumulated Context
|
||||
|
||||
### Decisions
|
||||
|
||||
- Full remaining original game is in scope; fidelity governs behavior and presentation, including significant original quirks.
|
||||
- Playable slices, standard granularity, autonomous mode and parallel independent plans; research, plan checking and verification enabled; models inherit this session.
|
||||
- Preserve Jimmy movement and implemented TSK startup-order correction; movement/contact/helper/animation/camera stabilization precedes broader gameplay expansion.
|
||||
- Cross-cutting checks continue throughout; each requirement has one accountable phase. No original-required category is deferred outside this release.
|
||||
- Builds/tests/packages stay local; push verified source/tools/docs to existing Gitea. Preserve unrelated working-tree changes.
|
||||
|
||||
### Pending Todos
|
||||
|
||||
None captured separately. Next action: `$gsd-discuss-phase 1` or `$gsd-plan-phase 1`.
|
||||
|
||||
### Blockers/Concerns
|
||||
|
||||
- Phase 1: Working whole-original reference capture and current native Windows comparison remain unverified access dependencies. Record limitations; keep acceptance open while independent source-backed recovery continues.
|
||||
- Phase 2: Real derived responses, helper membership/activation/cleanup, physical order and shared mutable reclip remain live admission gates. Lab/outside capsule stays until its replacement gate closes.
|
||||
- Full-game completion requires current integrated native Linux/Windows and original-reference evidence. Compilation, copied-original probes and Wine have narrower scopes.
|
||||
- Historical reports contain superseded narratives; prefer later continuation receipts with exact revision/platform identity. Carl startup ordering is already corrected, not an untouched defect.
|
||||
|
||||
### Evidence Pointers
|
||||
|
||||
- `.planning/research/SUMMARY.md`, `.planning/codebase/` — scope, dependencies and current architecture.
|
||||
- `docs/progress.md`, `docs/compatibility.md`, `docs/tasks.md` — implementation/runtime receipts and open work.
|
||||
- `docs/checkpoint/next-work-plan.md`, `coverage.md`, `implementation-plan.md` — recovery/admission sequence (latter two under the same directory).
|
||||
- `docs/gameplay/main-menu-player-lifetime.md`, `jimmy-movement-stabilization.md` — preserved correction and movement priority (same directory).
|
||||
- `../prompt.MD`, `AGENTS.md`, `../AGENTS.md` — authoritative specification/rules; original manifest at `docs/original-manifest.json`.
|
||||
|
||||
## Deferred Items
|
||||
|
||||
No original-required category deferred outside full reconstruction. Later phases express dependency order only.
|
||||
|
||||
## Session Continuity
|
||||
|
||||
Last session: 2026-11-12
|
||||
Stopped at: Roadmap initialization; Phase 1 ready for planning, 0 phases completed.
|
||||
Resume file: None
|
||||
@@ -0,0 +1,24 @@
|
||||
# Onboarding Summary
|
||||
|
||||
## Project State
|
||||
- PROJECT.md: present
|
||||
- REQUIREMENTS.md: present
|
||||
- ROADMAP.md: present
|
||||
- STATE.md: present
|
||||
|
||||
## Codebase Context
|
||||
- Brownfield repo: yes
|
||||
- Map readiness: complete
|
||||
- Codebase map: `.planning/codebase/` (complete codebase map)
|
||||
- Fast map available: yes
|
||||
|
||||
## Docs Context
|
||||
- Existing ADR/PRD/SPEC/RFC candidates detected by onboarding: 0
|
||||
- Authoritative scope: [prompt.MD](../../../prompt.MD); see [PROJECT.md](../PROJECT.md) for specification and evidence pointers.
|
||||
- Existing evidence reviewed in `.planning/research/`; prior runtime receipts remain bounded.
|
||||
|
||||
## Recommended Next Step
|
||||
- `$gsd-manager` for project navigation.
|
||||
- `$gsd-discuss-phase 1` to clarify Reproducible Fidelity Baseline, or `$gsd-plan-phase 1` to plan directly.
|
||||
|
||||
Initialization covers 8 playable-slice phases and 33 requirements. No reconstruction phase has executed under this roadmap.
|
||||
@@ -1,5 +1,16 @@
|
||||
# Decisions
|
||||
|
||||
## Full reconstruction planning — 2026-11-12
|
||||
|
||||
The user scoped GSD planning to the remaining full reconstruction and explicitly
|
||||
required accuracy as high as possible to the original. Organize work as playable
|
||||
slices, retaining the movement-first stabilization gate and all original-required
|
||||
content. Use autonomous mode, standard phases, parallel independent plans,
|
||||
tracked planning docs, research/plan checking/verification, full instructions
|
||||
and inherited session models; optional PR body sections are disabled.
|
||||
See `../.planning/PROJECT.md`, `config.json`, `REQUIREMENTS.md` and `ROADMAP.md`.
|
||||
These decisions introduce no gameplay changes or new compatibility claims.
|
||||
|
||||
User workflow update (2026-11-05): completed, verified milestones are now pushed
|
||||
to the existing `Gitea` remote at `https://gitea.unixnight.com/UnixNight/Neutron.git`
|
||||
on `main`. This explicit user instruction supersedes earlier local-only Git
|
||||
|
||||
@@ -1,5 +1,16 @@
|
||||
# Progress — 2026-11-07
|
||||
|
||||
## Planning initialization — 2026-11-12
|
||||
|
||||
GSD onboarding and full-reconstruction planning are initialized in
|
||||
`../.planning/PROJECT.md`, `REQUIREMENTS.md`, `ROADMAP.md` and `STATE.md`.
|
||||
The user requires fidelity as high as possible to the original and selected
|
||||
autonomous execution, standard granularity and playable slices. Eight phases
|
||||
map all33 requirements exactly once; phase1 is ready to plan, none executed.
|
||||
Research reuses existing evidence; it is not new binary or runtime verification.
|
||||
All existing movement/admission gates and platform limitations remain binding.
|
||||
Next: `$gsd-discuss-phase 1` or `$gsd-plan-phase 1` from GamePort.
|
||||
|
||||
Workflow update: the user authorizes pushing completed, verified commits to the
|
||||
existing `Gitea/main` upstream from now on. See docs/decisions.md and AGENTS.md.
|
||||
|
||||
|
||||
@@ -1,5 +1,15 @@
|
||||
# Tasks
|
||||
|
||||
## GSD handoff — 2026-11-12
|
||||
|
||||
- [x] Initialize full remaining reconstruction scope, research,33 requirements
|
||||
and8 playable-slice phases in `../.planning/`.
|
||||
- [ ] Discuss/plan phase1: Reproducible Fidelity Baseline. Keep original/native
|
||||
Windows access dependencies open; independent source-backed recovery may
|
||||
continue under the explicit roadmap exception.
|
||||
- [ ] Execute the roadmap with current evidence/admission gates; initialization
|
||||
does not complete or supersede existing gameplay tasks below.
|
||||
|
||||
Full-game completion remains the objective. Original files are authoritative;
|
||||
compile, runtime and original-fidelity verification are separate.
|
||||
|
||||
|
||||
Reference in new issue
Block a user