Package Marketplace / Package Edit Policy

Policy for inspectable packages, package edits, public/private/internal package lanes, package-use proofs, and runtime rights.

Last updated: May 11, 2026

Scope

This Package Marketplace / Package Edit Policy is part of bitfield-product-terms-2026-05-11. It applies to Bitfield package material, Command Center packages, builder packages, package marketplaces, private package lanes, and local package edits where a signed product policy allows them.

Package material is not the runtime

A package can contain records, stored bytes, slot declarations, UI surfaces, scripts, or other product material. Runtime Kit and Bitfield runtime artifacts are separate closed-source runtime artifacts.

Permission to inspect, edit, fork, replace, or publish package material does not grant a source license or redistribution right for Runtime Kit, Bitfield runtime artifacts, account systems, signing systems, or protected Bitfield services.

Package lanes

  • Public packages may be visible or editable when the product policy allows it.
  • Private packages may be visible only to allowed accounts, organizations, products, or release channels.
  • Internal/operator packages are not granted by package self-labels, hidden UI tabs, or local file edits.
  • Package admission is decided by signed package-use facts, rules, context, and proof.

Local edits and forks

A local package edit or fork must pass the same package boundary and package-use rules as any other package material. If the edit changes what is admitted, it needs a new package-use proof or a release policy that allows the local overlay.

Local edits may affect support, compatibility, security, update eligibility, and reproducibility. A product release may reject local edits when protected boot or signed package admission requires exact hashes.

Package authors and marketplace submissions

Package authors are responsible for the rights, security, compatibility, and behavior of the package material they submit or distribute.

Bitfield may review, reject, remove, quarantine, watermark, or require re-signing of packages for security, policy, compatibility, license, or abuse reasons.

Third-party package content

A package may include third-party content or dependencies. The package author must preserve required notices and licenses for that content.

Third-party package notices do not expand rights in Bitfield-owned runtime artifacts.