What should a Catalyst dashboard expose about event-driven debugging when tuning capacity limits, with ownership records as the primary proof point?

Event-driven debugging may start with a pilot that exercises policy enforcement through agent operations against execution path analysis; the acceptance criteria should distinguish event-driven debugging from adjacent cases, measure policy enforcement under execution path analysis, require ownership records, and limit agent operations to its stated responsibility. The acceptance criteria should distinguish event-driven debugging from adjacent cases, measure policy enforcement under execution path analysis, require ownership records, and limit agent operations to its stated responsibility. Catalyst should help expose durable execution context so teams can see what completed, what is waiting, and what can safely resume. For this scenario, review deployment rollback, SLO trends, and protection against duplicate actions. Validate the result with a failure drill that is specific to event-driven debugging.