CosmoEdge 1.1.0

CosmoEdge 1.1.0

The release target is commit
8e43b81083536e95dbce5fcaff08277b01adc3d1 (tree
69a9147c3a433010c3f8ccdac6a5770b8d091ea6). The four device archives
below were built from package-source commit
ded6519a641ace9b1e9451ee1d62b77de9c8c4fa (tree
d97f5e419014e4459bac559498d43883ef184eec). The intervening merged change
is limited to release notes, API documentation, and the PR build gate; it
changes no runtime or package input, and the archive hashes remain unchanged.
All release-scoped gates are closed.

English release notes ·
简体中文发布说明

CosmoEdge 1.1 expands the common video-ingest, visual-orchestration, event, and
operations workflow across BM1688, CV186X, RK3576, RV1126B, and x86. Apple
Silicon macOS receives a deliberately scoped Docker Preview.

Platform deliveries

Platform	v1.1 delivery	Boundary
Sophon BM1688	Target-specific Open installation archive	Public v1.0.0 -> v1.1.0 in-place upgrade path; plain models and no device authorization.
Sophon CV186X	Independent target-specific Open installation archive	First public CV186X release; fresh installation, not a public v1.0 upgrade.
Rockchip RK3576	Target-specific cross-built archive	Includes RKNN, MPP/RGA, and RKLLM runtime path; first public RK3576 release.
Rockchip RV1126B	Target-specific cross-built archive with manifested community example models	Same release tier as RK3576; no RKLLM. Bundled Ultralytics-derived examples are AGPL-3.0-only community assets.
x86 Linux / Windows	Source release and Docker Compose runtime	ONNX Runtime CPU with persistent named volumes; no device archive.
Apple Silicon macOS	scripts/macos-docker-preview.sh and isolated Compose profile	linux/amd64 emulation for one local-video Preview workflow.

Device archive assets

Target	Asset	Bytes	SHA-256
BM1688	cosmo-V1.1.0-5f5eececbe38932ffe5522de8744931f.tar.gz	63,031,220	902da7e7a3e5f03b5d0d3e6b887136e7544105f3bcb31762616268cb22bd5cff
CV186X	cosmo-V1.1.0-59b03c0b96973fa16ecf53e6ed30b5f5.tar.gz	63,031,220	edff732afd1c78402a7ac9ec7a906727030bb28f7383076cd8598d0d532e8c49
RK3576	cosmo-V1.1.0-980cca8314eba775bd9ef2cab90b6f32.tar.gz	52,504,283	923b726c45f34249b2f4c8a7069bef0906a9d408cb9897dce4bbfd390f9118ce
RV1126B	cosmo-V1.1.0-8d95283a4fb5bac62c4181aa9f31eec9.tar.gz	50,362,197	02ba3cd5c6fa6829431e2ae74305e461dab79418a41b690edf2d4aab6f972f71

Download CosmoEdge-v1.1.0-SHA256SUMS,
CosmoEdge-v1.1.0-TARGET_CHIP-MAP.tsv, and
CosmoEdge-v1.1.0-release-manifest.json with the selected archive. Never reuse
a complete package across chips, even when selected model bytes happen to
match.

Validation status

• Package-source candidate x86 build and tests: PASS
  (run 32740415479).
• Package-source candidate RK3576/RV1126B package builds, target verification, artifact
  upload, and locked shared-builder publication: PASS
  (run 32740415467).
• Package-source candidate BM1688/CV186X native builds, 23-test package-policy suite,
  7-test Model Guard suite, and archive verification: PASS.
• Four archive target markers, package contents, SHA-256 values, root
  LICENSE/NOTICE, and scoped dependency/platform license bundles: PASS.
• Release-target provenance rebind from the package-source commit: PASS.
  The merged range changes exactly two release-note files, two API-reference
  pages, and the PR-check workflow; runtime and package-input changes: zero.
• Relative to the superseded pre-license-remediation archives, all functional
  payload entries are unchanged. RV1126B additionally differs only in the
  generated resource-manifest.json#/created_at timestamp, with normalized
  runtime/model fields identical: PASS.
• Controlled 72-hour fixed-workload evidence rebind: PASS at the unchanged
  engine/existing-model/workload boundary. It is not a maximum-capacity,
  RTSP-resilience, or restart-resilience claim.
• BM1688, CV186X, and RK3576 VLM component-hash rebind: PASS at the exact
  matching engine/platform-runtime boundary. The observed short-run gates
  remain 6, 6, and 4 channels respectively at 0.1 FPS/channel.
• Final BM1688 installation, authenticated service/API startup, reboot
  recovery, and staged-upload restart/resume/idempotence/cleanup: PASS on
  the exact final archive and engine hash.
• BM1688 application upgrade/recovery: PASS. The real-device cycle covered
  the designated pre-v1.0 legacy build to v1.1.0, controlled recovery to the
  frozen public v1.0.0 archive, and a final public-v1.0.0 to exact-v1.1.0
  reinstall. Fourteen configured cameras remained queryable, and all 14
  protected video files (779,456,915 bytes) retained the same aggregate content
  hash through every install, reboot, recovery, and cleanup phase.
• Alarm history was not a preservation gate for that upgrade cycle. Model
  assets were not backed up or inherited; commercial-model resources and Model
  Guard authorization remain separately managed and were not used as an
  application-release acceptance signal. This boundary is neither a model
  functionality PASS nor a product failure.
• The separately scheduled 12-hour VLM run is supplementary and does not
  replace or block the frozen public 72-hour/VLM evidence. CV186X, RK3576, and
  RV1126B are first-release installation targets and do not inherit a public
  v1.0 upgrade requirement.

Upgrade and installation

Read the bilingual Deployment Guide
before installing an archive. Retain the previous package and an independently
stored data backup until post-start validation finishes. Complete or cancel
v1.0.0 uploads before a BM1688 upgrade; incomplete staged uploads are not
migrated as resumable sessions. Application-package acceptance does not
provision or prove separately managed commercial-model resources or Model
Guard licenses.

Known limitations

• The 72-hour observations cover the listed fixed-channel profiles, not maximum
  capacity.
• Real RTSP network interruption and recovery are outside the controlled
  local-loop observation.
• VLM results are short-run performance gates, not semantic-accuracy,
  long-run, or production-configuration certification.
• macOS remains a single-local-video linux/amd64 Docker Preview.

Community and support

GitHub Discussions
is the official searchable English support channel. Reproducible defects belong
in GitHub Issues, and
vulnerabilities follow SECURITY.md.

Release decision

GO. Runtime, package, public-evidence, device, documentation, workflow, and
provenance-rebind gates are closed.