# VxSound asset and provenance policy

This document describes how VxSound handles presets, recordings, media, fixtures and other externally supplied material. It is a project policy, not legal advice.

## Project-owned material

VxSound source code, independently authored built-in presets and the synthetic reference-audio generators are project-owned material released under the repository's MIT license unless a file states otherwise.

The **Music**, **Spatial**, **Gaming** and **Movie** reference clips are generated from code in `SyntheticTestAudio`. No third-party recordings are embedded in those clips.

## Imported profiles

Profile schema v3 stores provenance separately from the EQ values. A profile can record:

- source type;
- source name;
- optional source reference;
- optional license information;
- whether redistribution has been explicitly cleared.

A profile marked `RedistributionCleared = false` can be stored and used locally, but VxSound's normal profile-export path rejects it. This reduces accidental sharing; it is not DRM and does not establish ownership or legal permission.

Legacy imported JSON without provenance metadata is treated conservatively as external/local-only material.

## External EQ data

The generic external-EQ projection layer accepts numerical frequency/gain points supplied by an importer or user and maps them to VxSound's ten EQ bands. The projection layer is vendor-neutral and does not grant rights to the data supplied to it.

When adding an importer, keep parser-specific code separate from VxSound's built-in preset catalog and document the source format without committing private or unlicensed source data as fixtures.

## Recordings and test media

Bundled recordings must be one of the following:

1. created specifically for VxSound and released under compatible terms;
2. generated by VxSound itself;
3. public-domain material with documented provenance; or
4. third-party material with a license that explicitly permits the intended redistribution and required attribution.

Do not assume that material is redistributable because it can be streamed, downloaded, found on a public website or supplied by a user.

## Third-party libraries and icons

Dependency licenses and attribution requirements belong in `THIRD_PARTY_NOTICES.md` or in the appropriate bundled license file. Adding a dependency must not silently remove or replace its required notice.

## Contribution rules

Contributors should:

- identify the origin of externally supplied presets, recordings, images and data;
- include compatible license and attribution information when redistribution is required;
- avoid committing private exports, account data, listening histories or local application databases;
- prefer generated fixtures for tests;
- keep project branding and independently authored assets distinct from external material; and
- preserve provenance when transforming an imported profile.

Changing a source label, file format or a few numeric values does not by itself create redistribution rights.

## Packaging boundary

Release packages should contain only project-owned material and dependencies/assets whose redistribution terms are documented. Local user imports stay outside release packages.

The repository's MIT license applies to VxSound material released under it. It does not relicense third-party files or data imported by a user.