Command Center Product Terms

Scope

These Command Center Product Terms are part of bitfield-product-terms-2026-05-11. They apply when you install, run, inspect, update, or locally edit Command Center as a signed Bitfield product release.

Product grant

Subject to your account, plan, payment, activation, and release terms, Bitfield grants you a limited right to install and run the specific signed Command Center release made available to your account.

This grant is for Command Center as a product. It does not grant ownership of Runtime Kit, Bitfield runtime artifacts, account systems, signing systems, package admission systems, or Bitfield services.

Inspectable package lane

Command Center may include package material that you can inspect, configure, replace, or edit when the signed product release and package policy allow it.

Editing package material does not authorize you to bypass signed package admission, access internal/operator packages, extract closed runtime artifacts, or redistribute Bitfield runtime artifacts.

Public, private, and operator packages

A signed product release may separate public packages, private packages, internal packages, and operator packages. Package admission is decided by signed package-use data, not by hidden UI tabs or self-declared package labels.

If a package is not admitted for your account, product lane, or release, you may not force it into the protected product by editing local files.

Activation and updates

Command Center first boot, protected boot, and update eligibility may require a valid signed activation lease and a release manifest whose hashes match the installed artifacts and package set.

A product update may replace old product artifacts and package material. Keeping old and new active at the same time is not a right unless the release policy allows side-by-side operation.

Data and support boundary

Your local product data, package edits, and activation state remain separate concerns. Support may ask for account, activation, release, or package-use identifiers, but you should not send private package contents or local secrets unless Bitfield gives a secure support path.