Commercial and distribution systems

The routes a sale can take

Store-originated. A customer finds an approved product, selects a licence under its manifest, checks out through the authorised path, receives a signed entitlement and a compatible signed release, and their administrator approves the installation.

Publisher-originated. A publisher finds its own customer and registers the sale, which then follows the same pricing, licence, merchant and settlement path. The publisher keeps its intellectual property and the customer relationship.

Distributor-originated. A qualified partner demonstrates an available framework, registers the opportunity and its origin, and settlement reflects the approved channel band.

Publisher economics

On eligible partner framework sales, the split is 80 per cent to the publisher and 20 per cent to Lanvex, before applicable taxes, fees and any separately agreed channel band, and subject to contract.

That is a share of sales. It is not ownership of the publisher's intellectual property and not equity in the publisher's company.

What is recorded, and what is not

Recorded	Not recorded
Publisher identity and keys	Customer operational records
Framework identity, version, release hash	Customer-specific tasks
Site contract and approved features	Vault contents
Signed entitlement and its validity	Remote execution credentials
Transaction, split, tax, refund and settlement	The customer's own ledger

A site can be entirely offline after a licence is issued. This system records the commercial event, not the customer's activity.

The honest limit

Source that a publisher can modify can be forked, and no technical measure finds every unreported use of a distributed SDK. The design supports an authorised, tracked commercial ecosystem through contracts, signed releases and supported runtime verification. It is not surveillance, and it is not claimed to be exhaustive.