How should releases be versioned and delivered so I can resell them reliably?

Resellers need to know what a customer holds and what changed between releases. Ask for these conventions.

**Release identifier.** A unique `release_id` in the manifest, repeated in file metadata, so a listing can point to exactly one build.

**Schema version.** A version string that changes whenever a field is added, removed, retyped or redefined, with a short changelog explaining the change and its likely effect on loaders.

**Stable names.** File and table names that stay the same across releases, so a customer's pipeline does not break on a rename.

**Checksums.** A checksum per file, so you can verify delivery and customers can verify your copy.

**Splits and seeds.** Split definitions and environment seeds recorded in the release, so evaluation results can be reproduced and compared.

**Environment reset.** For simulated environments, a documented reset call and snapshot references, so customers can restore a known state between runs.

**Metadata access.** Listing metadata such as the table inventory, schema version and known limitations can be read through MirrorFirm's public MCP server, which helps keep your catalogue text aligned with the release.

When a release is superseded, keep the earlier version available to customers who built on it, and state the licence position for each version.