@cjwilburn please let's make sure this epic is linked to the automation when you have the chance 🙏

thank you everyone for completing this foundational milestone!

cc: @cjwilburn

@Alexand can we please make sure the automation is set for this epic? Also, could you please help @mbruemmer and I to understand the hours spent on this last week?

cc: @cjwilburn

Thanks everyone for bringing this to completion and presenting on the CTO Review

Summary

This MR adds a clarifying paragraph to the Production Change Lock (PCL) section of the change management handbook page.

Changes

Added a new paragraph after the introductory text explaining that:

• Hard PCLs are only created for low team-member coverage or periods of significant platform instability
• Users concerned about platform stability during events should consider the Soft PCL option

This helps set expectations about when Hard PCLs are appropriate and directs users to the right alternative.

thank you @rnienaber ! I am aligned. Approved - leaving to you to merge it

@e_forbes @Alexand @WarheadsSE - please link the issues of the work you are doing to this epic. If you don't have issues for the work you are doing please create one.

cc: @amyphillips

@andrewn for the sake of this PoC I think it is totally fair to use Caproni with everything running in Kubernetes

@e_forbes @Alexand please give a look to this epic and it makes sense. This is describing the ask for the PoC that ideally we want to show this Friday in the CTO Review.

Suggestion for scope cutting is to go with Fallback B (Go echo server deamon). Ideally we want to demo something that is go based. For Friday we can have a lot of manual connection if needed. In the future we should understand where the boundaries in capabilities between Caproni and OAK are so we can make sure we have clear interfaces and full compatibility, end-to-end

Let's use #proj_uam_platform for quick syncing but let's keep here all the decision points as the SSOT of this work.

cc: @chsanders @amyphillips @nolith @andrewn