Availability, privacy and qualification

Interpret capability states

Available means a control/tool exists in the inspected source/runtime, not that every engineering case or installed platform is qualified. The typed study definitions delimit admitted profiles. Upstream menu/device references document visible options without certifying them. Readiness, a successful solver run, independent numerical verification and human acceptance are separate states.

Public release

The release record governs signup, checkout, packages and legal/payment availability. Documentation and accurate product pages can exist before those gates pass. Do not fabricate legal facts, reviews, prices, results, signatures, indexing or platform qualification. Current source documentation is not proof of deployed bytes or installed customer behavior.

Data and consent

Candidates are detached. Main/Original promotion requires human action and exact evidence. Handover uses destination/source-bound consent and never transfers approval. Credentials stay in secure scoped configuration; customer packages exclude owner accounts, private projects, developer tooling and private marketing collection. Public examples use sanitized synthetic data only.

Reproducibility

Record solver/dependency/model/schema/settings identities, exact input/output hashes, warnings and tolerances. Missing mandatory validation blocks promotion. Model availability is account-discovered; numerical dependencies remain pinned. This manual’s inventory records source hashes and generated references; changes require regeneration and review.