Identify the installed version
Record the product release, enabled domains and actual service image versions. BOX 3.0, 3.1 and 3.2 share a product branch but may differ in interfaces, settings and component contracts.
Read by task and version
Use the BOX 3.x branch for deployment, cameras, detector presets, event review, functional administration and its API. Use Platform 4.0 material for model/scenario development on that platform. BOX 5.0 composition does not make older configuration files interchangeable.
Configuration differences
A feature can require a domain, service dependencies, environment variables and interface settings. Identify the files actually read by the installed build before following a configuration example.
Plan changes
Retain a release manifest, compatible instructions and a tested backup. Validate an update in an isolated environment with representative sources, API consumers and operator roles. Historical wiki fixes apply only to their documented versions.
Detailed manuals and the shared LLM chapter
BOX 3.2 adds expanded user workflows, LLM features and specialized sections to the earlier operational branch; availability still depends on configuration, roles and licenses. The new manual tree separates routine instructions from the Sigma training exercises. Shared modules use the same article in both version trees, while camera forms, catalogs and API fields retain version-specific guides.