Builder Redistribution Addendum

Scope

This Builder Redistribution Addendum is part of bitfield-product-terms-2026-05-11. It applies only when Bitfield gives you a builder plan, signed builder grant, or written redistribution right.

Builder grant

A builder grant may allow you to create, sign, distribute, and update products that include or depend on Bitfield runtime artifacts, package sets, slots, activation resources, and release manifests.

The grant is limited to the products, accounts, release channels, territories, quantities, and activation model stated in the builder grant or signed product release data.

Signed product releases are required

Builder products must ship through signed product releases or another written Bitfield-approved release mechanism. A zip file of copied runtime artifacts is not a redistribution grant.

The release must identify runtime artifact hashes, package-set hashes, package-use proof hashes, activation resource, update channel, package edit policy, redistribution scope, and terms pack version/hash when those fields are supported by the release manifest.

End-user rights

Your end users receive only the right to run the signed builder product release under the applicable End-User Runtime Terms or written Bitfield-approved terms.

Unless Bitfield says otherwise in writing, end users do not receive a standalone Bitfield runtime license, source license, resale right, or right to extract Runtime Kit or Bitfield runtime artifacts for other products.

Commercial and activation duties

Builder pricing, activation, customer account mapping, and usage reporting must follow the signed policy and builder grant. Do not hide runtime identities, forge observations, strip activation, or route protected runtime use around Bitfield licensing.

Active device and future pricing labels are policy labels over signed observations. They are not something a builder may redefine by local code or by failing to report protected runtime use.

Audit and suspension

Bitfield may require reasonable records, release manifests, distribution counts, activation records, or package-use proofs to verify builder compliance.

Bitfield may suspend builder redistribution rights, update channels, signing keys, or activation resources for material breach, security risk, non-payment, or unauthorized redistribution.