Cognia 7.2.1 — Programs find their data on every machine

Applies to: all

Prepared October 16, 2026. This is a patch release. Several programs located their bundled data (the monitoring web GUI, example web GUIs, reference files of the validation gates) through an absolute path into the source tree of the machine that built the package. On that machine everything worked; in an unpacked package, a .deb installation or a container on another machine the path did not exist. The engines and their numerical behaviour are unchanged from 7.2.0: saved networks, checkpoints, snapshots and DPSH event logs stay compatible.

Fixed

  • Monitoring GUI of cognia_transformer_serve, cognia_transformer_serve_cuda and Sensory. The monitoring server looked for its web GUI only in the build machine's source tree. Elsewhere it did not start at all, without any message. It now finds monitoring-web/ next to the executable or in the package root (bin/../monitoring-web), and a missing GUI is reported on standard error. Containers no longer need a symlink to the build path.
  • cognia_monitor, cognia_cdct_monitor and the composite monitor use the same lookup; --web-root still overrides it.
  • cognia_cdct_procurement_gui and cognia_cdct_warehouse_gui find the web GUIs of Examples 24 and 25 in the package without --web-root.
  • Validation gates run from the package (cognia_validate_cdct_v2, cognia_validate_placement and the cognia_ccdl_* regressions) no longer fail on a missing reference file: their test programs read Docs/ and Cognia/ from the package.
  • The package now contains Cognia/experiments/, the declared experiments read by the installed cognia_ccdl_* regressions.

Changed

  • Programs look for bundled data in this order: next to the executable, the package root (bin/..), and only then the source tree recorded at build time (development builds).

Known limitations

The limitations of 7.2.0 still apply: Linux camera input was not verified on real hardware, cuBLAS is not bundled, the Windows package targets the RTX 50 series only, and on Linux the desktop client is a browser launcher. The ONNX engine described in the Agent Design Kit is planned, not implemented.

Correction to the 7.1.0 notes

Levelized CDCT 7.1.0 ships the Elasticsearch retrieval contracts and an adapter verified against a fake transport only. It cannot be configured from the CLI, supports plain HTTP rather than HTTPS, and before the subsequent R-01 correction rejected every real _search response because it did not request version: true even though the response parser requires _version.