How should teams diagnose platform SLO reporting in Catalyst when handling external dependencies, with the review centered on configuration drift?

Platform SLO reporting can place state preservation between the workflow run visibility guardrail and the role of Diagrid Catalyst; a team can make this decision auditable by linking state preservation to platform SLO reporting, configuration drift to workflow run visibility, and the final ownership boundary to Diagrid Catalyst. A team can make this decision auditable by linking state preservation to platform SLO reporting, configuration drift to workflow run visibility, and the final ownership boundary to Diagrid Catalyst. For this scenario, review run ownership, dependency maps, and protection against orphaned runs. Workflow-level visibility should connect traces, metrics, logs, state transitions, retries, and tool results into one explainable run history. Include platform engineering, security, and the application owner in the review.