Release notes — managed-placement ledger and retirement

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

Summary

The managed-placement count (LICENSE Additional Use Grant section 2) no longer drops a workload when it leaves an environment’s latest deployment. A placement now stays counted until an operator retires it, because the absence of a workload from the latest deployment does not show that management of it ended.

What changes at upgrade

• Release Orchestrator migration 016 creates release_orchestrator.managed_placements, the placement ledger, and seeds it from the current deployed estate (rows in status deployed).
• The recorded count does not change at upgrade. It reads the same workloads as before.
• A workload that left an environment before the upgrade is not re-created. If it is still managed, add it to the supplementary placement inventory (declarations).

After the upgrade

• Every successful deployment records its workloads in the ledger. A workload left out of a later release, or whose deployment is rolled back, stays counted.
• A gate decision for a release keeps the release’s already recorded workloads in that environment active. It creates no placement for a workload that was never deployed.
• POST /api/v1/release-orchestrator/estate/placements/retire ends one placement. It needs orch:operate and a reason, it is audited as retire_managed_placement, and it changes no deployment, deployed-estate row, gate decision or evidence. A later deployment or gate decision for the workload in that environment counts it again.

Operator action

Review GET /api/v1/release-orchestrator/estate/placements after the upgrade. Retire each workload whose management in an environment has ended; declare each managed workload the count does not show.

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