openvistapro/docs/legal/asset-policy.md

Asset and Reference Policy

OpenVistaPro should be developed as a clean-room, open-source project.

Do not commit

• Original VistaPro binaries, installers, ISO images, disk images, archives, or extracted program files.
• Proprietary manuals unless their license explicitly permits redistribution.
• Proprietary sample landscapes, textures, colormaps, or data files.

The repository .gitignore excludes reference/, .work/, archives, disk images, and executables.

Acceptable project materials

• Original notes written from observation and public documentation.
• Fresh source code authored for OpenVistaPro.
• Openly licensed examples with attribution and license files.
• Synthetic test fixtures generated specifically for this project.
• Public-domain terrain data, such as USGS/NASA datasets, when redistributed according to source terms.

Test fixture layout

Project-owned synthetic terrain fixtures live under tests/fixtures/open/. The open/ segment marks the directory as cleared for commit: every file there must be authored specifically for OpenVistaPro, or carry an explicit open license with attribution alongside it.

Never place proprietary VistaPro data, extracted program files, manuals, screenshots, archives, disk images, or local-only reference payloads under tests/. Those belong in the git-ignored reference/ and .work/ directories and must stay local-only.

Importers parse only open or synthetic formats. The supported terrain source boundary currently consists of the original OpenVistaPro ovp-text plain-text heightfield format, script-level PNG heightmaps, and open SRTM/HGT, ESRI ASCII Grid, and GeoTIFF inputs. These all normalize to the same internal terrain model and are not reimplementations of any proprietary VistaPro file layout.

Legacy VistaPro terrain/image compatibility remains out of scope for the clean- room project unless a future, separately reviewed compatibility investigation explicitly approves it.

Reverse engineering boundary

Use the reference copies for product behavior research only. Avoid decompilation or binary translation unless a future legal review explicitly approves a narrow compatibility investigation.