Release notes — scan limb of the managed-placement count

Sprint: 20261027_003 (PLC-8) Status: Pre-release; forward-only Release Orchestrator migration 018.

Summary

The managed-placement count (LICENSE Additional Use Grant section 2) now also records the scan limb. A scan of an installed image or deployable artifact, and an earlier scan result applied to it while it is installed, are management activity for that workload in that environment.

What changes at upgrade

• Release Orchestrator migration 018 lets the placement ledger record the signals scan-of-installed-image and applied-scan-result. No row changes at upgrade.
• coverage.countedSignals of GET /api/v1/release-orchestrator/estate/placements lists applied-scan-result, deployment and scan-of-installed-image while the estate pass runs. definitive stays false: agent-observed containers, node changes and gate-only promotions are still not counted.

After the upgrade

• The estate pass (ReleaseOrchestrator:EstateRetouch, hourly by default) reads the latest successful scan of each installed digest through the Scanner owner API and records the earlier scan results its re-evaluation applies to each installed release.
• Each scan or applied result reaches every workload installed with that digest at that time. It adds no placement for a relationship already counted, and it re-activates a retired placement. A scan of a digest installed nowhere, or scanned before installation, changes nothing.
• With ReleaseOrchestrator:EstateRetouch:Enabled=false, the scan signals are not recorded and the read lists them as not counted.

Operator action

A workload that stays in an environment’s current deployment is still managed, and the estate pass counts it again. To end such a placement, deploy a release without the workload, then retire it with POST /api/v1/release-orchestrator/estate/placements/retire.

See the Release Orchestrator dossier, Managed placement (licence count).