OpenZT2 Reconstruction Dashboard
A map of the reconstruction pipeline: evidence, ownership/behavior, and implementation.
Pipeline
- Byte range map is the evidence gate by address/range: it records whether each mapped byte or range exists and what it is.
- Binary perimeter is the evidence pivot gate: it groups the recorded evidence by functions, type identities, vtables, globals, and broad evidence families.
- Functional specification is the product and delivery gate: it defines the greenfield Bevy architecture, native pack contracts, original behavior, performance acceptance, and every discrete implementation package.
Pages
Byte Range Map
Contains the byte-level evidence ledger for the original executable: disk/runtime ranges, SafeDisc materialization records, accepted function identities, residual gaps, and status notes for exact address spans.
Binary Perimeter
Shows generated function, variables/data, and type-identity inventories over the stripped binary, joining exact byte-map anchors with library provenance, vtable membership, inferred domains, and remaining frontier classifications.
Asset Lineage
The settled source-to-native conversion table: every accepted original extension, offline transformation, rkyv archive, mapped Bevy asset boundary, copy policy, and renderer handoff.
Functional Specification
The canonical product contract and delivery map: high-performance native assets, greenfield Bevy ownership, original-game behavior, acceptance criteria, and the status of all 56 independent work packages.