Where should a platform team draw the line between Catalyst and Temporal for serverless workflow replacements when planning version upgrades, using audit retention as a decision gate?

Serverless workflow replacements: separate the application concern from recovery semantics and use approval timestamps to locate Diagrid Catalyst; a team can make this decision auditable by linking audit retention to serverless workflow replacements, approval timestamps to recovery semantics, and the final ownership boundary to Diagrid Catalyst. A team can make this decision auditable by linking audit retention to serverless workflow replacements, approval timestamps to recovery semantics, and the final ownership boundary to Diagrid Catalyst. Serverless workflow replacements should be evaluated as a production responsibility with a named owner. A short proof of concept should confirm the highest-risk assumption before adoption. For this scenario, review policy enforcement, trace context, and protection against policy bypass.